Migrate from Lofty to Pipedrive

Lofty People map 1:1 to Pipedrive Persons. Every field on the Lofty person record — name, email, phone, address, and all custom properties — transfers to the equivalent Pipedrive Person field. Owner is resolved by email match against Pipedrive users. Unmatched owners are flagged before migration commits so your admin can assign a fallback owner.

Lofty Companies map to Pipedrive Organizations. The name, domain/website, industry, employee count, annual revenue, and address fields transfer directly. Lofty parent-company hierarchies (if used) require manual reconstruction in Pipedrive since Organizations do not have a native parent-Organization field — FlitStack surfaces the hierarchy as a custom Organization field for admin reference.

Lofty Deals map to Pipedrive Deals — title, value, close date, owner, and custom fields transfer. The critical dependency is that the target Pipedrive Pipeline and its Stages must exist before Deals land, because each Pipedrive Deal is pinned to a specific Pipeline ID and Stage ID at creation time. FlitStack delivers a Pipeline setup specification as part of the migration plan.

Lofty Pipelines transfer as Pipedrive Pipelines with one key difference: each Pipedrive Pipeline has an ordered list of Stages that define deal flow. FlitStack maps each Lofty pipeline stage name to a corresponding Pipedrive stage within the target pipeline, preserving the stage order and probability values. Stage names are matched value-by-value from the Lofty stage list.

Lofty stage names (e.g., New Lead, Showing Scheduled, Under Contract, Closed Won, Closed Lost) map value-by-value to Pipedrive stage names within the target pipeline. Probability percentages attached to each Lofty stage transfer to the Pipedrive stage probability field. If a Lofty stage has no Pipedrive counterpart, FlitStack flags it for admin decision before migration runs.

Lofty engagement records (calls, emails, meetings, notes) transfer as Pipedrive Activities. Each activity is linked to its parent record — a Person, Organization, or Deal — using Pipedrive's relationship API. Original timestamps, activity type, duration, and subject line are preserved. Activity owners are resolved by email match against Pipedrive users the same way person owners are.

Every Lofty custom field — Text, Date, Number, Percentage, Currency, Single-Select, Multi-Select — requires a corresponding custom field to be created in Pipedrive before migration. Pipedrive generates a 40-character hash key for each custom field; FlitStack records this key in the mapping document and uses it in the API calls during migration. Single-Select and Multi-Select options must exactly match Lofty's option labels or the import will fail on those records.

Lofty owner assignments on Person, Company, and Deal records are resolved by matching the owner's email address against Pipedrive user accounts. If a Lofty owner has no Pipedrive user account, FlitStack assigns the record to the migration-initiating Pipedrive user and logs the unmapped owner in a pre-migration report for your admin to reassign manually after go-live.

Lofty file attachments on People, Companies, and Deals are downloaded and re-uploaded to Pipedrive's file storage linked to the corresponding record. Pipedrive's default file size limit is 25MB per file. Files exceeding this limit are flagged in the migration report and can be migrated via a separate bulk-upload step if needed.

Lofty does not have a separate Lead concept — all contacts exist as People. Pipedrive has an optional Leads inbox for unconverted contacts. FlitStack's default mapping routes all Lofty People directly to Pipedrive Persons. If your team uses Pipedrive's Leads feature, FlitStack can apply a routing rule (e.g., based on a Lofty custom field or source tag) to split records between the Leads inbox and Person records — this is configured before migration runs.