Migrate from Market Leader to Pipedrive

Market Leader Contact maps directly to Pipedrive Person. All standard fields including name, email, phone, job title, and address transfer as Person fields. The Contact's primary company property resolves to the OrganizationId lookup on the Person record. FlitStack AI verifies that each referenced Organization exists in Pipedrive before creating the Person record to prevent orphaned org_id references.

Market Leader supports N:N contact-to-company associations. Pipedrive Persons have one primary OrganizationId and a secondary additional_org_ids field for additional organizations. FlitStack AI takes the most-recently-modified company as the primary OrganizationId and surfaces remaining company links in additional_org_ids for admin review. Contacts with more than two company associations in Market Leader require manual reconciliation post-migration.

Market Leader Company maps directly to Pipedrive Organization. Name, domain, website, industry, employee count, and annual revenue transfer as Organization fields. Parent-company hierarchies in Market Leader map to Organization's parent_org_id field. We migrate parent records first to ensure hierarchy resolution before child records are processed.

Market Leader Deal maps directly to Pipedrive Deal. The dealname field becomes Deal title, amount transfers as value, dealstage maps to the Stage within the target Pipedrive Pipeline, and closedate becomes close_date. Each deal's pipeline_id references the corresponding Pipedrive Pipeline created during pre-migration setup.

Market Leader Pipeline becomes a Pipedrive Pipeline. Each pipeline stage in Market Leader maps to a named Stage within that Pipeline. Stage order and probability values are preserved. If Market Leader has multiple pipelines, we create corresponding Pipedrive Pipelines with matching stage names.

Market Leader engagement records (calls, emails, meetings, notes) map to Pipedrive Activity objects. Each activity type maps to the Pipedrive Activity type field (call, email, or meeting). The activity is linked to the parent Person, Organization, or Deal record via id and type.

Market Leader Notes migrate as Pipedrive Activities with type = note. The note body and original create timestamp are preserved. Notes attached to specific contacts or deals are linked to the corresponding Person or Deal record. All notes are extracted via API to preserve full content that CSV exports omit.

Market Leader custom properties on contacts require corresponding Pipedrive Person custom fields. We create each custom field in Pipedrive before migration, capture the generated key hash, and use it in the field mapping. Pick-list custom properties require value-by-value mapping in Pipedrive's field options.

Market Leader deal custom properties (e.g., deal priority, referral source, product interest) migrate to Pipedrive Deal custom fields. Pipedrive does not have a native deal priority field — we create a custom pick-list or text field and map Market Leader's values. Field keys are generated at migration time.

Market Leader owner records are matched to Pipedrive users by email address. Unmatched owners are flagged before migration — the team either invites the user to Pipedrive or reassigns their records to a designated fallback user. No record lands in Pipedrive without a valid user_id.

Market Leader pre-built drip email sequences tied to lead products have no Pipedrive equivalent. We export campaign definitions (trigger conditions, step cadence, email content) as a rebuild reference document for Pipedrive Automations and Sequences setup. No automation logic migrates automatically.