Migrate from Exsalerate to HighLevel

Exsalerate Accounts map directly to GoHighLevel Locations, which serve as the Account equivalent in GoHighLevel's data model. We preserve account name, address fields, owner assignment, and custom properties. Location is created before any Contact import so that the Contact-Location lookup relationship is satisfied at the moment of insert. GoHighLevel's Location object supports multiple addresses per record which Exsalerate does not — we map the primary address from Exsalerate and flag any additional addresses for manual enrichment post-migration.

Exsalerate Contacts map to GoHighLevel Contacts with the parent Location reference resolved at migration time. We preserve first name, last name, email, phone, title, owner assignment, and custom field values. GoHighLevel Contacts support tags, custom fields, and a built-in contact scoring model — we map Exsalerate's custom field values to GoHighLevel's equivalent field types and create any missing custom fields in GoHighLevel before import.

Exsalerate Opportunities map directly to GoHighLevel Opportunities. We preserve opportunity name, value (monetary amount), expected close date, owner assignment, and stage. The Exsalerate pipeline-stage linkage maps to GoHighLevel's pipeline and stage assignment, which we configure in GoHighLevel before migration. If Exsalerate opportunity records carry a WorkflowMax quote cross-reference, we store that in a GoHighLevel custom text field.

Exsalerate Pipelines (named top-level containers for sales activity) map to GoHighLevel Pipelines, which we configure from scratch in GoHighLevel's Pipeline builder. The Exsalerate pipeline name becomes the GoHighLevel pipeline name. If the customer uses multiple named pipelines in Exsalerate (for different service lines or business units), we create a corresponding Pipeline in GoHighLevel for each one. GoHighLevel's Pipeline builder supports stage probability percentages, which we map from Exsalerate stage values.

Exsalerate Pipeline Stages (ordered labels within a Pipeline) map to GoHighLevel Pipeline Stages. We preserve the stage order, label text, and Exsalerate's colour-coding metadata as a custom field in GoHighLevel since GoHighLevel Stages do not natively support colour attributes. Stage-level automation triggers in Exsalerate do not migrate — we document them as part of the automation inventory for rebuild in GoHighLevel's workflow builder.

Exsalerate To-Do Items (colour-coded activity tiles) map to GoHighLevel Tasks or Activities. We preserve due date, status, owner assignment, and description. Exsalerate's colour-coding (which signals urgency and context) has no native GoHighLevel equivalent — we capture the colour value in a GoHighLevel custom field on the Task record. If GoHighLevel's Starter plan does not expose a custom field UI for Tasks at no extra cost, we discuss the customer's plan tier before committing this mapping approach.

Exsalerate email history (associated to Accounts and Contacts) migrates to GoHighLevel as Contact Activity records or as notes on the Contact. We preserve subject, body, timestamp, sender, and recipients. Attachments are handled as a separate file migration linked to the Contact record. Email threading relationships from Exsalerate do not have a direct GoHighLevel equivalent and are not preserved.

Custom fields on Accounts, Contacts, and Opportunities in Exsalerate migrate to GoHighLevel custom fields with field-type awareness applied. Picklist values, date formats, numeric precision, and text formats are normalised at import. GoHighLevel custom fields are available on all paid plans. We pre-create all required custom fields in GoHighLevel before data import begins. Any custom field that cannot be type-matched is flagged during scoping and stored as a text field with the original value preserved.