Migrate from Microsoft Dynamics 365 Sales to HighLevel

Dynamics 365 Account maps 1:1 to GoHighLevel Company. The primary Account name becomes Company name; Address fields map directly. The primary Contact association on the Account migrates as a separate Contact record with the Company assigned. If the source Account has no primary Contact, we create a placeholder contact record with the Account's address data. Account owner maps to the GoHighLevel assigned user on the Company record.

Dynamics 365 Contact maps directly to GoHighLevel Contact. We preserve email, phone, address, job title, and the parent Account lookup as the GoHighLevel Company assignment. Contact ownership maps to the assigned user in GoHighLevel. Lifecycle stage or status fields from Dynamics custom fields become GoHighLevel Contact custom fields of the corresponding type.

Dynamics Lead requires a split decision. Leads with qualification status (qualified, converted) map to GoHighLevel Contact records with Opportunity data (deal name, estimated value, close date) created as an associated GoHighLevel Opportunity. Unqualified Leads map to GoHighLevel Contact with a lead_source custom field capturing the original Dynamics Lead source attribution. We use the leadscore and leadqualityscore custom fields from Dynamics to populate a custom field in GoHighLevel if the customer has those configured.

Dynamics 365 Opportunity maps to GoHighLevel Opportunity. The opportunityname becomes the Deal name; estimatedvalue maps to the GoHighLevel Opportunity value field; closedate maps to the GoHighLevel Pipeline start date or custom close date field. Pipeline stage from Dynamics maps to a GoHighLevel pipeline Status value. The parent Account reference resolves to the GoHighLevel Company lookup. Loss reason and win reason from Dynamics custom fields become GoHighLevel Opportunity custom fields.

Dynamics 365 deal pipelines (defined per entity with record types and sales processes) map to GoHighLevel Pipelines. Each Dynamics stage with its probability percentage becomes a GoHighLevel Pipeline stage with a corresponding probability. We configure the GoHighLevel pipeline before migration so that stage mapping is deterministic at import time. If the Dynamics environment has more than one pipeline, we map each to a separate GoHighLevel Pipeline and note the mapping in the migration inventory.

Dynamics 365 Quotes, Orders, and Invoices form a document chain with line items. GoHighLevel Opportunities do not have native quote or order objects. We map Quote header fields (quote number, total amount, status) to GoHighLevel Opportunity custom fields, and the line items (product name, quantity, unit price) map to a GoHighLevel custom field or a sub-object if the customer uses GHL's product catalog. Invoice-level data maps to Opportunity custom fields. If the customer requires strict quote or invoice preservation, we document the gap and recommend GHL's built-in invoice and proposal tools as the replacement.

Dynamics 365 Products map to GoHighLevel Products if the customer uses GHL's product catalog. The product name, SKU (productnumber), and default price migrate. Price list assignments are not a native GoHighLevel concept; we map the default price list price as the GoHighLevel product price and flag any alternative price list prices as custom fields for the customer to manage in GHL pricing tools.

Dynamics 365 Tasks map to GoHighLevel Tasks attached to the matching Contact or Opportunity via the email or record reference. Emails migrate as GoHighLevel Notes with an email type marker. Appointments and Phone Calls from Dynamics map to GoHighLevel Tasks with type custom fields distinguishing the activity type. The activity date and owner migrate; the owner resolves via email match to a GoHighLevel user. If the original Dynamics owner is inactive, we map to the designated migration admin account.

Dynamics 365 Notes migrate as GoHighLevel Notes linked to the parent Contact or Opportunity. We extract note body as plain text and preserve the created-on timestamp. SharePoint-stored attachments from Dynamics require the customer to provide the SharePoint location; we download and attach as files to the corresponding GoHighLevel record. Attachments stored in Dataverse blob storage migrate similarly.

Dynamics 365 Users map to GoHighLevel Users by email match. We run a pre-migration audit of all Owner IDs referenced across Account, Contact, Opportunity, and Activity records. Any Dynamics owner without a matching GoHighLevel user (inactive or unlicensed) is mapped to a designated migration admin account or an inactive-owner placeholder. The customer's GoHighLevel admin provisions users before migration begins.