Migrate from Sage CRM to HighLevel

Sage CRM Companies are the primary account object, holding address, industry, and classification data. They map directly to GoHighLevel Locations (the account-level object) with address, website, and custom fields preserved. We use the Sage CRM CompanyName as the Location name and the company domain as the website field. Location is created before any Contact import so that the relationship field is satisfied at Contact insert time.

Sage CRM Contacts link to Companies via PrimaryCompanyLink and carry personal details, role, phone, email, and custom fields. They map to GoHighLevel Contacts with name, email, phone, and address preserved. We resolve the PrimaryCompanyLink to the corresponding GoHighLevel Location ID before import. Sage CRM custom Contact fields migrate as GoHighLevel Contact custom fields, though note that GoHighLevel field types (text, number, date, dropdown) must be specified in advance and cannot be changed post-creation.

Sage CRM uses a separate Lead entity distinct from Contacts, with its own lifecycle stages, qualification fields, and source tracking. GoHighLevel does not have a separate Lead object; all people records are Contacts. We map Sage CRM Lead records to GoHighLevel Contacts with a custom field leaddatasource__c carrying the original lead source and a status__c value indicating that the record was imported as an unqualified prospect. The customer's admin sets the intake pipeline stage in GoHighLevel during post-migration configuration.

Sage CRM Opportunities track pipeline stages, revenue amounts, expected close dates, and owner assignments with custom fields and multi-currency amounts. They map to GoHighLevel Opportunities with name, value, stage, expected close date, and owner preserved. The Sage CRM pipeline and stage map to a GoHighLevel Pipeline and stage via configuration before migration. Closed-Lost and Closed-Won reasons from Sage custom fields become GoHighLevel custom fields for loss reason and win reason tracking.

Each Sage CRM pipeline with its stages becomes a GoHighLevel Pipeline with corresponding stages. Stage names, probabilities, and ordering migrate from Sage to GoHighLevel. We configure the pipeline in GoHighLevel during the pre-migration phase so that Opportunities can be assigned to the correct pipeline on import.

Sage CRM Cases have severity, status, assignment, and threaded Communications. GoHighLevel has no native Case object. Service-type records are typically mapped to GoHighLevel Opportunities in a dedicated service pipeline (for billable support matters) or to Tasks with a custom case reference field (for non-billable support items). The customer chooses the mapping strategy during scoping based on whether cases are transactional or informational.

Sage CRM Communications (email, call logs, meeting notes) live in the entity-agnostic Communication table linked to entity IDs (Company, Contact, Lead, Opportunity, or Case). We export Communications grouped by parent entity type and ID, then insert them as GoHighLevel Tasks with the corresponding Contact or Opportunity linked. Call logs become Tasks with a custom call duration field; meeting notes become Tasks with location and description; email summaries become Tasks with the email body preserved.

Sage CRM Custom Entities have display names and internal table names (e.g., CustomEntityname) referenced by API. GoHighLevel has no Custom Object equivalent, so we map each Custom Entity to either GoHighLevel Contact custom fields (if the entity is person-attribute data) or GoHighLevel Opportunity custom fields (if the entity is deal-attribute data). Transaction-like Custom Entities with their own lifecycle map to Opportunities in a dedicated pipeline. We inspect the entity schema via the Sage CRM API model service and cross-reference with the UI display name to build an accurate entity map before migration scoping.