HubSpot to Dynamics 365 migration
We migrate Contacts, Companies, Deals, and Activity history from HubSpot Sales Hub into Microsoft Microsoft Dynamics 365 Sales with the Lead-versus-Contact routing resolved during scoping, HubSpot Company-to-Account lookups preserved at import time, and every deal pipeline re-expressed as a Dynamics Business Process Flow before cutover.
FlitStack AI migrates lead or contacts, accounts, opportunities, business process flows and products from HubSpot to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from HubSpot to Dynamics 365?
Moving from HubSpot Sales Hub to Microsoft Microsoft Dynamics 365 Sales is a schema transformation, not a straight record copy.
Read the full summary
HubSpot consolidates all people into a single Contact object with a Lifecycle Stage property; Dynamics 365 separates unqualified prospects into Leads and qualified buyers into Contacts attached to Accounts. We resolve that routing during discovery and apply it as a transform at migration time, preserving the original Lifecycle Stage in a custom field for audit. HubSpot Companies map directly to Dynamics Accounts, and Deals map to Opportunities with the pipeline re-expressed as a Business Process Flow. Activity history (calls, emails, meetings, tasks) migrates through the Dataverse Web API using batch operations with OData v4.0 pagination and parent-record GUID resolution. HubSpot Workflows, Sequences, and the Marketing Contacts billing flag do not migrate; we deliver a written automation inventory and a Dynamics workflow rebuild guide for the customer's admin team.
Contact → Lead or Contact (routing required)
HubSpot Contacts with Lifecycle Stage of subscriber, lead, or marketing qualified lead route to Dynamics 365 Lead.
How it maps
Lifecycle Stage of SQL, customer, evangelist, or other qualified states route to Dynamics 365 Contact attached to an Account. We apply this split as a transform during migration using HubSpot's lifecyclestage property, and write the original Lifecycle Stage into a custom field hs_original_lifecycle on both Lead and Contact for reconciliation.
Company → Account
HubSpot Company records map directly to Dynamics 365 Account.
How it maps
The HubSpot company domain becomes the Account Website field and acts as a dedupe key during import. Account is provisioned before any Contact or Lead import so that the CustomerId (Account) lookup is satisfied at the moment of insert. Dynamics 365 does not have a separate Company entity; all organizational records land in Account.
Deal → Opportunity
HubSpot Deals map to Dynamics 365 Opportunity.
How it maps
The HubSpot dealstage property maps to the active Business Process Flow stage on Opportunity. We configure the Business Process Flow (BPF) during migration setup to match the HubSpot pipeline's stage names, step order, and category labels so that deal history reflects the correct progression.
Pipeline → Business Process Flow
Each HubSpot Deal pipeline becomes a Dynamics 365 Business Process Flow attached to the Opportunity entity.
How it maps
We define the BPF stages, step categories, and step labels during migration setup in the destination Dynamics environment, matching the HubSpot pipeline configuration. Multi-pipeline accounts require multiple BPFs, and we configure which BPF applies to each Opportunity at migration time via the Process field.
Product → Product
HubSpot Products map to Dynamics 365 Product records with Standard Price List entries created during import.
How it maps
ProductCode maps from HubSpot hs_sku. Dynamics Products carry a Product Type (Sales, Services) that we set based on HubSpot product categorization.
Line Item → Opportunity Product
HubSpot Line Items attach to Deals and map to Dynamics 365 Opportunity Product records linked to the parent Opportunity.
How it maps
We resolve the Product reference, Quantity, and Unit Price at migration time. Opportunity Product is inserted after the Opportunity and Product records exist in the destination.
- ContactLead or Contactsplit
- CompanyAccount1:1
- DealOpportunity1:1
- PipelineBusiness Process Flowtransformed
- ProductProduct1:1
- Line ItemOpportunity Product1:1
+ 8 more in the mapping below
How HubSpot and Dynamics 365 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | HubSpot | Dynamics 365 |
|---|---|---|
| Lead vs Contact model | Single Contact object with Lifecycle Stage property | Separate Lead and Contact objects with explicit Qualify/Convert action |
| Company model | Company is a standalone object linked to Contacts via associations | Account is the parent of Contact; Company is not a separate entity type |
| Pipeline structure | Deal pipelines with stage names, probabilities, and custom properties per pipeline | Business Process Flows tied to Opportunity with stage steps and step categories |
| Custom objects | Enterprise tier only ($150/seat/mo + $3,500 onboarding) | Available via custom entities in Dataverse at most tiers without mandatory onboarding fees |
| Pricing model | Per-seat plus Marketing Contacts metering on the marketing layer | Per-user subscription with volume-based tiers; no per-contact billing |
| API architecture | HubSpot CRM API v3 with token-bucket rate limits (100-200 req/10sec burst) | Dataverse Web API (OData v4.0 REST) with OAuth 2.0 via Microsoft Entra ID |
| Microsoft ecosystem | No native Microsoft integration depth; Zapier or third-party connectors required | Native integration with Microsoft 365, Teams, Power BI, Azure, and SharePoint |
What to watch for in a HubSpot to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Lead-Contact routing has no automated default in Dynamics
HubSpot collapses all people records into a single Contact object with a Lifecycle Stage property; Dynamics 365 separates unqualified prospects into Lead records and qualified buyers into Contact records attached to Account.
How we handle it
We design the routing rule during scoping using the customer's Lifecycle Stage matrix (lead maps to Lead; SQL and beyond map to Contact), apply it as a transform at migration time, and preserve the original Lifecycle Stage in a custom field on both the Lead and Contact for audit. Teams that skip this step end up with Contacts that have no Account (orphaned) or Leads that should have been qualified on day one, requiring manual rework in Dynamics.
HubSpot Workflows and Sequences do not migrate to Dynamics 365
HubSpot Workflows use property-triggered branching with built-in delays and CRM actions that do not map to any Dynamics 365 automation primitive.
How we handle it
Dynamics 365 uses Business Rules, Power Automate flows, and classic Workflows for automation — each with different triggers, action types, and scoping rules. Sequences (sales engagement cadences) are a HubSpot-specific sales engagement feature that has no direct Dynamics 365 equivalent. We do not migrate automations as code. We deliver a written inventory of every active HubSpot Workflow and Sequence with its trigger, conditions, actions, and a recommended Dynamics rebuild guide for the customer's admin team.
HubSpot Company is not a Dynamics Company object — it is an Account
HubSpot has a standalone Company object; Dynamics 365 does not.
How we handle it
All organizational records in Dynamics 365 live as Account (for organizations) or Contact (for people) — there is no Company entity. The HubSpot Company-to-Account mapping is straightforward for standard fields (name, domain, industry), but any Company-specific custom properties must map to Account custom fields that we create before migration. Teams that assume a Company object exists in Dynamics will create duplicate records if they try to create a Company entity that does not exist.
Dataverse batch operations require careful GUID sequencing
Dynamics 365 requires parent records to exist before child records can reference them.
How we handle it
HubSpot allows forward-referencing (a Deal can reference a Contact that does not yet exist). We sequence migrations as: Accounts (from Companies) first, then Users (Owners), then Leads and Contacts with AccountId resolved, then Opportunities with AccountId and OwnerId resolved, then Products and Price Lists, then Line Items, then Activity history. Skipping this sequencing results in referential integrity failures and batch rejection by the Dataverse Web API.
HubSpot Marketing Contacts billing flag has no Dynamics equivalent
HubSpot's Marketing Contacts flag (which determines whether a contact is billed at the marketing contact tier) has no direct Dynamics 365 analog because Microsoft Dynamics 365 Sales uses per-user licensing.
How we handle it
We preserve the flag value in a custom field hs_marketing_contact on the migrated Lead or Contact so that if the customer later connects a marketing automation tool (Dynamics 365 Marketing, Customer Insights, or a third-party platform), they can re-segment based on the original billing classification. Email opt-in and opt-out preferences migrate to Dynamics 365 Contact's Email Opt In field.
How the migration runs
Discovery and Dynamics environment audit
We audit the source HubSpot portal across tier (Starter/Professional/Enterprise), all custom properties, custom objects, pipeline count, active workflows, active sequences, and engagement volume.
What this step covers
We pair this with a Dynamics 365 environment audit: identifying the existing Dataverse environment, security roles, existing entities, and Business Process Flows already in place. The discovery output is a written migration scope, a Lead-Contact routing rule, and a list of custom fields to create in Dynamics before any data moves.
Schema design and custom entity provisioning
We design the destination schema in Dynamics 365.
What this step covers
This includes creating custom fields on Account, Contact, Lead, and Opportunity to receive HubSpot custom properties; defining Business Process Flows to match each HubSpot pipeline; setting up Price Lists and Product records; and provisioning any custom entities for HubSpot custom objects. Custom entities in Dataverse are created before any data import. Schema is validated in a Dynamics Sandbox environment before production migration begins.
Sandbox migration and reconciliation
We run a full migration into a Dynamics 365 Sandbox using production-representative data volume.
What this step covers
The customer's Dynamics admin and RevOps lead reconcile record counts (Accounts in, Leads in, Contacts in, Opportunities in, Activities in), spot-check 25-50 records against the HubSpot source, and validate that the Business Process Flow stages match the original deal history. Any mapping corrections are documented and applied to the production migration plan before cutover.
Owner reconciliation and User provisioning
We extract every distinct HubSpot Owner referenced on Contact, Company, Deal, and Engagement records and match by email against the Dynamics 365 destination User table.
What this step covers
Owners without a matching Dynamics User enter a reconciliation queue. The customer's admin provisions any missing Users (active or inactive) before migration proceeds because Owner (OwningUser) is a required reference on most standard entities. This step is a hard gate before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from HubSpot Companies), Users (Owner resolution validated), Leads and Contacts (with AccountId resolved and the Lifecycle Stage routing applied as a transform), Opportunities (with AccountId, OwnerId, and Business Process Flow assigned), Products and Price Lists, Opportunity Products (Line Items), and Activity history (Emails, Phone Calls, Appointments, Tasks, Notes via Dataverse batch API).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation rebuild handoff
We freeze HubSpot writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dynamics 365 as the system of record.
What this step covers
We deliver the Workflow, Sequence, and automation inventory document to the customer's admin team with a recommended Dynamics rebuild path for each automation. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's sales team. We do not rebuild HubSpot Workflows or Sequences as Power Automate flows or Business Rules inside the migration scope; that work is a separate engagement.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Pricing reflects record volume, custom entity complexity, and pipeline reconfiguration scope. Dynamics implementations often require a Microsoft partner for Business Process Flow configuration and Power BI dashboard setup, which can add 2-3x to the base subscription cost over the first year. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for HubSpot to Dynamics 365 →Why teams move from HubSpot to Dynamics 365
- Teams with existing Microsoft infrastructure (Office 365, Teams, SharePoint, Azure) gain native data continuity by moving sales data into Dynamics 365. HubSpot lacks a first-party Microsoft connector at the data layer, requiring Zapier or third-party middleware to push deal data into Teams channels or SharePoint document libraries. Dynamics 365 writes to these services natively, eliminating sync fragility and per-record API costs that accumulate on HubSpot's per-seat model at scale.
- HubSpot's per-seat pricing plus the Marketing Contacts billing flag creates unpredictable bills as contact databases grow. A team with 80,000 HubSpot contacts — many inherited from a previous CRM — may receive a 3-4x bill multiplier because all imported records default to marketing-billed status. Microsoft Dynamics 365 Sales uses per-user licensing with no per-contact metering, making cost projections stable and auditable for finance teams regardless of database size.
- HubSpot's marketing automation is genuinely strong, but its sales configuration tools (territory management, hierarchical sales structures, complex compensation models) plateau at Enterprise tier. Dynamics 365 offers advanced territory management, multi-level sales hierarchies, and quasi-direct ERP integration with Dynamics 365 Finance or Business Central that HubSpot cannot replicate without a separate integration layer and per-record sync costs.
- Dynamics 365 reporting through Power BI delivers multi-dimensional pipeline analysis across territories, product lines, custom fiscal periods, and non-standard attribution models that HubSpot's templated dashboards constrains without a data warehouse export. Enterprise revenue operations teams cite this as the decisive factor when HubSpot's reporting layer blocks the board-level visibility they need.
- HubSpot's mandatory onboarding fees ($1,500 at Professional, $3,500 at Enterprise) plus feature tier surprises (sequences, calling, and quoting gated at Professional) create budget overrun risk that teams discover mid-implementation. Dynamics 365 publishes pricing more transparently and does not require a mandatory onboarding engagement to access core CRM functionality, though a certified implementation partner is strongly recommended for Business Process Flow configuration.
Questions, answered
HubSpot to Dynamics 365 migration questions
How long does a HubSpot Sales Hub to Microsoft Microsoft Dynamics 365 Sales migration take?
Most migrations land between four and six weeks for accounts under 20,000 Contacts and 4,000 Deals with no custom objects and a straightforward Lifecycle Stage matrix. Migrations with custom objects, multi-pipeline Deal structures, large engagement histories (over 300,000 activity records), or HubSpot Marketing Hub co-existence requirements move to ten to fourteen weeks because of Business Process Flow design, custom entity schema setup, and Owner-to-User reconciliation. Dynamics 365 implementations broadly (not just data migration) typically require 3-6 months with a certified partner, but the data migration scope alone is shorter.
Do HubSpot Workflows, Sequences, and Forms migrate to Dynamics 365?
No. HubSpot Workflows and Dynamics 365 Power Automate or Business Rules are structurally different automation models with different triggers, action types, and scoping. Sequences (sales engagement cadences) are a HubSpot-specific feature that has no direct Dynamics 365 equivalent. We do not migrate automations as code. We deliver a written inventory of every active HubSpot Workflow and Sequence with its trigger, conditions, actions, and a recommended Dynamics rebuild guide (Power Automate, Business Rules, or workflow) for the customer's admin team. Forms do not migrate; we recommend Dynamics 365 Customer Voice or a Power Apps portal form as the replacement.
Do we lose historical engagement data (calls, emails, meetings, tasks)?
No. We migrate the full engagement history through the Dataverse Web API using batch operations with OData v4.0 pagination and parent-record GUID resolution. Emails land as Dynamics Email records linked to the regarding Lead, Contact, or Opportunity. Calls land as Phone Call records with Duration and Direction preserved. Meetings land as Appointment records with start time, end time, location, and attendees. Tasks land as Task records with subject, status, priority, and due date preserved. Activity ordering is preserved by setting the actual duration or timestamp fields to the original HubSpot values.
Can we keep HubSpot Marketing Hub while moving Sales to Dynamics 365?
Yes. A hybrid stack is a common pattern we migrate. HubSpot Marketing Hub continues to handle inbound marketing, email campaigns, and lead capture; Microsoft Dynamics 365 Sales handles the sales process from Lead qualification through Opportunity close. We configure the native HubSpot-to-Dynamics 365 connector (a HubSpot-built bidirectional sync) during migration so that new HubSpot Leads flow into Dynamics 365 Leads, and Dynamics 365 Contacts and Opportunities sync back to HubSpot for marketing attribution and reporting. The customer continues paying for HubSpot Marketing Contacts at the marketing layer while moving sales seat licensing to Dynamics 365.
How do we handle the HubSpot Marketing Contacts billing flag during migration?
The Marketing Contacts flag is a HubSpot billing concept with no direct Dynamics 365 equivalent because Microsoft Dynamics 365 Sales uses per-user licensing. We preserve the flag value in a custom field hs_marketing_contact on the migrated Lead or Contact so that if the customer later connects Dynamics 365 Marketing, Customer Insights, or another marketing automation platform, they can re-segment based on the original billing classification. Email opt-in and opt-out preferences migrate to Dynamics 365 Contact's Email Opt In and Do Not Bulk Email fields.
What happens to HubSpot Deals and pipelines in Dynamics 365?
HubSpot Deal pipelines become Dynamics 365 Business Process Flows attached to the Opportunity entity. We configure each BPF during migration setup to match the HubSpot pipeline's stage names, step order, and category labels. Multiple HubSpot pipelines require multiple BPFs, and we assign the correct BPF to each Opportunity at migration time via the Process field on the Opportunity record. Closed-Lost and Closed-Won reasons from HubSpot custom fields become custom fields on the Opportunity in Dynamics.
Can FlitStack AI also migrate from HubSpot Marketing Hub to Dynamics 365 Marketing or Customer Insights?
Yes. HubSpot Marketing Hub to Dynamics 365 Marketing or Customer Insights Journeys is a parallel scope we handle. Dynamics 365 Marketing uses a different data model (marketing contacts and segments rather than HubSpot's contact-lifecycle approach), and Customer Insights uses a unified profile model that requires data unification before activation. We migrate the marketing contact database, email subscription preferences, and segmentation lists. Marketing automation flows and customer journeys are documented for rebuild in Dynamics 365 Marketing or Customer Insights; they do not migrate as code because the automation models differ substantially between platforms.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Dynamics 365 to HubSpotThe same pair in reverse Bitrix24 to Dynamics 365Mapping · history · rollbackZendesk Sell to Dynamics 365Mapping · history · rollbackPipedrive to Dynamics 365Mapping · history · rollbackOdoo CRM to Dynamics 365Mapping · history · rollbackZoho CRM to Dynamics 365Mapping · history · rollbackMailchimp to Dynamics 365Mapping · history · rollback HubSpot to SalesforceMapping · history · rollbackHubSpot to Zoho CRMMapping · history · rollbackHubSpot to PipedriveMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
Get a quote
Moving from HubSpot to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote