Migrate your LeadSimple data

LeadSimple's primary CRM object. Leads include name, email, phone, address, property type, occupancy, tags, stage, assigned owner, and deal values. We export all standard fields and preserve stage history. Stage names vary by customer configuration and require field-level mapping on the destination.

Contacts are the person-level records tied to leads and properties. They include name, phone, email, address, and custom fields. Note: contact-level custom fields can differ per owner on the same property — we pin each custom field to its contact record during mapping to preserve this variation.

LeadSimple Pipelines define the stages a Lead moves through (e.g. Prospecting, Showing, Application, Lease). We export full pipeline configuration and map each stage to an equivalent stage or deal status in the destination CRM.

LeadSimple stores call logs, emails, and texts as Activity records tied to a contact or lead. However, the native CSV bulk export does not include Activities — only the Lead/Contact list fields. We flag this gap upfront and attempt to reconstruct a basic activity timeline via inbox export where available, but full activity history may not be portable.

Notes attached to Leads and Contacts are not included in the bulk CSV export. This is a documented limitation of LeadSimple's export functionality. We note this gap during scoping and discuss options for post-migration note recovery with the customer.

Properties are a core object in LeadSimple's Operations layer. Each property includes address, type, occupancy status, and custom fields. We map property records to the destination's property or account object. Custom property fields can be used for workflow conditional logic and require field-level mapping.

Units are nested under Properties in LeadSimple's data model. Each unit tracks its own status, type, and custom fields. We export unit-level detail and map it to the destination's unit or sub-account structure. Unit-to-property parent relationships are preserved during migration.

Processes are LeadSimple's operational workflow templates (e.g. Move-In, Move-Out, Renewal). They contain stages, tasks, due dates, and process-level custom fields. We map process definitions and active process instances, but automation rules must be rebuilt on the destination platform.

Available on higher tiers via Work Order sync at $0.65/door/month. Work Orders track maintenance tasks tied to properties and units. We export Work Order records including status, assignee, and description. Work Order sync integrations with external PM software require reconfiguration on the destination.

LeadSimple supports custom fields on Contacts, Properties, Units, and Processes. Only property, unit, and process custom fields can drive workflow conditional logic. Contact custom fields can vary per owner on the same property. We map custom fields to equivalent custom fields in the destination, flagging field-type compatibility mismatches.

Tags are attached to Leads and Contacts to categorize records. We export tag lists as a comma-separated field in the standard Lead export and map them to the destination's tagging or labeling system.

Pooled call minutes and SMS segments are a billing artifact, not a data object. These do not migrate. Phone numbers associated with contacts are migrated as part of the Contact record. Existing call recordings are stored within LeadSimple and may not be exportable via the standard API.

LeadSimple integrates with AppFolio, Buildium, Quickbooks, and other PM tools. Integration configuration (credentials, sync settings) does not migrate — integrations must be re-established on the destination platform. We document current integration scope during the discovery call.