Migrate from Lofty to Salesforce Sales Cloud

Lofty's primary record is the Lead object, which maps directly to Salesforce Lead with a one-to-one correspondence. Lofty's agent owner field resolves to Salesforce OwnerId through email address matching against existing Salesforce users. Property associations attached to Lofty leads require custom handling through a junction object — see the property mapping section below for the complete transformation approach.

Lofty leads that have reached a closed status (stage equals Closed Won or Closed Lost) can route directly to Salesforce Contact records. Agents who manage ongoing deals remain as Salesforce Leads until they are qualified and converted through Salesforce's standard Lead conversion process. This decision rule applies based on the final Lofty stage value captured at the time of migration.

Lofty property associations attach a property record directly to a lead through a linking table. In Salesforce, each property becomes both a Salesforce Account (representing the brokerage or property entity) and optionally a custom Property__c object, with a junction table named LeadProperty__c that connects the property to Salesforce Leads through lookups on both sides.

Lofty pipeline stage values map to Salesforce Opportunity StageName pick-list values through a value-by-value mapping approach. Each stage maps to a corresponding Salesforce stage with associated probability percentage and forecast category assignment. Lofty's custom stage names such as Showing, Offer, and others require pick-list value creation in Salesforce Setup before the mapping can be applied during migration.

Lofty's pipeline construct, which organizes leads through sequential stages, maps to Salesforce's combination of Sales Process and Record Type. Each distinct Lofty pipeline becomes a Salesforce Record Type on the Opportunity object, with its own Sales Process that controls which StageName values are available for selection at each stage of the sales cycle.

Lofty single-select custom fields migrate to Salesforce custom pick-list fields using the __c API name suffix. Field values map one-to-one with no transformation required. The new pick-list field must be created in the target Salesforce org before migration begins, with all allowed pick-list values defined in Salesforce Setup to match the source Lofty field values exactly.

Lofty multi-select fields migrate to Salesforce Multi-Select Pick-list fields that store values as semicolon-separated strings within a single field. Important limitation: Multi-Select Pick-lists cannot be used as dependent pick-lists dependent on other fields, and they cannot be referenced in some formula field contexts or certain workflow criteria, which may require alternative field architecture design.

Lofty currency fields migrate to Salesforce custom currency fields that require setting the target Salesforce org's currency ISO code (such as USD, EUR, or GBP) in Setup before migration commences. Currency amount values transfer as-is with their original decimal precision preserved, and the field displays using the org's configured currency format settings.

Lofty number, percentage, date, and text custom fields map directly to Salesforce custom fields of their equivalent data type. Salesforce text field length must be set to accommodate the maximum Lofty source field values, noting that standard Salesforce text fields have a maximum length of 255 characters unless configured as Long Text Area fields with up to 131,072 characters.

Lofty activity history encompassing calls, emails, meetings, and notes migrates to Salesforce as Tasks (for calls and emails), Events (for scheduled meetings), and Notes objects (for text notes). Original creation timestamps and original owner IDs are preserved during migration to maintain complete activity history and accountability tracking.

Lofty agents resolve to Salesforce users through email address matching against the target Salesforce org's user records. Any unmatched agents are flagged in a pre-migration report with their record counts — your team must either create corresponding Salesforce user accounts or assign those records to a designated fallback owner to prevent OwnerId null errors during the migration insert operations.

Lofty tags and segments have no direct Salesforce equivalent native object or field type. We preserve the original tag data as a multi-select custom field on the Lead record for reference and historical preservation. Any segmentation logic or dynamic list membership based on tags must be rebuilt using Salesforce Campaigns, Campaign Member statuses, or custom report filter criteria.