Migrate from EspoCRM to HighLevel

EspoCRM Contacts map to GoHighLevel Contacts. The EspoCRM firstName and lastName split maps to GoHighLevel's firstName and lastName; email, phone, and address fields map 1:1. Custom fields on EspoCRM Contacts (including multi-enum fields capped at 20 options) migrate to GoHighLevel Contact custom fields. If the EspoCRM Contact has a linked Account, the Account name populates the GoHighLevel Company field on the Contact record.

EspoCRM Accounts map to GoHighLevel Company values stored on the Contact record rather than a separate Account object. We extract each distinct EspoCRM Account name, deduplicate, and map the Account-Contact relationship by writing the Account name into the GoHighLevel Contact's Company field. If the customer requires a dedicated company-level record in GoHighLevel for reporting, we discuss a Custom Object for Accounts as an optional configuration step.

EspoCRM Leads map directly to GoHighLevel Leads. Lead status, source, and assigned user fields migrate. The EspoCRM lead type and any custom lead classification fields map to GoHighLevel Lead custom fields. Note that EspoCRM's Lead conversion (which creates a Contact and Account) does not apply during data migration; we preserve the Lead as-is and the customer decides whether to convert in GoHighLevel post-migration.

EspoCRM Opportunities map to GoHighLevel Opportunities. Deal amount maps to Opportunity Value, stage maps to Pipeline stage, close date maps to Close Date, and probability maps to a custom field (GoHighLevel Opportunities do not have a native probability field but one can be added as a custom number field). The Opportunity-Contact link (primary contact on deal) maps to GoHighLevel's Opportunity contact association.

EspoCRM Opportunity stages map to GoHighLevel Pipeline stages. We extract the stage names and order from EspoCRM, create corresponding Pipelines in GoHighLevel, and assign stage names and ordering to match the source. Each EspoCRM pipeline becomes a separate GoHighLevel Pipeline within the Opportunities module.

EspoCRM Cases (support tickets) have no native GoHighLevel equivalent. We evaluate the customer's Case usage and map to either GoHighLevel Tasks (if Cases are primarily activity tracking) or a Custom Object named Cases with fields for status, priority, subject, and related Contact. The customer chooses the strategy during scoping based on whether Cases are used for ticket management or light activity tracking.

EspoCRM Campaigns map to GoHighLevel Campaigns. Campaign name, status, type, and start/end dates migrate. GoHighLevel Campaigns support linking to Contacts for tracking campaign membership. Note that email send history and email engagement metrics from EspoCRM do not migrate because GoHighLevel Campaign tracking starts fresh on the new platform.

EspoCRM Call activities map to GoHighLevel Tasks with the type set to Call. Call duration, disposition, and related Contact reference migrate. The original call date populates the Task due date for timeline ordering. Call recordings (stored as attachments on self-hosted EspoCRM) are extracted from the filesystem and uploaded to GoHighLevel Media Library, with the file URL stored in a custom field on the Task record.

EspoCRM Meeting activities map to GoHighLevel Appointments. Meeting title, start and end datetime, location, and related Contact or Opportunity reference migrate. The original meeting date and time are preserved in the Appointment record. Attendee information migrates as notes on the Appointment if the customer requires attendee history.

EspoCRM Task activities map to GoHighLevel Tasks with the type set to Task. Status (completed, not completed), priority, due date, and assigned user migrate. The original task date preserves activity timeline ordering in GoHighLevel's contact record timeline.

EspoCRM email activities migrate as timeline entries in GoHighLevel Contacts. Email subject, body, direction (sent or received), and timestamp migrate. The full email body is stored in a custom field or note attached to the Contact record. Note that GoHighLevel's email deliverability runs on shared Mailgun infrastructure (LC Email); we flag this in the gotchas and advise warming a dedicated sending domain post-migration.

EspoCRM Entity Manager custom entities map to GoHighLevel Custom Objects. We extract the entity definition metadata (field types, labels, relationships) during discovery, create the corresponding Custom Object schema in GoHighLevel (field types mapped: text to text, varchar to short text, int to number, decimal to number, date to date, datetime to datetime, enum to dropdown, multi-enum to multi-select, link-multiple to association). Up to 10 Custom Objects per location are available on all GoHighLevel plans as of the October 2025 release. Cross-entity relationships map to GoHighLevel object associations (1:1, 1:N, or N:N).

EspoCRM Documents and attachments on self-hosted instances are stored on the server filesystem under data/files/. We extract the referenced files during migration, upload each file to GoHighLevel's Media Library via the API, and store the resulting file URL in a custom field on the parent record (Contact, Opportunity, or Custom Object). File names and original upload dates are preserved in the custom field label. For cloud-hosted EspoCRM, attachments are referenced via the Attachment entity and migrated as file URL custom fields in GoHighLevel.

EspoCRM Users map to GoHighLevel Users by email match. We extract the EspoCRM user list (name, email, role, team membership) and match against GoHighLevel Users created during the account setup phase. Any EspoCRM User without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision. Role and team mapping is documented in the migration inventory for manual configuration in GoHighLevel's team settings.