Migrate from erxes to Pipedrive

erxes Contacts map directly to Pipedrive People. The firstName and lastName fields split from erxes combined name field. Email, phone, and custom property values migrate as custom fields on Person. The erxes contactId becomes a custom field pipedrive_migration_id__c on the destination record for deduplication if the migration is re-run or supplemented. We validate email format before insert since Pipedrive enforces email syntax on the Person object.

erxes Companies map to Pipedrive Organizations. Company domainName becomes the Organization's Website field. name becomes the Organization name. erxes companyId maps to pipedrive_migration_id__c on Organization. We create Organizations before People so that the Organization lookup on Person (visible in Pipedrive's Person detail view as a link to Organization) is satisfied at insert time.

erxes allows a Contact to be linked to multiple Companies via companyIds. Pipedrive People link to one primary Organization. We map the primary companyId (first in the list or flagged as primary) to the Organization link and store any secondary company associations in a custom field secondary_orgs__c as a comma-separated list for manual reconciliation in Pipedrive.

erxes Deals map to Pipedrive Deals with stage, amount, currency, owner, and custom fields preserved. The erxes pipelineId maps to a Pipedrive Pipeline we create or use based on the customer's pipeline configuration. Stage name maps from erxes stageName to Pipedrive stage. We set deal_value as the Pipedrive amount field and preserve any erxes custom field values as Pipedrive custom fields.

erxes Pipelines define the deal workflow stages. Each erxes pipeline becomes a Pipedrive Pipeline with stages ordered to match the erxes stage sequence. Stage probabilities migrate from erxes (probability field on each stage) to Pipedrive's stage probability. We configure Pipedrive Pipelines before Deals migrate so that stage assignments are valid at insert time.

erxes Tasks assigned to Users map to Pipedrive Activities. Task title becomes the Activity subject, description becomes the body, status maps to done (boolean) in Pipedrive, and due_date maps to due_date. Owner assignment resolves by matching erxes assignedBy to Pipedrive User via email lookup. Tasks with no due date migrate with no due date set.

erxes multi-channel Conversations cannot map to a single Pipedrive object because Pipedrive Activities do not store the full message content and channel metadata natively. We create a Pipedrive Activity (type determined by channel: email, call, meeting) as the timeline entry and attach a Note containing the conversation body, customer name, channel type, and timestamp. The conversation subject becomes the Activity subject. Message ordering is preserved by the original createdAt timestamp.

Pipedrive does not have custom objects. erxes custom objects require remapping: we identify the parent object (Contact, Company, Deal, or Task), create custom fields on that object in Pipedrive for each custom object field, and insert the values. If a custom object has lookup relationships to other objects, those associations are stored in a Note on the parent record with a structured prefix (CUSTOMOBJ:) for identification. The customer reviews the Note contents post-migration to determine if a relationship management tool or third-party integration is needed.

erxes Users map to Pipedrive Users by email address. We extract all distinct ownerIds and assignedBy values from Deals, Tasks, and Conversations and match against the destination Pipedrive User list by email. Any erxes user without a matching Pipedrive User goes to a reconciliation queue. The customer provisions missing Pipedrive Users before record migration continues because OwnerId is required on Deal and Activity insert.

erxes Channels define the connected communication mediums (email, SMS, chat, WhatsApp) with their API keys and webhook URLs. Channel credentials do not migrate because they are sensitive and platform-specific. We deliver a written inventory of every active Channel with its type, connected inbox or phone number, and a note that the customer must re-authenticate each channel in Pipedrive's settings or reinstall the relevant integration app from Pipedrive's marketplace.

erxes Automations define trigger-action sequences across Contacts, Companies, Deals, and Tasks. We extract the automation structure including trigger type, conditions, and actions from erxes but do not migrate them as code. Pipedrive's workflow builder (available on Advanced and above) uses a different trigger-action model. We deliver a written inventory of every active automation with its trigger, conditions, and actions, and a recommended Pipedrive workflow equivalent. The customer's admin rebuilds automations in Pipedrive post-migration.