Migrate from Dynamics 365 Marketing to HighLevel

Dynamics 365 Contact records map to GoHighLevel Contact objects. We extract standard fields (full name, email, phone, address, company name) from the Dataverse contact table and import via GoHighLevel's Contacts API. The Dynamics 365 Contact-to-Account lookup is preserved as the GoHighLevel Contact's company association. We flag contacts that qualify as Marketing Contacts in Dynamics 365 for the customer's awareness during import because GoHighLevel bills contacts differently (by usage, not by marketing status).

Dynamics 365 Leads merge into GoHighLevel Contacts when the destination does not use a separate Lead object. We import Lead records with leadscore, leadstatus, and conversion data preserved as custom fields on the GoHighLevel Contact. Any Lead_Status values from Dynamics 365 are stored in a custom field for segmentation review in GoHighLevel. The original Lead creation date and owner are preserved for audit purposes.

Dynamics 365 Account records map to GoHighLevel Company records. Industry classification, address fields, and account hierarchy parent references transfer directly. Account custom fields and custom properties require pre-creation in GoHighLevel before import because GoHighLevel's custom field schema must be defined before data is written.

Dynamics 365 Opportunities map to GoHighLevel Opportunities. Pipeline stage, estimated close date, estimated value, probability, and owner assignment transfer directly. We create GoHighLevel pipeline stages that correspond to the Dynamics 365 sales process stage values before migration so that the Opportunity import resolves stage references correctly.

Dynamics 365 Campaigns map to GoHighLevel Campaigns. Campaign name, objective, target products, budget, start and end dates, and owner transfer. We preserve the campaign structure for historical reporting purposes. Active campaign tracking migrates with the understanding that ongoing campaign activity continues in GoHighLevel post-migration.

Dynamics 365 Marketing Lists containing member records map to GoHighLevel Tags or Groups depending on list size and intended use. We extract the marketing list membership (Contact IDs and Account IDs), re-associate each member with the corresponding GoHighLevel Contact or Company, and create the tag or group in GoHighLevel before importing membership records. Large lists with thousands of members are batched into API chunks to respect GoHighLevel rate limits.

Dynamics 365 activity records (Email, Task, PhoneCall, Appointment) stored in ActivityPointer and type-specific child tables map to GoHighLevel activity records. The regarding object lookup (Contact or Opportunity) is resolved at migration time by matching the Dynamics 365 record ID to the corresponding GoHighLevel Contact or Opportunity. Activity timestamps, disposition codes, duration, and notes body transfer directly. GoHighLevel's activity timeline uses a unified activity model versus Dynamics 365's split table model.

Dynamics 365 Annotations (notes with optional file attachments) map to GoHighLevel Notes. We export the note body as plain text or rich text, extract the file attachment as a blob, and re-associate it with the target Contact or Opportunity in GoHighLevel. Annotations are handled in a separate pass after the parent Contact and Opportunity records are confirmed in GoHighLevel.

Custom Dataverse entities created in a managed solution require pre-migration schema export from the Configuration Migration Tool. We do not infer custom entity structure from UI exports. Each custom entity field is defined in GoHighLevel as a custom field on the corresponding object (Contact, Company, or Opportunity) before any data import. Lookup relationships between custom entities require resolution ordering to ensure parent records exist before child records are written.

Marketing emails stored in the msdynmkt_email table (Customer Insights - Journeys schema) are not migratable as functional templates. GoHighLevel uses its own email template format with drag-and-drop builder. We extract the email subject and HTML body from Dynamics 365 and document the content for manual recreation in GoHighLevel's email builder. This is a written handoff, not an automated template migration, because template structures differ fundamentally between platforms.