Migrate from HighLevel to Microsoft Dynamics 365 Sales

HighLevel Contacts with no associated Opportunity and no assigned sales rep map to Microsoft Dynamics 365 Sales Lead. HighLevel Contacts linked to a Company and actively managed by a sales user map to Microsoft Dynamics 365 Sales Contact attached to the corresponding Account. The split is computed using HighLevel's tags, pipeline membership, and assigned user properties. The original HighLevel contact ID is preserved in a custom field hgl_contact_id__c on both Lead and Contact for reconciliation. Email opt-in status from HighLevel's subscription preferences migrates to HasOptedOutOfEmail on Contact.

HighLevel Companies map directly to Microsoft Dynamics 365 Sales Account. The Company name becomes Account Name; the primary phone and address fields map to standard Account fields. Account is created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. Companies without a contact association are imported as Accounts with no related Contacts for manual review.

HighLevel Opportunities map to Microsoft Dynamics 365 Sales Opportunity with Pipeline Stage, dollar amount, close date, and assigned owner preserved. The HighLevel pipeline and stage names are mapped to a Microsoft Dynamics 365 Sales Process and StageName values that we configure before migration. Closed-Won and Closed-Lost reasons from HighLevel custom fields migrate to corresponding custom Opportunity fields. Each Opportunity is linked to its parent Account via AccountId lookup resolved at migration time.

Each HighLevel Pipeline becomes a Microsoft Dynamics 365 Sales Record Type with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from HighLevel to the probability field on each Opportunity Stage entry. Stage ordering is preserved per pipeline mapping.

HighLevel Custom Objects migrate to Microsoft Dynamics 365 Sales custom tables via Dataverse. We introspect the HighLevel custom object's field schema before migration, map each field to the equivalent Dataverse column type (string to Text, number to Decimal or Whole Number, date to Date Only or DateTime), pre-create the destination custom table in the Dynamics 365 environment, then import data with lookup relationships resolved against parent Contacts and Accounts. Custom table API naming uses the standard Dataverse naming convention.

HighLevel Tasks linked to Contacts migrate to Microsoft Dynamics 365 Sales Task records. Subject, due date, status, priority, and assigned user (mapped via email to Dynamics 365 OwnerId) transfer directly. The Task's Regarding (WhatId) links to the related Account or Opportunity if a relationship exists in HighLevel.

HighLevel Appointments (scheduling module) map to Microsoft Dynamics 365 Sales Appointments with start time, end time, location, and assigned contact preserved. The appointment's scheduling link and calendar configuration are documented as a manual rebuild item in the destination system.

HighLevel Users referenced as owners on Contacts, Companies, and Opportunities are resolved by email match against the Microsoft Dynamics 365 Sales User table. Users without a matching Dynamics 365 User are placed in a reconciliation queue for the customer's admin to provision before record import resumes. Active status on the HighLevel User determines whether the Dynamics 365 User is set to active or inactive.

HighLevel tags are stored as a semicolon-delimited string in a custom text field on the target Contact or Account record. There is no native tag equivalent in Microsoft Dynamics 365 Sales . The customer chooses whether tags are preserved as a single text field or split into a multi-select picklist during scoping. Tag usage for Workflow triggers is documented separately for admin rebuild.

HighLevel file attachments linked to Contacts or Opportunities are extracted via HighLevel's file management API, uploaded to the linked SharePoint document library (Dynamics 365's native document storage), and attached via the Regarding lookup to the parent Contact, Account, or Opportunity record. Files exceeding 25MB are flagged for chunked upload with retry logic.