Migrate from LeadSimple to Pipedrive

LeadSimple leads map 1:1 to Pipedrive Leads Inbox. Fields like Pipeline Name, Stage Name, Source Name, and Referrer Name migrate as custom fields on the Pipedrive Lead object. Owner is resolved by email match against Pipedrive users. LeadSimple's stage status (Active / Won / Lost) maps to Pipedrive Lead status via value mapping.

LeadSimple person fields (name, email, phone, address) map directly to Pipedrive Person. Custom fields on LeadSimple contacts (e.g., owner_type, owner_request) create custom Person fields in Pipedrive. Notes and activities associated with a contact are migrated via LeadSimple API and attached to the Pipedrive Person record.

Pipedrive has no native Property or Unit object. LeadSimple properties are migrated as Pipedrive Organizations with property-specific data stored in custom fields: property_type, occupancy, number_of_units, cost. Address fields from LeadSimple property map to Organization address fields (street, city, state, zip). If a property has multiple owners or tenants, additional contact roles are created as Organization Contact Relationships.

LeadSimple Units are co-located with Property in a parent-child relationship. In Pipedrive, unit count and unit-level custom fields are merged into the parent Organization as custom fields (e.g., Unit_Count__c, Unit_Type__c). If a property has more than one unit record with distinct data, FlitStack creates a custom linked entity or stores unit data as a multi-value custom field for reference.

LeadSimple deals map to Pipedrive Deals with direct field mapping for name, ACV (annual contract value), stage, and close date. Owner resolves via email match to Pipedrive users. LeadSimple's deal-level cost field maps to a Pipedrive custom field (Deal_Cost__c) since Pipedrive has no native cost field. The deal is linked to the associated Organization (property) via Pipedrive's org_id relationship.

LeadSimple Processes define stage-based workflows (e.g., Inquiry → Showing → Application → Lease). Pipedrive has no process object. Process stage names migrate as a custom pick-list field (Process_Stage__c) on Lead and Person so the historical process position is preserved. The process definition and automation logic must be rebuilt in Pipedrive Automations — we export the process tree as a reference document.

LeadSimple bulk export does not include notes, calls, emails, or texts. FlitStack retrieves activities via LeadSimple API, maps them to Pipedrive Activity records (type: note, call, email, task), and associates each activity to the correct Person, Organization, or Deal. Original timestamps and owners are preserved. This requires API access beyond the standard bulk export.

LeadSimple owner IDs map to Pipedrive users by email address. Before migration, FlitStack generates an owner resolution report: matched owners map directly; unmatched owners are flagged and assigned to a designated fallback Pipedrive user. No record lands without a Pipedrive owner assignment.

LeadSimple tag lists on leads, contacts, and properties map to Pipedrive Labels using the same tag names from LeadSimple. Each unique tag in LeadSimple becomes a Label in Pipedrive and is applied to the corresponding Person, Lead, or Organization record. Tags containing special characters or spaces are normalized to alphanumeric format for Pipedrive compatibility. Multi-tag lists expand to multiple label assignments on the same record, preserving the full tagging taxonomy from LeadSimple.

LeadSimple contact custom fields (e.g., how_did_you_hear, owner_request) map to Pipedrive Person custom fields by type: text → varchar, number → int, currency → varchar with $ prefix, date → date. Pick-list fields require value-by-value mapping since Pipedrive stores pick-list options as API hashes.

LeadSimple property custom fields (e.g., lease_status, renewal_date, property_notes) map to custom fields on the Pipedrive Organization record. Conditional-logic fields that only exist on property or unit objects in LeadSimple must be stored as text or pick-list fields on Organization since Pipedrive has no property-level conditional logic.

LeadSimple's internal record ID is preserved as a custom text field (LeadSimple_ID__c) on each migrated record in Pipedrive. This enables delta-run de-duplication to prevent re-importing records already migrated, cross-system audit traceability to trace any record back to its LeadSimple origin, and rollback identification if reconciliation fails. The custom field stores the full LeadSimple GUID so you can reference source records during post-migration audits.