Migrate from CRM Service to HighLevel

CRM Service Accounts map to GoHighLevel Contacts with the Account Name stored in the Contact's Company field. We preserve the original Account.Id as an external reference in a custom field crm_account_id__c for audit traceability. Industry, AnnualRevenue, and BillingAddress from the Account map to custom fields on the GoHighLevel Contact. If multiple CRM Service Contacts share the same Account, they become separate GoHighLevel Contacts sharing the same Company name value, which GoHighLevel uses as its primary company grouping mechanism.

CRM Service Contacts map directly to GoHighLevel Contacts. The Email field is the dedupe key. We preserve FirstName, LastName, Phone, MobilePhone, Title, Department, and the Contact's custom __c fields. The CRM Service Contact's AccountId resolves to the Company field on the GoHighLevel Contact via the Account mapping above. Lifecycle stage or lead status from CRM Service maps to GoHighLevel's Lifecycle Stage property if available, or to a custom dropdown field.

CRM Service Leads have no separate GoHighLevel object equivalent. We merge all Lead records into GoHighLevel Contacts, storing the original LeadSource, Status, Rating, and IsConverted flag as custom fields on the Contact record. The CRM Service Lead.Id is preserved as lead_original_id__c. If the lead was already converted in CRM Service, the corresponding Contact record (from step 2) inherits the conversion data; if not converted, the Contact is created with IsConverted=false stored as a custom field.

CRM Service Opportunities map to GoHighLevel Opportunities. The Opportunity Name, Amount, CloseDate, StageName, Probability, and Description migrate directly. The CRM Service Opportunity.AccountId resolves to the GoHighLevel Opportunity's Contact lookup (via the Account-Contact merge). StageName values are mapped to GoHighLevel Pipeline Stage names that we configure before migration. ForecastCategory migrates as a custom field if the customer requires it.

CRM Service Opportunity stages (mapped via the Sales Process and Record Type) are translated to GoHighLevel Pipeline stages. We define the stage mapping during scoping by extracting all distinct StageName values from the CRM Service org and matching them to existing or new GoHighLevel Pipeline stages. Stage probabilities migrate from CRM Service to GoHighLevel stage probability settings.

CRM Service custom objects have no direct GoHighLevel equivalent because GoHighLevel does not support custom object creation at any plan tier. We decompose each custom object by identifying its most related standard CRM Service object (typically Account or Opportunity) and migrate its fields as custom fields on the corresponding GoHighLevel Contact or Opportunity. Lookup relationships within custom objects are preserved as custom text fields holding the referenced record ID or name.

CRM Service Products map to GoHighLevel Products if the customer uses GoHighLevel's built-in product and invoicing features. ProductCode, Name, Description, and StandardPriceBook pricing migrate. If GoHighLevel's product module is not in active use, we skip product migration and document the exclusion in the scoping report.

CRM Service Tasks map to GoHighLevel Contact Activity entries. Task.Subject, Status, Priority, ActivityDate, and Description migrate to GoHighLevel's activity log on the associated Contact record. We resolve the Task.WhoId (Contact or Lead) to the GoHighLevel Contact via email match, and Task.WhatId (Opportunity or Account) is stored as a custom reference field.

CRM Service Events (meetings) map to GoHighLevel Contact Activity entries with Type=Meeting. StartDateTime, EndDateTime, Subject, and Location migrate. Attendees from the EventRelation table are stored as a comma-separated list in a custom activity notes field on the GoHighLevel Contact activity log entry.

CRM Service EmailMessage records (and related Task entries for email activities) migrate to GoHighLevel Contact Activity log entries with Type=Email. Subject, Body (plain text or HTML stripped), MessageDate, and FromAddress/ToAddress migrate. The email is stored as an activity entry on the GoHighLevel Contact.

CRM Service Campaign membership (CampaignMember records linking Contacts to Campaigns) migrates as a Tag on each GoHighLevel Contact. Campaign.Name becomes the tag value. If the customer runs multiple simultaneous campaigns, we store campaign names as comma-separated tag values. The customer chooses between tag and custom field during scoping based on reporting needs.

CRM Service Cases have no direct GoHighLevel equivalent. We assess the Case volume and customer intent: if Cases are primarily reference notes, they migrate as GoHighLevel Contact Activity entries. If Cases represent a core operational workflow (support tickets), we document the Case-to-GoHighLevel migration pattern and recommend using GoHighLevel's pipeline features to replicate Case status as an Opportunity pipeline, or using a dedicated helpdesk integration post-migration.