Agency Migration Guide
Microsoft Dynamics 365 to HubSpot Migration
What actually transfers, what quietly does not, and what has to be rebuilt by hand.
We mapped Microsoft Dynamics 365 against HubSpot feature by feature: 82 features, 15 synced objects, 15 documented traps and 26 items that have to be rebuilt. The whole map is on this page, ungated.
The PDF is the same reference, formatted to send to a client.
Get The Guide And The Calculator
The full Microsoft Dynamics 365 to HubSpot reference as a branded PDF you can send straight to a client, plus the Excel calculator we scope these migrations with: every one of the 82 features as a row, enter your counts, get hours.
Three files: the guide as a PDF, the same guide unbranded in Markdown for your AI tool, and the full Excel effort calculator.
Microsoft Dynamics 365 to HubSpot is a high migration, typically 3-8 weeks. Of 82 features we mapped, 22 carry across as they are and 57 land with something lost. The work is not moving records: it is the 26 items nothing moves for you.
Migration Scorecard
- Migration complexity
- High
- Typical timeline
- 3-8 weeks
- Recommended method
- Smart transfer
- Native sync
- Data sync, two way
- Smart transfer
- Supported
- HubSpot subscription
- Base integration is free on all HubSpot plans. Custom field mappings require a paid Data Hub (Data Hub) subscription (Starter+). Custom object sync requires Enterprise. Workflow automation for sales orders requires Professional or Enterprise. Dynamics 365 side requires Read and Write permissions for each record type synced.
Feature parity across 82 capabilities
- Maps directly: 22 (27%)
- Maps partially: 57 (70%)
- No equivalent: 3 (4%)
15
Objects synced natively
15
Limitations and traps
26
Manual rebuild items
4
Source editions covered
Where this comes from: Our own research corpus, verified 2026-07-31, behind every number on this page.
The Fifteen Objects That Sync Natively
What the connector moves for you, and which way each one flows.
Contacts
Two wayBecomes Contacts
One-to-one record sync model. A single HubSpot contact generating multiple Dynamics leads is NOT supported natively. Contacts and Leads are separate sync configurations.
Leads
Two wayBecomes Contacts
Dynamics Leads sync to HubSpot Contacts separately from Dynamics Contacts. The native connector does not handle one HubSpot contact mapping to multiple Dynamics leads. Tasks associated with a Dynamics Lead can only sync one-way from Dynamics to HubSpot.
Accounts
Two wayBecomes Companies
Account hierarchies (parent-child relationships) and territory rollups from Dynamics do not transfer. Owner mapping between Dynamics queues and HubSpot round-robin can conflict.
Opportunities
Two wayBecomes Deals
Opportunity status codes may not align between systems, potentially causing revenue attribution issues. Line item prices changed in HubSpot do NOT sync back to created Dynamics sales orders.
Products
Two wayBecomes Products
Both Dynamics Products and Bundles sync to HubSpot Products. Product syncing is available as a standard object type. Direction confirmed against the app's HubSpot marketplace listing (read 2026-07-31), which marks this object INBOUND, source to HubSpot only. Split from the former 'Products and Bundles' entry: HubSpot's marketplace listing (read 2026-07-31) lists Products and Bundles as two separate shared objects with different directions. Products syncs BOTH ways.
Bundles
Into HubSpotBecomes Products
Dynamics 365 product bundles sync into HubSpot Products. HubSpot's marketplace listing (read 2026-07-31) marks this object INBOUND, source to HubSpot only, with 5 default field mappings. Changes made in HubSpot do not flow back.
Invoices
Into HubSpotBecomes Invoices
Invoice sync available as a standard object type. Sync card visible on invoice records after setup. Direction confirmed against the app's HubSpot marketplace listing (read 2026-07-31), which marks this object INBOUND, source to HubSpot only.
Sales Orders
Into HubSpotBecomes Orders
Sales order sync must be explicitly configured. If the sync is not configured, creating a Dynamics sales order will not create a corresponding HubSpot order. Line item price changes on HubSpot deals do NOT sync to the created sales order. Direction confirmed against the app's HubSpot marketplace listing (read 2026-07-31), which marks this object INBOUND, source to HubSpot only.
Appointments
Two wayBecomes Meetings
Dynamics Appointments map to HubSpot Meetings. Part of the activities sync category.
Tasks
Two wayBecomes Tasks
A task must be associated with another object record (e.g., lead or contact) to sync from HubSpot to Dynamics. Tasks associated with Dynamics Leads can only sync one-way from Dynamics to HubSpot.
Notes
Two wayBecomes Notes
Part of the activities sync category.
Emails
Into HubSpotBecomes Emails
Offline activities logged in Dynamics may not appear in HubSpot. Part of the activities sync category. Direction confirmed against the app's HubSpot marketplace listing (read 2026-07-31), which marks this object INBOUND, source to HubSpot only.
Phone Calls
Into HubSpotBecomes Calls
Dynamics Phone Calls map to HubSpot Calls. Part of the activities sync category. Direction confirmed against the app's HubSpot marketplace listing (read 2026-07-31), which marks this object INBOUND, source to HubSpot only.
Custom Entities
Two wayBecomes Custom Objects
Microsoft Dynamics 365 is listed as a supported app for custom object sync. Requires HubSpot Enterprise. Some community reports indicate custom entities may have limited support via the native Data Sync connector and may require third-party tools or custom API integration for complex scenarios.
Cases
Two wayBecomes Tickets
Dynamics 365 Cases sync to HubSpot Tickets. Listed as a shared object on the app's HubSpot marketplace listing (read 2026-07-31); no default field mappings are published, so ticket properties need mapping by hand.
Fifteen Things the Sync Does Not Tell You
Each one is documented, and each one has ended a migration in a bad week.
One Object Type Synced at a Time
The native connector requires configuring each object type separately. You can only set up and sync one object type at a time (e.g., contacts separately from companies). This makes initial setup more time-consuming for complex data models.
Workaround: Plan sync setup order carefully. Configure contacts first, then companies, then deals, then other objects. Allow time for each object sync to complete before starting the next.
Dropdown and Multi-select Fields Sync One-way Only
Dropdown, radio select, multi-select, and checkbox field types cannot sync bidirectionally. They only flow one-way into text fields. This means structured data in Dynamics becomes unstructured text in HubSpot.
Workaround: Create matching dropdown/select properties in HubSpot manually. Use Data Hub or workflows to transform text values back into structured properties after sync.
Lookup and Reference Fields Do Not Sync
Dynamics 365 lookup (reference) fields are not supported by the native connector. This means relational references between records cannot be synced as field values.
Workaround: Use text-based ID fields to store references. Manually map associations post-sync. Consider middleware (Make, Power Automate, n8n) for complex relational sync.
Custom Field Mappings Require Paid Subscription
Default field mappings are available on free plans, but creating custom field mappings between Dynamics and HubSpot requires a paid Data Hub (Data Hub) subscription.
Workaround: Upgrade to Data Hub Starter or higher. Alternatively, use the default mappings and supplement with CSV imports or API-based field transfers.
Deal Line Items Do Not Sync
The native Dynamics 365 connector does not sync deal line items. Additionally, line item price changes on HubSpot deal records do not sync back to the created Microsoft Dynamics 365 sales order.
Workaround: Manually migrate line items via CSV or API. Use middleware for ongoing line item synchronization if needed.
No List-to-list Sync
There is no native list-to-list synchronization between Dynamics 365 marketing lists and HubSpot active lists or segments.
Workaround: Manually recreate lists in HubSpot using filters and properties. Export list membership from Dynamics and import as a contact property in HubSpot.
One-to-one Record Sync Model Only
The native connector supports only a one-to-one record sync model. A single HubSpot contact cannot generate or sync to multiple Dynamics leads, which is a common scenario in some Dynamics implementations.
Workaround: Use middleware (Make, Power Automate, n8n) for many-to-one or one-to-many sync scenarios. Redesign data model to fit one-to-one constraints.
Account Hierarchies and Territory Rollups Break
Dynamics 365 account hierarchies (parent-child relationships) and territory assignment/parent rollups do not transfer to HubSpot through the native sync.
Workaround: Manually recreate parent-child company associations in HubSpot. Use custom properties to store territory information. Rebuild territory logic using HubSpot Teams and workflows.
Opportunity Status Codes May Not Align
Dynamics opportunity status codes and stages may not map cleanly to HubSpot deal stages, potentially causing incorrect revenue attribution.
Workaround: Create a stage mapping document before migration. Configure HubSpot deal pipelines to mirror Dynamics opportunity stages. Use milestone mirroring approach.
Owner Mapping Conflicts Between Systems
Owner fields do not map cleanly between Dynamics queue-based assignment logic and HubSpot round-robin assignment, causing potential conflicts in lead routing.
Workaround: Establish owner mapping rules before sync. Decide which system is the owner source of truth. Use conditional sync logic to protect owner fields from being overwritten.
Offline Dynamics Activities May Not Sync
Activities logged offline in Dynamics (such as via the mobile app in offline mode) may never appear in HubSpot.
Workaround: Ensure Dynamics users sync their offline activities before expecting them to appear in HubSpot. Consider syncing summarized activity data (Last Activity Date) rather than individual activities.
Tasks Associated With Leads Have One-way Sync Only
If a task is associated with a Dynamics Lead, it can only sync one-way from Microsoft Dynamics to HubSpot. Bidirectional task sync requires association with a Contact or other supported object.
Workaround: Associate tasks with contacts instead of leads where possible. Accept one-way sync for lead-associated tasks.
Race Conditions With Bidirectional Sync
When syncing everything both ways, race conditions can occur where the last write wins, potentially overwriting intended data changes.
Workaround: Establish clear data ownership rules per field. Use one-way sync for high-conflict fields (owner, stage, revenue). Implement conditional sync logic via middleware.
Custom Entity Sync Has Limited Native Support
While Microsoft Dynamics 365 is listed as a supported app for custom object sync, community reports indicate that complex custom entities may not sync reliably via the native Data Sync connector. Certain custom entities with complex relationships may require third-party tools.
Workaround: Test custom entity sync thoroughly in a sandbox. Use third-party tools (Make, Power Automate, custom Azure Functions) for complex custom entity scenarios. Consider API-based custom integration.
Attachments and Files Do Not Sync Natively
Dynamics 365 file attachments and documents do not sync through the native Data Sync connector.
Workaround: Use HubSpot Smart Transfer one-time transfer for attachments. Manually download and re-upload critical files. Use API scripting for large volume attachment migration.
Three Microsoft Dynamics 365 Features HubSpot Cannot Replace
Not a workaround away. If a client depends on one of these, it belongs in the conversation before the contract.
Who Knows Whom
HubSpot has no native who-knows-whom or relationship graph feature. Third-party tools like Nudge.ai (now Affinity) or LinkedIn TeamLink provide similar insights.
Field Service
HubSpot has no field service management capability. Requires dedicated field service solution (ServiceTitan, Jobber, FieldEdge) integrated with HubSpot.
Power Automate - Desktop Flows (RPA)
HubSpot has no RPA capability. If client uses desktop flows, need dedicated RPA platform (UiPath, Power Automate Desktop can continue standalone, or Automation Anywhere).
Four Things a Migration Does Not Rebuild
These are Microsoft Dynamics 365's own code and products. A HubSpot migration does not port them, so they carry no hours in any estimate. They still need a decision, because the client is giving something up.
Power Apps (Model-Driven & Canvas)
Power Apps represent custom applications that need complete rethinking. Model-driven apps partially map to HubSpot record customization. Canvas apps need external web application development. Assess each app's purpose, user base, and business criticality. This can be a major project in itself.
Plugins (Custom Code)
Plugins are custom .NET code requiring complete rewrite. Each plugin needs analysis: can it become a workflow, custom code action, or does it need an external service? Pre-operation/pre-validation plugins are hardest; no HubSpot equivalent for blocking saves with server-side logic. Count all plugins and estimate rewrite effort.
Azure Integration (Service Bus, Functions, Logic Apps)
Azure integrations are often deeply embedded in enterprise architectures. Each Azure service touchpoint needs evaluation. Some can be redirected to HubSpot API; others need rearchitecting. If client is heavily Azure-invested, this is a major workstream.
Dual-Write (Finance & Operations)
Dual-write is critical for orgs using both Dynamics CRM and Dynamics ERP. Moving CRM to HubSpot breaks this native sync. Must build custom ERP<->HubSpot integration. Assess all data flows between CRM and ERP before migration planning.
The 26 Items That Get Rebuilt by Hand
This is the list that separates a quote that holds from one that does not.
Data And Objects
Custom Entities and Data Model
Dynamics 365 custom entities, relationships, and complex data models must be redesigned and rebuilt in HubSpot.
Account Hierarchies
Parent-child account relationships and territory rollup structures do not transfer.
Marketing Lists
Dynamics 365 marketing lists (static and dynamic) do not sync to HubSpot.
Attachments and Documents
File attachments, SharePoint documents linked in Dynamics, and notes with attachments do not sync.
Deal Line Items
Line items on opportunities/deals do not sync. Price changes on HubSpot deals do not sync to Dynamics sales orders.
Automation
Power Automate Flows and Business Process Flows
Dynamics 365 Power Automate flows, business rules, and Business Process Flows must be completely rebuilt in HubSpot.
Business Rules and Plugins
Dynamics server-side plugins and business rules have no like-for-like HubSpot equivalent, but much of the work relocates: workflows cover rule-style field logic, and Data Hub Professional custom code actions run JavaScript or Python server-side. What does not map is synchronous pre-save plugin execution against the record write path.
Email Templates and Sequences
Dynamics email templates and sales sequences must be rebuilt.
Lead Routing and Queue Logic
Dynamics queue-based lead routing, round-robin within queues, and SLA timers must be recreated.
Approval Flows
Dynamics approval flows (built in Power Automate or custom) have limited HubSpot equivalents.
Reporting
Dynamics Reports and Views
All Dynamics 365 reports, advanced find views, and personal views must be rebuilt in HubSpot.
Power BI Dashboards
Any Power BI dashboards connected to Dynamics data will lose their data source.
Forecasting Configuration
Dynamics 365 forecasting models, hierarchies, and historical forecast data do not transfer.
Dynamics Dashboards
Interactive dashboards, entity-specific dashboards, and system dashboards must be recreated.
Sales And Marketing Config
Lead Scoring Models
Dynamics 365 lead scoring (native or via Dynamics Marketing/Customer Insights) must be recreated.
Marketing Campaigns and Customer Journeys
Dynamics Marketing or Customer Insights journeys, segments, and campaign orchestration do not transfer.
Quotes and Sales Literature
Dynamics quotes, sales literature, and competitor tracking must be rebuilt.
Forms and Lead Capture
Any Dynamics-based web forms or Power Apps portals for lead capture must be replaced.
Knowledge Base Articles
Dynamics 365 Customer Service knowledge articles do not transfer.
Users And Permissions
Security Roles and Business Units
Dynamics 365 security roles, business units, and field-level security do not transfer.
Teams and Business Unit Hierarchy
Dynamics business unit hierarchy and team structures must be recreated.
User Setup and Owner Mapping
Dynamics user records must be mapped to HubSpot users for owner assignment on all records.
Integrations
Outlook Integration
Dynamics 365's deep Outlook integration (App for Outlook, server-side sync) must be replaced.
SharePoint Integration
Dynamics-SharePoint document management integration is lost.
Power Platform Connections
Power Apps, Power Automate, and Power Virtual Agents connected to Dynamics lose their data source.
Third-Party Dynamics Apps
Any apps connected to Dynamics (accounting software, ERP modules, Slack, Zoom, etc.) must be reconnected to HubSpot.
The Sequence
Sync First, Then Migrate
Order is the content here. These are a dependency chain, and running them out of order is a documented way these migrations fail.
- 1
Audit
Document all Dynamics 365 entities, fields, relationships, business rules, Power Automate flows, reports, and integrations.
- 2
Pre-clean
Deduplicate records, standardize field values, validate data quality. Export critical data as CSV backups.
- 3
Plan
Create field mapping document matching Dynamics fields to HubSpot properties. Identify custom properties and objects needed in HubSpot.
- 4
Configure HubSpot
Set up custom properties, deal pipelines, ticket pipelines, custom objects, teams, and user permissions.
- 5
Connect Integration
Navigate to HubSpot Marketplace, search for Microsoft Dynamics 365, connect using your Dynamics subdomain.
- 6
Configure Object Sync
Set up each object sync one at a time: start with contacts, then companies, then deals. Configure sync direction and field mappings for each.
- 7
Test With Sample Data
Start with 5 representative records per object type. Validate field mapping accuracy. Scale to 50 records, then full production.
- 8
Smart Transfer
Use HubSpot Smart Transfer for one-time data transfers (attachments, segments, historical data not covered by sync).
- 9
Rebuild Automation
Recreate Power Automate flows as HubSpot workflows. Rebuild business process flows, email templates, and sequences.
- 10
Rebuild Reports
Recreate critical reports and dashboards in HubSpot. Reconnect Power BI if applicable.
- 11
User Training
Train all teams on HubSpot. Department-specific training for sales, marketing, and service.
- 12
Parallel Run
Run both systems in parallel briefly (1-2 weeks) to validate data integrity and workflow accuracy.
- 13
Cutover
Set HubSpot as primary CRM. Disable Dynamics sync. Update all integrations and form submissions.
- 14
Post-migration Monitoring
Monitor for 2-4 weeks. Check daily sync logs, error reports, and user-reported issues.
Typically 3-8 weeks end to end, depending on how much of the source configuration is actually in use.
Effort Estimator
How Big Is This Migration?
A handful of questions, no email required. The ranges come from the research above: every feature we mapped carries an effort figure, and this adds up the ones that apply to you.
Estimated Effort
Answer a couple of questions and an hours range appears here.
Built from our research on 82 Microsoft Dynamics 365 features. It is a range, not a quote.
A planning range, not a quote. It is delivery effort only, with no project management line and no agency markup, so add your own. What moves it most in practice is data quality.
What Goes Wrong Most Often
The failures that show up again and again, in roughly the order they bite.
Dropdown and Multi-select Fields Only Sync One-way Into Text
structured data becomes unstructured
Lookup/reference Fields Do Not Sync Natively
relational data is lost
Account Hierarchies and Territory Rollups Break During Migration
Account hierarchies and territory rollups break during migration
Opportunity Status Codes May Not Align, Causing Wrong Revenue Attribution
Opportunity status codes may not align, causing wrong revenue attribution
Owner Mapping Conflicts Between Dynamics Queues and HubSpot Round-robin
Owner mapping conflicts between Dynamics queues and HubSpot round-robin
Offline Activities Logged in Dynamics May Never Appear in HubSpot
Offline activities logged in Dynamics may never appear in HubSpot
Tasks Associated With Leads Can Only Sync One-way (Dynamics to HubSpot)
Tasks associated with Leads can only sync one-way (Dynamics to HubSpot)
Deal Line Items Do Not Sync
must be migrated separately
One HubSpot Contact Cannot Map to Multiple Dynamics Leads
One HubSpot contact cannot map to multiple Dynamics leads
Custom Field Mappings Require Paid Data Hub Subscription
without it you are limited to default mappings
Power Platform Integrations (Power Apps, Power Automate, Power BI) Connected to Dynamics Lose Their Data Source
Power Platform integrations (Power Apps, Power Automate, Power BI) connected to Dynamics lose their data source
Lifecycle Stages Can Get Overwritten by Automated Marketing Workflows, Creating False SQL Counts
Lifecycle stages can get overwritten by automated marketing workflows, creating false SQL counts
Attempting to Migrate Everything at Once Over a Weekend Is a Disaster Pattern
use phased approach with 5-record, 50-record, then full-production validation
One Mismatched Column or Incorrect Field Mapping Can Cause Thousands of Records to Import Incorrectly
One mismatched column or incorrect field mapping can cause thousands of records to import incorrectly
Questions
Microsoft Dynamics 365 To HubSpot, Answered
Yes. Data sync, two way, covering 15 objects. Smart transfer is supported. What it does not do is rebuild configuration: that is the 26 items below.
Typically 3-8 weeks. Complexity is driven by automation and reporting depth, not by record count: the connector moves records, so a large database is not by itself a long project.
Of 82 features we mapped, 22 (27%) carry across directly and 57 (70%) map partially, meaning something is lost or reshaped. 3 have no HubSpot equivalent at any tier.
26 items have to be rebuilt by hand, and 15 documented limitations are not surfaced by the connector at all. The full list of both is on this page.
Base integration is free on all HubSpot plans. Custom field mappings require a paid Data Hub (Data Hub) subscription (Starter+). Custom object sync requires Enterprise. Workflow automation for sales orders requires Professional or Enterprise. Dynamics 365 side requires Read and Write permissions for each record type synced.
3: Who Knows Whom, Field Service, Power Automate - Desktop Flows (RPA). If a client depends on one, it belongs in the conversation before the contract.
No. 4 items are Microsoft Dynamics 365's own code and products, which a HubSpot migration does not port and which carry no hours in an estimate. They still need a decision, because the client is giving something up.
Only in one direction. The sync is not bidirectional here, so a parallel period means picking a system of record and accepting drift in the other.
Ready to get started?
Let's do something great together.
Augment your agency's marketing team's bench with our end-to-end inbound and digital solutions and find out why we're "The HubSpot Agency for HubSpot Agencies."
Fill out this form, and someone from our Solutions team will be in touch with you soon!