Migrate from Microsoft Dynamics 365 Sales to HubSpot

Dynamics Account maps directly to HubSpot Company. Company name, website, address fields, industry, employee count, and annual revenue transfer as-is. HubSpot does not have a separate parent-account hierarchy in the same way as Dynamics — parent-child relationships map via HubSpot association labels.

Dynamics Contact maps one‑to‑one to HubSpot Contact, preserving standard fields such as full name, email, phone, job title, and address. Owner resolution matches Dynamics OwnerId email to an existing HubSpot user; unmatched records are flagged for manual assignment before migration. Dynamics StateCode (active/inactive) translates to the corresponding HubSpot lifecycle stage, ensuring active contacts land in the correct lifecycle state.

Dynamics Lead maps to HubSpot Contact, not a separate lead object. Unconverted Leads land in HubSpot at the lifecycle stage you specify (typically 'lead' or 'MQL'). Dynamics StateCode=1 (Qualified) routes to lifecycle stage 'SQL'. We preserve the original Lead creation date as a custom datetime field.

Dynamics Leads that were never converted split into HubSpot contacts at the 'lead' lifecycle stage. We apply a configurable routing rule based on Lead StateCode and StatusCode so your HubSpot lifecycle distribution reflects your original Dynamics pipeline state at migration time.

Dynamics Opportunity maps to HubSpot Deal. Deal name, amount, close date, probability, and owner transfer directly. Dynamics stepname (business process flow stage) maps to a HubSpot deal pipeline stage — each Dynamics pipeline with its own business process flow becomes a separate HubSpot deal pipeline.

Dynamics stores pipeline stage as stepname within a business process flow, not on the Opportunity itself. We extract stepname per Opportunity and map it to the corresponding HubSpot deal stage in the target pipeline. Stage entry dates map to HubSpot deal stage history timestamps.

Dynamics tasks (phone calls, follow-up tasks) map to HubSpot engagements on the contact timeline. Original timestamps, owners, and subject lines transfer. Task Regarding (linked record) maps to HubSpot's association model so the activity appears on the correct contact or deal.

Dynamics email activities map directly to HubSpot email engagements, preserving sender, recipient, subject, body (plain text or HTML), and sent timestamp. Direction (inbound or outbound) is recorded using HubSpot's email direction property. Tracking events such as opens and clicks from Dynamics appear as HubSpot email events on the contact timeline, maintaining engagement history. Attachments in Dynamics emails are stored as HubSpot file links on the engagement record.

Dynamics phone call records map to HubSpot call engagements, preserving the call subject, duration, direction (inbound or outbound), and the CallOutcome field. Call duration and direction are displayed on the HubSpot contact timeline for accurate activity reporting. If Dynamics stores a call recording URL, it is transferred as a custom property on the HubSpot engagement so users can replay the conversation directly from the record.

Dynamics notes attached to any record such as Account, Contact, or Opportunity are mapped to HubSpot notes on the corresponding contact or deal, preserving note body, author, and file links. The note-created and note-modified timestamps transfer to HubSpot as datetime properties, maintaining an audit trail for compliance. Attachments referenced in Dynamics notes are linked as HubSpot file references so users can access the original documents from the HubSpot record.

Dynamics custom tables in Dataverse map 1:1 to HubSpot custom objects. All custom fields transfer as HubSpot custom properties. Lookup relationships from custom entities to Account or Contact map to HubSpot association labels — many-to-many junction tables become HubSpot many-to-many association types.

Dynamics Product catalog entries — including product name, product number, default unit price, and quantity — map to HubSpot products, where they become available for line items on deals. Each HubSpot product can be associated with deals via line items, allowing revenue calculations. When Dynamics contains price lists, we create a value‑mapping table that translates each Dynamics price list price to the HubSpot product price, ensuring pricing is applied during migration.

Dynamics OwnerId (user or team) resolves by email match to HubSpot users. Records owned by Teams route to a designated HubSpot user or queue. Unmatched owners are flagged before migration — your team either creates HubSpot users or reassigns records before the full run.

Dynamics Opportunity Competitors lack a native HubSpot counterpart, so we capture each competitor name as a multi-select custom property on the HubSpot Deal. The property stores the list of competitors associated with the opportunity, preserving competitive intelligence context for the deal. If Dynamics stores competitor details such as website or revenue, those can be added as separate custom properties on the deal record to keep richer context.

Dynamics territory assignment (Territory object) stores region or district on the Opportunity, and may include levels such as region, district, and zone. HubSpot lacks a native territory field, so we create a custom pick-list property (Territory__c) and map each Dynamics territory value to a HubSpot pick-list entry. If Dynamics uses territory fields, we replicate them as custom properties on the deal or contact record, preserving the territorial hierarchy for reporting.