Migrate from erxes to HighLevel

erxes Contacts map directly to GoHighLevel Contacts. We extract standard fields (firstName, lastName, email, phone, position) and custom field values via GraphQL and import to GoHighLevel Contacts using the contacts API endpoint. Email serves as the dedupe key; duplicate emails trigger an update rather than a create. Custom fields require pre-creation in GoHighLevel before migration with matching field types (text, number, date, select) to avoid type mismatches.

erxes Company records map to GoHighLevel Companies. We extract companyName, industry, size, website, and address fields via GraphQL. Companies must import before Contacts so that the GoHighLevel companyId can be resolved and linked to Contact records during Contact import. The company domain serves as the dedupe key if domain normalization is needed.

erxes Deals map to GoHighLevel Opportunities. We extract dealName, amount, stage, pipelineId, and custom field values. The erxes pipelineId maps to a GoHighLevel Pipeline that we pre-create or match by name during schema setup. Stage names translate to GoHighLevel Pipeline Stage names, preserving order and probability percentages where they exist in erxes.

erxes Pipelines define the sales workflow stages for Deals. We map the full pipeline configuration including stage order, names, and probability mappings to GoHighLevel Pipelines. Each erxes pipeline becomes a GoHighLevel Pipeline; if the customer has multiple erxes pipelines, each maps to a separate GoHighLevel Pipeline with its own Stages configuration. Stage IDs are translated to destination stage IDs during Deal import.

erxes Tasks map to GoHighLevel Tasks. We extract task titles, descriptions, due dates, status (pending, in progress, complete), and owner assignments. Owner resolution uses email matching against GoHighLevel Users. Tasks attached to specific Deals link via GoHighLevel Opportunity ID lookup after Deal migration completes. Tasks attached to Contacts link via Contact ID lookup.

erxes multi-channel Conversations (email, SMS, chat, WhatsApp) require configuration-level mapping. The conversation body, metadata, and linked customer association migrate to GoHighLevel as structured notes attached to the related Contact or Company record. Message threading order is preserved by setting the GoHighLevel note createdAt timestamp to the original erxes server-side createdAt value. Channel-specific metadata (SMS sender ID, chat thread ID) migrates as custom note fields.

erxes custom fields on Contacts, Companies, and Deals require pre-creation in GoHighLevel before migration. We map field types: erxes text fields map to GoHighLevel text fields, erxes select fields map to GoHighLevel dropdown fields, erxes date fields map to GoHighLevel date fields. erxes has no type enforcement on ingest, so we validate each value against the defined field type and flag mismatches rather than writing invalid data to GoHighLevel.

erxes Users (team members) map to GoHighLevel Users by email match. We extract user records including name, email, role, and status. Role and permission configurations in erxes have no direct GoHighLevel equivalent, so we document the original permission structure for the customer's admin to reconfigure manually in GoHighLevel's team management settings. Inactive erxes users can be mapped to inactive GoHighLevel users or excluded based on customer preference.

erxes Channels define communication mediums (email, SMS, chat) connected to the platform. Channel credentials (API keys, webhook URLs, SMTP configurations) do not migrate because they are platform-specific secrets. We deliver a channel inventory document listing each erxes channel, its type, connected integration, and recommended GoHighLevel channel setup steps so the customer's admin can reconfigure the integrations after migration.