Migrate from LeadSimple to Salesforce Sales Cloud

LeadSimple Lead records split based on pipeline stage and lifecycle intent. Qualified leads (Stage Status = Closed Won or advanced stages) land as Salesforce Contact under an Account. Unqualified inbound leads land as Salesforce Lead with Status mapped from Stage Name. The split rule is configurable — teams that treat all leads as contacts can set a rule to route everything to Contact instead.

LeadSimple Property records map directly to Salesforce Account objects. Property Name becomes Account Name, Address maps to BillingAddress compound, city/state/zip map to those sub-fields, and Property Type becomes a custom Industry or Type pick-list value. LeadSimple's parent-property hierarchy (if used) maps to Salesforce ParentId on Account.

LeadSimple Units exist as a sub-record of Property. In Salesforce, units can map to a custom Unit__c junction object linking back to the parent Account (Property), storing Number_of_Units__c, Occupancy__c, Property_Type__c, and rent fields. Alternatively, for simple single-property portfolios, units count migrates as Number_of_Units__c on the Account. The choice depends on reporting complexity — FlitStack surfaces this decision before migration runs.

LeadSimple Processes (operational workflows for leasing, renewal, make-ready) have no direct Salesforce equivalent. Process type, stage, and custom process fields migrate as a custom Process__c object with lookup to Account. Stage history is preserved as a custom text area field listing stage transitions with timestamps. Process automation must be rebuilt in Salesforce Flow.

Each LeadSimple pipeline becomes a Salesforce Sales Process linked to a Record Type. Pipeline Stage values map to Opportunity StageName via value-by-value translation. Probability and forecast category are re-applied from Salesforce-side stage defaults. Teams with multiple pipelines in LeadSimple end up with multiple record types in Salesforce — each needing its own page layout and field set.

LeadSimple owner email addresses are matched against Salesforce User emails. Matched users receive their assigned records. Unmatched owners are flagged before migration — either those users are invited to Salesforce first or their records are reassigned to a designated fallback owner. No record lands in Salesforce without an OwnerId.

LeadSimple's communication log (calls, emails, texts) is not included in the standard bulk export. FlitStack retrieves activity records via LeadSimple's API, then loads them as Salesforce Tasks (Type = Call, Email, or SMS) with the original WhoId (Lead or Contact), subject line, description, and created timestamp. Activity owners resolve via email match as with standard records.

LeadSimple notes attached to leads, properties, or units are not in the bulk export. FlitStack retrieves them via API and loads as Salesforce Notes or ContentNotes linked to the parent record (Lead, Contact, or Account). Original author and create date are preserved as body metadata. Rich-text formatting is retained.

LeadSimple's Tag List stores comma-separated labels on a lead or property (e.g., 'high-priority, referral,Section8'). These migrate as a custom text field (Tag_List__c) on the target object. Tag-based segmentation is rebuilt in Salesforce as filter views or report groups rather than as a native tagging system.

LeadSimple custom fields on properties, units, and processes (currency fields, date fields, link fields) map to Salesforce custom fields on the appropriate object. Date fields preserve the original value as-is. Currency fields map to Salesforce Currency fields with the org's default currency or the source's recorded currency. Link fields (URLs) migrate as URL fields on Account or the relevant custom object.

LeadSimple's Annual Contract Value on a lead and Cost on a property are two different measures. For property-level financial data, Annual Contract Value maps to Account.AnnualRevenue. For deal-level financial tracking (e.g., renewal value per unit), the same metric maps to Opportunity.Amount with the Opportunity linked to the Account. Teams choose which model applies to their reporting structure before migration runs.

LeadSimple's autopilot rules and stage-change triggers have no direct equivalent in Salesforce. FlitStack exports the rule definitions as a PDF-readable reference document showing trigger conditions, actions, and field updates. Salesforce admins use this as a rebuild guide for Flow. No automation logic migrates automatically.