Migrate from Freshmarketer to Pipedrive

Freshmarketer Contact records map to Pipedrive Person records using email as the dedupe key. The lifecycle_stage property migrates to a custom field lifecycle_stage__c on Person so the original segmentation is preserved for reporting even though Pipedrive has no native lifecycle concept. Any Marketing Contacts flag value (true/false based on campaign enrollment) migrates to a custom field marketing_contact__c. Owner assignment resolves via email match to Pipedrive User records, with unresolved owners held in a reconciliation queue.

Freshmarketer Company records map to Pipedrive Organization records using company domain as the secondary dedupe key alongside name. The org_contact_id association between Freshmarketer Companies and Contacts maps to the link between Pipedrive Organizations and Persons, which we resolve after both object types are loaded. Industry, address, and custom company fields migrate to matching Pipedrive Organization fields or custom fields.

Freshmarketer Deals map directly to Pipedrive Deals with pipeline and stage preserved. We create Pipedrive pipelines matching the Freshmarketer pipeline structure before Deal import, and stage names map 1:1 to Pipedrive stage labels. The deal owner maps via email match to the Pipedrive User. Custom deal fields require mapping against Pipedrive's custom field types; dropdown fields in Freshmarketer map to Pipedrive select options.

Freshmarketer email logs and email conversations migrate to Pipedrive Activity records with type=email. We preserve subject, body, timestamp, and direction (sent/received) in the activity record linked to the Person. Email attachments migrate as file references linked to the activity. Activity timestamps maintain chronological ordering in Pipedrive's timeline view.

Freshmarketer call records migrate to Pipedrive Activity with type=call. Call duration, disposition, and recording URL (if available via API) map to custom activity fields. Owner assignment resolves via email match to Pipedrive User.

Freshmarketer meeting records migrate to Pipedrive Activity with type=meeting. Start time, end time, location, and attendees preserve in the activity record. Attendee emails are matched to Pipedrive Person records and linked if found; unmatched attendees are stored as free-text attendee names.

Freshmarketer sales activities and standalone notes migrate to Pipedrive Activity with type=note or type=task depending on the Freshmarketer record type. Status, priority, and due date preserve on task-type activities. Note body migrates as the activity text content.

Freshmarketer custom fields on contacts, companies, and deals require pre-creation in Pipedrive before migration begins. We map field types during discovery: Freshmarketer text maps to Pipedrive text, date maps to date, dropdown maps to select, multi-select maps to multiple select where supported, and numeric fields map to numeric. Custom field creation happens in Pipedrive before record import so that field mapping during load is satisfied.

Freshmarketer Journeys cannot be exported as executable automation logic via the API. We capture Journey configuration (trigger conditions, step actions, enrolled contact count at cutover) as a structured reference document. We also export which contacts were enrolled in which Journey at cutover as a static list so the customer's admin can replay enrollment in Pipedrive automation or document it for a marketing ops rebuild. Journeys do not execute in Pipedrive without manual recreation.

Freshmarketer Segments define audience criteria for campaign targeting. Pipedrive has no native segment object, so we map segment criteria to Pipedrive static lists or tag assignments at migration time. Contacts matching segment criteria receive the corresponding tag in Pipedrive. The segment definition (criteria logic) is documented in the handoff inventory for the admin to rebuild as a Pipedrive filter or list if dynamic audience behavior is needed.

Tags on Freshmarketer contacts, companies, and deals migrate as flat tag strings applied to the corresponding Pipedrive record. No tag hierarchy exists in either platform, so the mapping is direct. Tags from different object types on the same record append as comma-separated tag values in Pipedrive.

Freshmarketer User records (name, email, role) map to Pipedrive User records resolved by email match. Active status, role assignment, and team membership map where the field names match. Users without a matching Pipedrive User at migration time are held in a queue for admin provisioning before record import resumes because OwnerId references on Contacts, Companies, and Deals require a valid User.