Migrate from eSalesTrack to HighLevel

eSalesTrack Contact records map directly to GoHighLevel Contact. The Contact's email address serves as the primary dedupe key. We resolve any eSalesTrack owner_id references against GoHighLevel User records by email match. Unmatched owners are held in a reconciliation queue for the customer's admin to provision GoHighLevel team members before record insert resumes. Contact phone, address, and custom properties map to GoHighLevel custom fields which we pre-create during schema setup.

eSalesTrack Account records map to GoHighLevel Company. The Account name becomes the Company name, and the Account domain or website URL becomes the Company website field. Company is inserted before Contact import so that the Contact-to-Company relationship (the contact belonging to a specific Company) is satisfied at the moment of Contact insert.

eSalesTrack Lead records do not have a direct GoHighLevel equivalent because GoHighLevel does not maintain a separate Lead object by default. We migrate eSalesTrack Leads as GoHighLevel Contacts with a custom tag or custom field (lead_source__c) set to the original eSalesTrack Lead source. This preserves the lead capture context without requiring a separate object in GoHighLevel. The customer can configure a GoHighLevel pipeline and workflow to handle lead-stage progression if needed post-migration.

eSalesTrack Opportunity records map to GoHighLevel Deals. The Opportunity name becomes the Deal name, and the eSalesTrack deal amount and close date map to GoHighLevel Deal value and close date fields. The eSalesTrack pipeline and stage assignment maps to a GoHighLevel Pipeline that we configure during schema setup, with stage names and probabilities aligned to the original eSalesTrack pipeline structure. Deal owner resolves by email against GoHighLevel Users.

eSalesTrack pipelines with their stage names and stage order migrate to GoHighLevel Pipeline configuration. Each eSalesTrack pipeline becomes a separate GoHighLevel Pipeline board with stages that match the original stage names. Stage probability percentages (if present in eSalesTrack) transfer to GoHighLevel stage probability fields. Pipeline is configured in GoHighLevel before Deal import begins so that Deals can be assigned to the correct pipeline during migration.

eSalesTrack Owner records map to GoHighLevel User accounts. We match by email address (the standard identifier in both platforms). If a GoHighLevel User account does not exist for an eSalesTrack Owner, the Owner is flagged in the reconciliation report with the action required: provision a GoHighLevel User with that email address before re-running the migration phase. Owner assignment on Deals and Contacts resolves after User matching is confirmed.

eSalesTrack call logs map to GoHighLevel Activity records with type set to Call. Call duration, disposition, and outcome migrate to GoHighLevel Activity fields. The Activity is linked to the parent Contact or Deal using GoHighLevel's relationship model. We preserve the original timestamp so the activity timeline reflects the actual call date.

eSalesTrack email engagement records map to GoHighLevel Activity records with type set to Email. Email subject and body migrate to the Activity content field. The Activity is linked to the parent Contact. If eSalesTrack captures email direction (sent or received), we preserve that as a custom field or activity tag. Email attachments migrate as notes linked to the activity.

eSalesTrack Notes attach to the parent record (Contact, Account, or Opportunity) and migrate to GoHighLevel Note records. We link each Note to the corresponding Contact or Deal using GoHighLevel's object relationship. Note content and creation date preserve. Notes from engagement-type records that have no direct GoHighLevel equivalent attach to the related Contact for timeline visibility.

eSalesTrack custom fields on Contact, Account, and Opportunity migrate to GoHighLevel custom fields. We pre-create the GoHighLevel custom fields during schema setup, matching field type where possible (text to text, number to number, date to date, picklist to dropdown). Any eSalesTrack custom fields that do not have a native GoHighLevel equivalent are created as text fields and flagged in the mapping document for the customer to review post-migration for potential re-typing or re-configuration.