Migrate from HighLevel to Salesforce Sales Cloud

HighLevel Contacts with Lifecycle Stage of subscriber, lead, or marketing qualified lead map to Salesforce Lead. Lifecycle Stage of SQL, customer, or evangelist map to Salesforce Contact attached to an Account. We compute the split during migration using HighLevel's lifecyclestage property and preserve the original value in a custom field hl_original_lifecycle__c on both Lead and Contact for reporting continuity.

HighLevel Company records map to Salesforce Account. The Company name becomes the Account Name, and the domain (if present) populates the Website field as a dedupe reference. Account is created before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert.

HighLevel tags applied to Contacts migrate to Salesforce multi-select picklist fields on Lead and Contact. Tags used for campaign-style segmentation migrate to Salesforce Campaign with CampaignMember records linking the target Leads and Contacts. The customer chooses tag strategy during scoping based on whether tags drive reporting or purely serve as internal labeling.

HighLevel Opportunities map to Salesforce Opportunity. The Pipeline maps to a Salesforce Record Type and Sales Process; the Stage maps to StageName within that Sales Process. Dollar amounts migrate directly, and any custom opportunity fields (e.g., deal_source, referral_partner) map to custom Opportunity fields we provision before import.

HighLevel Pipelines map to Salesforce Opportunity Record Types. Each Pipeline's Stages become StageName values within a corresponding Sales Process. Probability percentages migrate from HighLevel to Salesforce StageProbability, rounded to the nearest integer. Multiple Pipelines per sub-account become multiple Record Types in Salesforce.

HighLevel Tasks linked to Contacts migrate to Salesforce Task with Status, Priority, ActivityDate, and description preserved. Assignment migrates by resolving HighLevel's hubspot_owner_id to Salesforce OwnerId via the User email lookup. Tasks without a valid owner are held in a reconciliation queue for the admin to resolve.

HighLevel Appointments migrate to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendee mapping creates EventRelation records linking to the migrated Lead, Contact, or User. Status (confirmed, cancelled) maps to ShowTime in Salesforce Event.

HighLevel Campaigns (email and SMS broadcast groupings) migrate to Salesforce Campaign as a naming and organizational container. Campaign metadata (name, description, associated contacts) migrates. Campaign performance metrics (open rates, click rates) and email/SMS content do not migrate via API; we flag these for manual re-creation or integration with Salesforce Marketing Cloud Account Engagement.

HighLevel Custom Objects migrate to Salesforce custom objects with API names preserved and a __c suffix. We pre-create the destination schema in a Salesforce Sandbox including all custom fields, picklist values, lookup relationships to standard objects (Contact, Account, Opportunity), and validation rules before any data moves. Custom object migration runs last after parent record lookups are resolved.

HighLevel Forms capture lead data and trigger automations. Form field mappings and structure are documented for manual re-creation in Salesforce Web-to-Lead or Experience Cloud. Form submissions themselves are captured as Lead records with the form name stored in a custom field.

HighLevel Landing Pages and Funnels are content artifacts rather than data records. We export the page structure and field mappings during discovery, then provide a written recommendation for Salesforce Experience Cloud Site or external hosting. The pages themselves are not migrated via API.

HighLevel Users (agency staff and client-level users within sub-accounts) map to Salesforce Users by email match. We extract all distinct users referenced on Contacts, Opportunities, Tasks, and Appointments and match them against the destination Salesforce org's User table. Missing users go to a reconciliation queue for the admin to provision before record import resumes.

HighLevel sub-accounts are data isolation boundaries with no direct Salesforce equivalent. For agency migrations, we map each sub-account to a separate Salesforce org, a Salesforce Division, or a Campaign-based segmentation strategy depending on the destination structure. This is the highest-severity architectural decision and is resolved during the discovery call.