Migrate from Dynamics 365 Marketing to HubSpot

Dynamics 365 Accounts map directly to HubSpot Companies. Account.Name becomes Company name. HubSpot's primary-company model differs from Dynamics 365's required AccountId on every Contact — we resolve the primary company by account role or most-recent modification date. This ensures accurate company attribution for reporting.

Contact maps 1:1 to HubSpot Contact. Email is the deduplication key. We preserve Contact.fullname as FirstName + LastName split, phone, jobtitle, and all address components. Dynamics 365's createdon and modifiedon timestamps migrate as custom datetime properties for reporting continuity across systems.

Dynamics 365 Leads with status 'Open' or 'Qualified' that were not converted to Contacts map to HubSpot Contacts with lifecycle_stage set to 'lead'. Leads that converted to Contacts already exist in the Contact table and do not duplicate and are retained for audit.

Opportunity maps to HubSpot Deal. Opportunity.name becomes Deal name; estimatedvalue maps to amount; estimatedclosedate maps to closedate; statecode/stagecode maps to dealstage. HubSpot deal pipelines are separate from the Deal object — we map each Dynamics 365 Opportunity's salesstage to a corresponding HubSpot pipeline stage.

Dynamics 365 parentaccountid creates a parent-child account hierarchy. HubSpot Companies support a single parent_company_id field. We map the top-level parent account first, then resolve child accounts referencing their parent. Circular references (if any) are flagged for manual resolution and are documented in the migration report for your team to address before final load.

Dynamics 365 Marketing Lists are entity-specific (Contact, Account, or Lead lists). Each list migrates as a HubSpot static list. Dynamic marketing lists require HubSpot's list-filter equivalent to be rebuilt — we export the filter criteria as JSON for your HubSpot admin.

Dynamics 365 Campaigns carry journey logic, multi-channel execution records, and campaign activity history. HubSpot Campaigns track email campaign performance only. We migrate the campaign name and description as a custom object for reference; the campaign structure and customer journeys must be rebuilt in HubSpot.

Dynamics 365 Products (with product hierarchy, pricing, and unit groups) map to HubSpot Products. Product.name, productnumber, and defaultuomscheduleid (unit of measure) transfer. Bundle and product family structures become HubSpot product categories. Pricing lists and unit groups are preserved, and any associated product relationships are mapped accordingly.

Each Opportunity Product line item in Dynamics 365 maps to a Deal Line Item in HubSpot. Quantity, unit price, manual discount, and product lookup resolve against the migrated Product records. If the product does not exist, the line item is created without the product link and flagged for review.

Dynamics 365 Notes (notemime = 'text/html') migrate as HubSpot Notes with creation timestamp and owner preserved. File attachments (annotation_documentbody) download, re-upload to HubSpot Files, and attach to the corresponding contact, company, or deal record. Ensuring that attachment metadata, such as file size and original filename, is retained in HubSpot's file manager.

Dynamics 365 activities map to their HubSpot equivalents: Email -> Email, Task -> Task, PhoneCall -> Call, Appointment -> Meeting. We preserve subject, description, regardingobjectid (linked record), createdon, and owner. Activity party records (attendees, recipients) resolve by email to HubSpot contacts.

Dataverse custom tables migrate as HubSpot custom objects if they have a relationship to Contact or Company. Standalone custom tables without HubSpot equivalents become custom properties on the primary contact/company record. N:N relationships in Dataverse may require HubSpot custom junction objects.