Migrate your erxes data

Contacts are the primary customer records in erxes with standard fields for name, email, phone, and custom properties. We migrate Contacts 1:1 and preserve all custom field values as property mappings on the destination side.

Companies represent business accounts that can be associated with multiple Contacts. We map Company records and their linked Contacts, maintaining the association through the companyId reference in the destination schema.

Deals are erxes' opportunity records tied to Pipelines and Pipeline Stages. We preserve deal amounts, stage assignments, and custom fields during migration, mapping pipeline IDs to the destination pipeline structure.

Pipelines define the sales workflow stages. We map the full pipeline configuration including stage order, names, and probability mappings. Stage IDs are translated to destination IDs during import.

Tasks are work items that can be assigned to Users and organized into Teams and Cycles. We migrate task titles, descriptions, due dates, and status, preserving owner assignments via userId mapping.

Conversations capture multi-channel customer messages across email, SMS, chat, and WhatsApp. The conversation body, metadata, and customer association migrate, but message threading order may require validation against destination timestamps.

Automations define trigger-action sequences for customer journeys. We extract the workflow structure including triggers, conditions, and actions, but complex conditions referencing object IDs may need reconfiguration on the destination platform.

Custom fields can be defined on Contacts, Companies, Deals, and Tasks. We migrate the field schema and values, but field type mapping (text vs. select vs. date) must be verified against the destination field configuration.

Users represent team members with roles and permissions. We migrate user records and map them to the destination system, but role and permission configurations often require manual review due to platform-specific access control models.

Channels define the communication mediums (email, SMS, chat) connected to the platform. Channel credentials (API keys, webhook URLs) do not migrate—we flag these for manual reconfiguration to avoid credential exposure.