Migrate from X2CRM to Pipedrive

X2CRM Contacts map 1:1 to Pipedrive People. Standard fields (name, email, phone, address) migrate directly. We resolve the email address as the dedupe key during import to prevent duplicate Person records. Custom contact fields from X2CRM map to Pipedrive custom fields on Person, which we pre-create via the Pipedrive API before the Person import phase begins.

X2CRM Accounts (companies and organizations linked to Contacts) map 1:1 to Pipedrive Organizations. We preserve associated tags, lifetime value, and linked Contact relationships by resolving the Account ID against the Contact mapping table. Organization is created before Person import so that each Person's org_id reference is satisfied at insert time.

X2CRM Deals track stage, value, probability, and expected close date, all of which map directly to Pipedrive Deal fields (stage_id, value, success_probability, close_date). Pipeline stage mappings are configured in Pipedrive before migration. Deal owner maps to the Pipedrive User resolved by email match from the X2CRM User table.

Each X2CRM Deal pipeline becomes a Pipedrive Pipeline with stages configured to match the source stage names, probabilities, and order. We create Pipedrive pipelines via the API before any Deal records are imported. Closed-Lost and Closed-Won stage names in X2CRM map to Pipedrive's corresponding stage designations.

X2CRM Products (catalog items with pricing, SKU, and description) map 1:1 to Pipedrive Products. We migrate product code, name, unit price, and description. If X2CRM Products are associated with Deals as line items, we create Pipedrive Deal-Product associations during the Deal import phase using Pipedrive's dealProducts endpoint.

X2CRM Services track recurring service contracts or subscriptions linked to Accounts, with status, renewal dates, and associated Account links. Pipedrive has no native Services object. We map Services to Deals with a custom field service_type__c (picklist: Subscription, Contract, Support, Maintenance) and renewal_date__c to preserve the renewal date context. The customer chooses the target Pipeline and stage during scoping.

X2CRM Campaign records (name, type, status, associated mailing lists) have no native Pipedrive equivalent. We migrate Campaign records as Activity records with a custom field campaign_name__c and campaign_type__c for reference. Email campaign templates migrate as static HTML content notes. We document campaign structure in the handoff report so the customer's admin can recreate Pipedrive Email Campaigns if they have the Marketing add-on.

X2CRM Activities (calls, meetings, tasks) with timestamps, owners, and related Contacts or Deals map to Pipedrive Activities. Each activity type maps to its Pipedrive Activity subtype: Task for tasks and logged calls, Meeting for calendar entries. We preserve chronological ordering by setting the activity date to the original X2CRM timestamp. Owner resolution uses the User email mapping established during discovery.

X2CRM Tags are standalone label records applied across multiple object types. Pipedrive does not have a native global tag object. We preserve tag associations by creating a custom multi-select picklist field on Person and Organization (tagged_contacts__c, tagged_organizations__c) and reapplying tag labels post-import. The customer selects tag strategy during scoping, as some teams prefer to use Pipedrive's label feature or List membership instead.

X2CRM User accounts (name, email, role, assignment permissions) are exported during discovery. We resolve each X2CRM user by email against the Pipedrive destination User table. Role configurations (viewer, editor, admin) are documented in the handoff report for the Pipedrive admin to reconfigure under Settings > Users & Permissions because Pipedrive's permission model (regular, admin, api) is distinct from X2CRM's role-gated access tiers.

X2CRM custom fields added via the module builder vary by module and require per-field mapping during scoping. We inspect the X2CRM field schema via API discovery and align each custom field to the equivalent Pipedrive custom field, pre-creating destination fields before migration. Picklist fields with specific value sets are replicated as Pipedrive drop-down options; date fields map to Pipedrive date fields; numeric fields map to number fields with appropriate formatting.