Migrate from MARS to Pipedrive

MARS Contacts map to Pipedrive People. The MARS contact email address becomes the Person email field and serves as the dedupe key during import. First name and last name split from the MARS full-name field. Phone, address, and any standard fields migrate to their Pipedrive equivalents. Custom fields on Contact carry as Pipedrive custom fields on Person.

MARS Companies map to Pipedrive Organizations. The company name becomes the Organization name field. Website, address, phone, and industry fields migrate directly. Organization is created before Person import so that the person-organization link is satisfied at the moment of Person insert if MARS Contact carries a company association.

MARS Deals map directly to Pipedrive Deals. Deal name, value, expected close date, stage, and owner migrate. The MARS deal stage maps to a Pipedrive Stage within the target Pipeline. Closed-won and closed-lost status from MARS carries into Pipedrive Deal status values.

Each MARS deal stage value maps to a Pipedrive Stage. We configure the target Pipeline in Pipedrive with stages matching the MARS stage names and probabilities before migration. If MARS uses multiple pipelines, we create a Pipedrive Pipeline for each and assign the correct pipeline ID to Deals during import.

MARS pipelines map to Pipedrive Pipelines. Each Pipedrive Pipeline gets its own set of Stages, and Deals are assigned to the correct Pipeline by matching the pipeline name from MARS to the configured Pipedrive Pipeline. We configure pipelines before any Deal import so that the pipeline ID reference is valid at insert time.

MARS call activities map to Pipedrive Activity records with type set to Call. Duration, disposition, and outcome fields carry to Pipedrive custom fields on the Activity. The activity is linked to the parent Person and Deal via Pipedrive's subentity references at insert time.

MARS email activities map to Pipedrive Activity records with type set to Email. Subject and body content carry to the Pipedrive Activity subject and content fields. Attachments migrate as linked files on the Activity record. The activity is linked to the correct Person and Deal via lookup at insert time.

MARS meeting activities map to Pipedrive Activity records with type set to Meeting. Start time, duration, and location fields carry from MARS. The activity is linked to the relevant Person and Deal at migration time.

MARS task activities map to Pipedrive Activity records with type set to Task. Subject, due date, status, and priority migrate directly. The task is linked to the parent Person, Organization, or Deal via Pipedrive's subentity references.

MARS notes attached to Contacts, Companies, or Deals migrate to Pipedrive Note records linked via ContentDocumentLink to the parent record. Note content migrates as rich text with the creation timestamp preserved.

MARS owners resolve by email match against Pipedrive User records. We extract every distinct owner email referenced on Contacts, Companies, Deals, and Activities and match to Pipedrive Users by email. Any MARS owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

MARS custom fields on Contacts, Companies, and Deals carry to Pipedrive Custom Fields on the equivalent object. We verify each MARS custom field type against Pipedrive's accepted types before schema build. Pipedrive does not allow field type changes after creation, so type verification happens in the discovery phase. If a type mismatch is found, we recreate the field with the correct type and use Pipedrive System ID export/import to transfer existing data.