Migrate from FIVE CRM to Pipedrive

FIVE CRM Contacts map directly to Pipedrive Person records. Email address, phone number, and owner assignment transfer via CSV or API import. We validate email format and flag duplicate Person records (by email address) before insertion to avoid silent duplication in Pipedrive. The FIVE CRM owner hubspot_owner_id resolves to a Pipedrive User by email match.

FIVE CRM separates Leads from Contacts in its data model. We merge Lead records into Pipedrive Person records, preserving the originating Lead_Source as a custom field lead_source__c on the Person. Any lead score value from FIVE CRM migrates to a custom numeric field lead_score__c. Leads without an email address are flagged for manual review because Pipedrive Person requires an email for most API operations.

FIVE CRM Companies map directly to Pipedrive Organization records. Name is the dedupe key during import. Organization is created before any Person import so that the Person.organization_id lookup is satisfied at the moment of Person insert. Address, domain, and industry fields map where present.

FIVE CRM pipeline stages with custom labels map to Pipedrive Pipeline stages. During scoping, we enumerate every FIVE CRM pipeline stage label and agree on the equivalent Pipedrive stage name. Pipedrive allows multiple pipelines; if FIVE CRM has one pipeline, we create one Pipedrive Pipeline. If FIVE CRM has multiple pipelines, we create multiple Pipedrive Pipelines and map Deals accordingly.

FIVE CRM Deals map to Pipedrive Deals. Deal title, value, expected close date, and stage transfer directly. The FIVE CRM pipeline stage maps to the Pipedrive Pipeline stage value via the mapping agreed during scoping. Owner assignment resolves via email match to Pipedrive User. We flag Deals without a linked Company or Person for manual resolution before the migration inserts them.

FIVE CRM Campaigns track email marketing sequences and campaign membership. Pipedrive has no native Campaign object in its standard tiers. We map campaign membership to Pipedrive Tags on the associated Person record, with the tag name matching the FIVE CRM campaign name. Alternatively, the customer may choose to create a custom field campaign_name__c on Person and map membership there during scoping.

FIVE CRM tracks email engagement (opened, clicked, replied) at the individual contact level. Since FIVE CRM does not expose a bulk export endpoint for granular per-event logs, we migrate campaign membership and engagement status flags as custom fields on the Pipedrive Person (e.g., campaign_last_engaged__c, campaign_member_status__c). Full per-event history (timestamps of individual opens or clicks) cannot be migrated in this migration pattern.

FIVE CRM Task records map to Pipedrive Activity records of type Task. Due date, assignee, completion status, and subject transfer directly. Pipedrive Activity types (call, email, meeting, task, deadline) require type classification during mapping; FIVE CRM task types are enumerated during scoping and assigned to the nearest Pipedrive Activity type.

FIVE CRM call engagements map to Pipedrive Activity records of type Call. Call duration, disposition, and outcome transfer to custom fields on the Pipedrive Activity. Activity timestamps preserve the original FIVE CRM call time for timeline accuracy.

FIVE CRM email engagements map to Pipedrive Activity records of type Email. Email subject and body transfer to the Pipedrive Activity. Linked Person or Organization resolves via email address matching at migration time. We flag any email engagements attached to FIVE CRM records with no matching Pipedrive Person or Organization for manual link resolution.

FIVE CRM notes attached to Contacts, Companies, or Deals migrate to Pipedrive Notes linked to the equivalent Person, Organization, or Deal via the activity_id field. Note content migrates as plain text. We flag any notes exceeding Pipedrive's character limit for truncation or split handling.

FIVE CRM User records (names, emails, roles, assignment permissions) map to Pipedrive User records. We resolve by email match. Any FIVE CRM Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role discrepancies (FIVE CRM roles that have no Pipedrive equivalent) are documented for manual post-migration reassignment.