LeadSimple to Salesforce migration
Moving from LeadSimple to Salesforce Sales Cloud lets property management teams trade a per-user CRM with limited automation for Salesforce's account hierarchy, opportunity management, and AppExchange ecosystem — while preserving every lead, property, unit, pipeline stage, and custom field across the migration.
FlitStack AI migrates lead / contacts, accounts, custom object or task series, opportunity + sales process + record types and user / ownerids from LeadSimple to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

What moves from LeadSimple to Salesforce?
LeadSimple models its CRM around Leads, Properties, Units, and Processes with pipeline stages tied to a lead's lifecycle.
Read the full summary
Salesforce Sales Cloud uses a separate Lead and Contact object model backed by an Account hierarchy, with Opportunities for deal tracking, custom __c fields, and a robust Activity history built from Tasks and Events. FlitStack AI extracts LeadSimple data via its export API — bulk-exported leads with property details, stage history, and custom fields — and maps each record into the appropriate Salesforce object. Pipeline stages translate to Opportunity StageName values, property records map to Account objects, and units become either custom fields on Account or a custom junction object depending on the relationship model. Notes and activity history (calls, emails, texts) require separate retrieval since LeadSimple does not include them in its bulk export — those are surfaced as Salesforce Notes and Tasks with original timestamps and owners preserved. Workflows and automation logic do not migrate and must be rebuilt in Salesforce Flow.
Lead → Lead / Contact
LeadSimple Lead records split based on pipeline stage and lifecycle intent.
How it maps
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.
Property → Account
LeadSimple Property records map directly to Salesforce Account objects.
How it maps
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.
Unit → Custom junction object or Account field
LeadSimple Units exist as a sub-record of Property.
How it maps
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.
Process → Custom Object or Task series
LeadSimple Processes (operational workflows for leasing, renewal, make-ready) have no direct Salesforce equivalent.
How it maps
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.
Pipeline → Opportunity + Sales Process + Record Type
Each LeadSimple pipeline becomes a Salesforce Sales Process linked to a Record Type.
How it maps
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.
Owner / Assigned To → User / OwnerId
LeadSimple owner email addresses are matched against Salesforce User emails.
How it maps
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.
- LeadLeadsplit
- PropertyAccount1:1
- UnitCustom junction object or Account fieldtransformed
- ProcessCustom Object or Task seriestransformed
- PipelineOpportunitytransformed
- OwnerUsertransformed
+ 6 more in the mapping below
How LeadSimple and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | LeadSimple | Salesforce |
|---|---|---|
| Record model | Leads, Properties, Units, Processes — flat per-user CRM | Lead, Contact, Account hierarchy with Opportunity, custom __c objects |
| Activity export | Bulk export excludes notes and activities — not in standard CSV | Tasks and Events store full activity history with owner and timestamp |
| Pipeline representation | Pipeline Name + Stage Name on Lead object | Opportunity StageName tied to Sales Process and Record Type |
| Custom fields | Custom fields on contacts, properties, units, and processes; conditional logic limited to property/unit | Unlimited custom __c fields with field-level security and formula support |
| Pricing model | $29–$59/user/month (Phone+Inbox), $99/month (CRM), $1.35/door/month (Operations) | Per-user licensing from $25/user/month (Starter) to $550/user/month (Agentforce 1 Sales) |
| Automation portability | LeadSimple autopilot rules and process triggers do not export | Salesforce Flow, Process Builder, and Apex handle automation rebuild |
| Integration ecosystem | AppFolio and Buildium integrations with no broader AppExchange equivalent | AppExchange with 5,000+ prebuilt apps and native Einstein AI |
LeadSimple to Salesforce field mapping
The 30 most-used fields of 34 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
lead_nameLeadNameLead -
lead_nameLeadLastNameContact -
email_addressLeadEmailLead -
email_addressLeadEmailContact -
combined_phone_numbersLeadPhoneLead
| LeadSimple field | Salesforce field | Mapping | Note |
|---|---|---|---|
Lead.lead_name | Lead.Name | direct | |
Lead.lead_name | Contact.LastName | transformed | Lead name becomes LastName on Contact; first name extracted if space is present, otherwise LastName holds full name. |
Lead.email_address | Lead.Email | direct | |
Lead.email_address | Contact.Email | direct | |
Lead.combined_phone_numbers | Lead.Phone | direct | |
Lead.combined_phone_numbers | Contact.Phone | direct | |
Lead.tracked_phone_number | Lead.MobilePhone | direct | |
Lead.tracked_phone_number | Contact.MobilePhone | direct | |
Lead.address | Lead.Street | direct | |
Lead.city | Lead.City | direct | |
Lead.state | Lead.State | direct | |
Lead.zip_code | Lead.PostalCode | direct | |
Lead.address | Contact.MailingStreet | direct | |
Lead.city | Contact.MailingCity | direct | |
Lead.state | Contact.MailingState | direct | |
Lead.zip_code | Contact.MailingPostalCode | direct | |
Lead.pipeline_name | Opportunity.RecordTypeId | transformed | Each LeadSimple pipeline becomes a Salesforce Record Type; RecordTypeId is set based on pipeline name matching. |
Lead.stage_name | Opportunity.StageName | value_mapping | Stage values map value-by-value per pipeline/Record Type. Probability re-applied from Salesforce stage defaults. |
Lead.stage_status | Opportunity.Stage_Status__c | custom_field_required | LeadSimple Stage Status becomes a custom pick-list field on Opportunity for reference continuity. |
Lead.source_name | Lead.LeadSource | direct | |
Lead.referrer_name | Lead.Referrer_Name__c | custom_field_required | Referrer name stored as a custom text field since Salesforce has no native referrer field. |
Lead.property_type | Account.Industry | value_mapping | Property type values (single-family, multi-family, commercial) map to Industry pick-list values. |
Lead.occupancy | Account.Occupancy__c | custom_field_required | Occupancy rate stored as a custom percent field on Account. |
Lead.annual_contract_value | Account.AnnualRevenue | direct | |
Lead.cost | Account.Cost__c | custom_field_required | Cost stored as a custom currency field on Account for financial reference. |
Lead.number_of_units | Account.Number_of_Units__c | custom_field_required | Unit count stored as a custom number field on Account. |
Lead.created_at | Lead.Original_Create_Date__c | custom_field_required | Salesforce CreatedDate is set at migration time; original LeadSimple create date preserved as custom datetime. |
Lead.created_at | Contact.Original_Create_Date__c | custom_field_required | Same preservation pattern for Contact records — original create date stored as custom datetime. |
Lead.closed_at | Opportunity.CloseDate | direct | |
Lead.next_task_kind | Task.Subject | direct |
What to watch for in a LeadSimple to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Notes and activities are excluded from LeadSimple's bulk export
LeadSimple's Export Leads function produces a CSV containing contact fields, property details, pipeline stage, and custom properties — but notes and activity history (calls, emails, texts) are not included.
How we handle it
Teams that rely on historical agent notes to maintain leasing context will find those records absent from a standard migration. FlitStack retrieves notes and activities via LeadSimple's API after the bulk export, then loads them as Salesforce Notes and Tasks. However, this requires API access and is rate-limited — very large activity histories may require multiple API passes spread over time to avoid hitting LeadSimple's request throttling.
Pipeline stages require value-by-value mapping per Record Type in Salesforce
Each LeadSimple pipeline becomes a Salesforce Record Type, and stage values must map individually to the Opportunity StageName pick-list scoped to that Record Type.
How we handle it
A LeadSimple pipeline with five custom stage names (Inquiry, Tour Scheduled, Application, Approval, Lease Signed) maps to five Opportunity Stage values with corresponding probability and forecast category settings. If probability or forecast category settings are misconfigured at the Salesforce admin level, pipeline reporting will show inaccurate revenue projections post-migration. FlitStack delivers a stage-mapping worksheet before the migration runs so Salesforce admins can verify probability and forecast settings per stage before data lands.
Property-to-Account mapping flattens LeadSimple's unit hierarchy
LeadSimple stores units as a sub-record of Property with their own occupancy, rent, and type fields.
How we handle it
Salesforce Account has no native unit sub-object — units are typically modeled either as a custom Unit__c junction object with a lookup to Account, or as custom fields on Account (Number_of_Units__c, Occupancy__c) for single-property portfolios. Teams with multi-building portfolios and unit-level reporting needs must decide on the unit data model before migration begins. FlitStack surfaces this decision in the pre-migration schema plan. The chosen model affects reporting and process automation downstream.
LeadSimple workflows and autopilot rules do not export
LeadSimple's autopilot features — automatic stage-change rules, renewal-triggered workflows, delinquency alerts, and make-ready task sequences — are a core part of the product for property managers.
How we handle it
Salesforce has no equivalent import path for these rules. They must be rebuilt in Salesforce Flow or Process Builder. FlitStack exports a human-readable rule inventory as a reference document showing each autopilot trigger, condition, and action. Salesforce admins use this as a blueprint for Flow rebuild. This step is manual and typically requires 1–3 weeks depending on workflow count and complexity.
Tag-based segmentation has no native Salesforce equivalent
LeadSimple uses a freeform Tag List on leads and properties (comma-separated labels like 'referral-partner,high-priority,veteran').
How we handle it
Salesforce has no native tagging system — segmenting records requires custom fields, report filters, or a third-party tagging app from the AppExchange. FlitStack migrates the tag list as a custom text field (Tag_List__c) so the raw data is preserved. Teams that rely on tags for quick filtering in LeadSimple will need to recreate that workflow using Salesforce report filters or a tagging solution after migration.
How the migration runs
Audit LeadSimple data export scope and retrieve activity data via API
FlitStack runs a bulk export from LeadSimple covering all Leads, Properties, Units, and Process records with custom fields expanded.
What this step covers
Simultaneously, we initiate an API-based retrieval of notes and activity history (calls, emails, texts) that fall outside the bulk export scope. This step identifies record counts per object, identifies which custom fields exist on each object, and surfaces any API rate-limit responses that require throttling or retry. A data-quality report is generated listing duplicate risks, missing required fields, and records without an assignable owner.
Design Salesforce schema: Account hierarchy, Record Types, and custom fields
Based on the LeadSimple data audit, FlitStack delivers a Salesforce schema plan covering the Account hierarchy design (property → unit model), Record Type creation per LeadSimple pipeline, custom field creation on Account, Contact, Lead, and Opportunity with correct types and pick-list values, and junction object design for unit relationships.
What this step covers
The plan is reviewed by your Salesforce admin before any custom fields are created. This ensures the Salesforce schema is ready before any data loads run, preventing the common migration problem of data arriving before the fields it needs.
Resolve owners and create user mapping
FlitStack matches LeadSimple owner email addresses against Salesforce User emails.
What this step covers
Matched owners receive their assigned records automatically. Unresolved owners are flagged in a pre-migration owner report — your team either provisions those users in Salesforce first or designates a fallback owner for their records. No record loads into Salesforce without an OwnerId. This step also validates that Salesforce user licenses are sufficient for the expected user count post-migration.
Run sample migration with field-level diff
A representative slice of records — typically 100–500 spanning leads across different stages, a sample of properties with units, and a few process records — migrates into a Salesforce sandbox.
What this step covers
FlitStack generates a field-level diff comparing source values against destination field values for every mapped field. You review the diff to verify stage mapping, owner resolution, property-to-Account linkage, and unit data placement. Only after you sign off does the full migration proceed.
Execute full migration with delta-pickup window
The full dataset loads into production Salesforce in dependency order: Accounts first (for AccountId lookups), then Leads and Contacts, then Opportunities with stage and RecordTypeId mapping, then custom objects, then activities and notes.
What this step covers
A delta-pickup window of 24–48 hours captures any records created or modified in LeadSimple during the cutover window. All operations are logged in an audit trail. One-click rollback is available if post-migration reconciliation reveals data integrity issues.
LeadSimple - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
LeadSimple-to-Salesforce migrations land in the lower-to-middle range when record counts are under 10,000 and the data model uses standard lead export fields. Costs climb toward the upper bound when properties and units require Account hierarchy mapping with custom junction objects, when custom property fields exceed 30, or when activity data must be reconstructed from separate API calls after the bulk export completes. Pipeline-to-Opportunity stage mapping with value-by-value translation and record-type configuration also adds schema complexity that affects scope. FlitStack prices against record count, custom field count, and destination-side schema complexity — custom __c field creation and junction object design are the primary cost drivers. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for LeadSimple to Salesforce →Why teams move from LeadSimple to Salesforce
- LeadSimple users report persistent email errors that interrupt daily communication — messages fail to send or close without warning, requiring page reloads to recover. Salesforce's native email sync with Outlook or Gmail integration eliminates this failure class entirely and provides server-side logging of every sent and received email.
- LeadSimple's feature set is purpose-built for property management and caps out when teams need multi-entity reporting, territory management, or compensation planning. Salesforce's reporting engine (standard reports, Salesforce Reports, and Tableau Next) handles cross-account analytics that LeadSimple cannot deliver without a third-party overlay.
- As property portfolios scale beyond 500 doors, LeadSimple's per-user pricing plus per-door Operations fee compounds faster than Salesforce's per-seat model for teams that only need CRM access. Salesforce Professional at $100/user/month with unlimited contact storage and no per-door surcharge becomes more cost-predictable at scale.
- LeadSimple's integration library is limited to AppFolio and Buildium, leaving teams with no path to connect Salesforce CPQ, Salesforce Maps, or Salesforce Data Cloud. Once a property management team adopts a broader Salesforce stack, LeadSimple becomes a standalone island that requires manual data re-entry or brittle API bridges.
- LeadSimple does not export notes and activities in its bulk export — these must be retrieved separately via API or reconstructed manually. Teams with years of leasing-agent notes, call logs, and email threads hit a data preservation wall that cannot be resolved through standard CSV export alone.
Questions, answered
LeadSimple to Salesforce migration questions
How long does a LeadSimple to Salesforce Sales Cloud migration take?
Most LeadSimple-to-Salesforce migrations complete in 48–72 hours of clock time for datasets under 50,000 records. The planning and schema design phase typically runs 3–5 business days before any data moves. Larger portfolios with 500,000+ records, complex property-to-unit hierarchies, or heavy activity histories requiring API-based activity retrieval extend to 5–7 days. The longest single step is usually retrieving notes and activity data via LeadSimple's API if the history spans several years, because API rate limits require pacing the requests.
Will my LeadSimple workflows and autopilot rules migrate to Salesforce Flow?
No. LeadSimple's autopilot rules, stage-change triggers, renewal workflows, and delinquency alerts do not export. FlitStack generates a workflow inventory document listing every active rule with its trigger conditions, criteria, and actions — this serves as a rebuild reference for your Salesforce admin or FlitStack's automation team. Automation rebuild typically requires 1–3 weeks depending on rule count and complexity. Salesforce Flow is the replacement tool, and FlitStack can scope the Flow rebuild as a separate workstream.
What does a LeadSimple pipeline stage become in Salesforce?
Each LeadSimple pipeline becomes a Salesforce Record Type, and each Stage Name maps to an Opportunity StageName value scoped to that Record Type. The mapping is value-by-value — a LeadSimple stage called 'Tour Scheduled' becomes a Salesforce Opportunity Stage with the same label (or a renamed equivalent if your admin prefers). Probability and forecast category are re-applied from Salesforce's stage defaults or your admin-defined settings. FlitStack delivers a stage-mapping worksheet before migration runs so you can verify the probability and forecast implications of each mapping.
Can I migrate LeadSimple properties and units to Salesforce Accounts?
Yes. LeadSimple Property records map directly to Salesforce Account objects — Property Name becomes Account Name, address fields map to BillingAddress, and Property Type maps to Industry. LeadSimple Units require a decision: for simple portfolios, unit count and occupancy migrate as custom fields on Account (Number_of_Units__c, Occupancy__c). For portfolios requiring per-unit tracking, FlitStack designs a custom Unit__c junction object with a lookup to Account, storing rent, occupancy, and type per unit. This decision is made during the pre-migration schema design phase.
What happens to my LeadSimple notes and activity history after migration?
LeadSimple's bulk export does not include notes and activity records — this is a known limitation of the platform's export function. FlitStack retrieves notes and activity history (calls, emails, texts) separately via LeadSimple's API and loads them as Salesforce Notes and Tasks respectively, linked to the parent Lead, Contact, or Account. The original author and timestamp are preserved. Very large activity histories may require API request pacing to avoid throttling — FlitStack handles this transparently and flags the expected retrieval timeline during the audit phase.
Does the migration affect my LeadSimple account during the cutover?
No. FlitStack uses scoped read access to extract data from LeadSimple — your team continues working in LeadSimple throughout the migration window. A delta-pickup window (24–48 hours) captures any new leads, updated stage changes, or modified property records created or changed during the cutover period. At go-live, your Salesforce org reflects LeadSimple's final state as of the delta close. No records are modified or locked in LeadSimple during the migration process.
What does LeadSimple's Tag List become in Salesforce?
LeadSimple's Tag List (comma-separated labels on leads or properties) migrates as a custom text field called Tag_List__c on the target Salesforce object (Account for property tags, Lead for lead tags). The raw tag data is preserved exactly. However, Salesforce has no native tagging UI — teams that used tags for quick visual segmentation will need to recreate that workflow using Salesforce report filters, list views, or an AppExchange tagging app. FlitStack surfaces this as a post-migration configuration note so your admin can select a tagging solution that fits your workflow.
How are LeadSimple custom property fields handled in Salesforce?
LeadSimple custom fields on properties and units (currency fields, date fields, URL fields, or conditional-logic fields) map to Salesforce custom fields on the appropriate object. Currency fields become Currency fields in Salesforce, dates preserve their original values, and URL fields become URL fields. Fields used for conditional logic in LeadSimple (which must live on Property or Process in LeadSimple) become custom fields on the corresponding Salesforce object. FlitStack's pre-migration schema plan lists every custom field, its Salesforce target object, field type, and any value-mapping required before the migration runs.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Aweber to SalesforceMapping · history · rollbackDynamics 365 to SalesforceMapping · history · rollbackSnovio to SalesforceMapping · history · rollbackServiceTitan to SalesforceMapping · history · rollbackInsightly CRM to SalesforceMapping · history · rollbackZendesk Sell to SalesforceMapping · history · rollback LeadSimple to HubSpotMapping · history · rollbackLeadSimple to Zoho CRMMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from LeadSimple to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote