Migrate from erxes to Salesforce Sales Cloud

erxes Contacts with no associated Company record or with a lifecycle indicator of 'prospect' map to Salesforce Lead. erxes Contacts with an associated Company record and a lifecycle indicator of 'customer' or 'active' map to Salesforce Contact attached to an Account. We apply the split rule at migration time using erxes custom property values, and preserve the original erxes contactId in a custom field erxes_original_id__c on both Lead and Contact for reconciliation.

erxes Company records map directly to Salesforce Account. The Company domain field maps to Account Website. We use erxes companyId as the externalId for deduplication during import. Account must be created before any Contact import so that the AccountId Lookup is satisfied at Contact insert.

erxes Deals map to Salesforce Opportunity. The erxes pipeline stage assignment maps to Salesforce StageName, and the pipelineId maps to a Salesforce Record Type and Sales Process that we configure before migration. Deal amount, close date, and ownerId migrate directly with the erxes ownerId resolved to the Salesforce OwnerId via User email matching.

Each erxes pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the stage values from the erxes pipeline. Stage probability percentages migrate from erxes to Salesforce StageProbability rounded to the nearest integer. We configure Page Layouts per Record Type so that stage-specific fields display correctly for each pipeline in the destination org.

erxes pipeline stages map to Salesforce Opportunity Stage values within the corresponding Sales Process. The stage order and probability are preserved. Any erxes stage with a closed-won or closed-lost status maps to Salesforce Closed Won or Closed Lost, with the erxes close reason stored in a custom field erxes_close_reason__c.

erxes Tasks migrate to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Task assignment migrates by resolving erxes ownerId to Salesforce OwnerId via User email matching. erxes Cycles and Teams do not have a direct Salesforce equivalent; we map cycle-based task grouping to a custom field erxes_cycle__c and flag team-assigned tasks with the erxes team name in a custom field erxes_team__c.

erxes Conversations split by channel during migration. Email messages migrate as Salesforce EmailMessage records linked to the parent Contact or Account via WhoId and WhatId. SMS, chat, and WhatsApp messages migrate as Task records with TaskSubtype=Chat and the original channel stored in a custom field erxes_channel__c. Message ordering is preserved using the original erxes server timestamp (createdAt) as ActivityDate.

erxes Users migrate to Salesforce User records by email match. We resolve every distinct erxes ownerId referenced on Contact, Company, Deal, Task, and Conversation records and match against the Salesforce org's User table. Users without a matching Salesforce User are held in a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission configurations require manual review post-migration because erxes role models do not map directly to Salesforce Profiles and Permission Sets.

erxes custom fields on Contacts map to Salesforce custom fields on Lead and Contact with type mapping: erxes text fields become Text (255), long text become TextArea, date fields become Date, number fields become Number, and select fields become Picklist. We validate field types against erxes field definitions before import because erxes does not enforce type constraints on ingest—a text field in erxes may contain a date value that Salesforce would reject on a Date field. Any type mismatches are flagged and mapped to Text fields in Salesforce to prevent import failures.

erxes custom fields on Companies map to Salesforce custom fields on Account with the same type-mapping logic as Contacts. We validate erxes field definitions against Salesforce field types before import. Any custom fields referencing erxes-specific picklist values are mapped to Salesforce Picklist with the same value set or to Text if the value set does not fit a picklist model.

erxes custom fields on Deals map to Salesforce custom fields on Opportunity with type validation. We map all custom field values and preserve the erxes field label in the Salesforce field description for admin reference.

erxes Channels define communication mediums (email, SMS, chat, WhatsApp) connected to the platform. Channel credentials such as API keys, webhook URLs, and third-party service tokens do not migrate. We flag every Channel for manual reconfiguration in Salesforce Omni-Channel or email routing rules post-migration. The channel type (email, SMS, chat, WhatsApp) is preserved as a custom field on the migrated Conversation records.