---
title: "Dynamics 365 to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Dynamics 365 to HubSpot with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/dynamics-365-sales/to/hubspot"
---

# Dynamics 365 to HubSpot migration

Moving from Dynamics 365 Sales to HubSpot consolidates your lead and contact records into HubSpot's unified contact model, where lifecycle stage replaces Dynamics' split lead-contact architecture — FlitStack AI translates every Account, Contact, Lead, Opportunity, and custom entity field while preserving original create dates and stage-transition history so your HubSpot reports reflect the full customer journey from day one.

Short answer

FlitStack AI migrates companies, contacts, contact with lifecycle stage = leads, deals and deal pipeline stages from Dynamics 365 to HubSpot, 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: 24–72 hours for under 50,000 records.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/hubspot#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Dynamics 365 ![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp)

Destination HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Company Contact Contact with lifecycle stage = lead Deal Deal Pipeline Stage

Mapped field by field · sample run · one-click rollback

## What moves from Dynamics 365 to HubSpot?

Dynamics 365 Sales stores accounts, contacts, and leads in separate tables with a business-process-flow field (stepname) that has no native HubSpot equivalent.

Read the full summary

HubSpot uses a single contact object with lifecycle\_stage as the unifying property — a contact that never converted in Dynamics becomes a HubSpot contact at the appropriate lifecycle stage, not a separate lead record. We extract Dynamics data via the Dataverse API (accounts, contacts, leads, opportunities, tasks, emails, notes, and custom entities) and map each record into HubSpot's contact, company, deal, and custom object model. Dynamics business process flows — including pipeline stage names, probabilities, and forecast categories — become HubSpot deal pipelines with stage-level mapping. Custom entities in Dynamics migrate as HubSpot custom objects. Dynamics workflows, plugins, and SLA configurations do not migrate and must be rebuilt in HubSpot's automation tools. The migration runs in a staged sequence: accounts first, then contacts with owner resolution by email match, then opportunities, then activities. A delta-pickup window (24–48 hours) captures any records modified in Dynamics during the cutover. We deliver a field-level diff of the sample migration before the full run commits.

direct

### Account → Company

Dynamics Account maps directly to HubSpot Company.

How it maps

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.

direct

### Contact → Contact

Dynamics Contact maps one‑to‑one to HubSpot Contact, preserving standard fields such as full name, email, phone, job title, and address.

How it maps

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.

transformed

### Lead → Contact

Dynamics Lead maps to HubSpot Contact, not a separate lead object.

How it maps

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.

split

### Lead (unqualified) → Contact with lifecycle stage = lead

Dynamics Leads that were never converted split into HubSpot contacts at the 'lead' lifecycle stage.

How it maps

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.

direct

### Opportunity → Deal

Dynamics Opportunity maps to HubSpot Deal.

How it maps

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.

transformed

### Business Process Flow (stepname field) → Deal Pipeline Stage

Dynamics stores pipeline stage as stepname within a business process flow, not on the Opportunity itself.

How it maps

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.

******What moves 15 objects

Dynamics 365 HubSpot

- Account Company 1:1
- Contact Contact 1:1
- Lead Contact transformed
- Lead Contact with lifecycle stage = lead split
- Opportunity Deal 1:1
- Business Process Flow Deal Pipeline Stage transformed

\+ 9 more in the mapping below

## How Dynamics 365 and HubSpot 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                    | Dynamics 365                                                                                       | HubSpot                                                                                                    |
| ---------------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Data Model Architecture      | Split lead and contact tables with conversion step; business process flow stored as stepname field | Unified contact model; lifecycle stage tracks prospect-to-customer progression in one record               |
| Pipeline / Opportunity Stage | Opportunity StageName pick-list; separate Business Process Flow stepname per pipeline              | HubSpot deal pipeline stages; each pipeline is its own workflow with probability per stage                 |
| Custom Entities              | Unlimited custom tables in Dataverse; master-detail and lookup relationships supported             | HubSpot custom objects (Enterprise); associations via labels and many-to-many links                        |
| Activity History             | Email, Task, and PhoneCall stored as separate entities linked by party-list to contact             | HubSpot timelines consolidate email, call, meeting, and note history on the contact and deal record        |
| Pricing Tiers                | Sales Professional $65/user/mo; Sales Enterprise $105/user/mo; Sales Premium adds AI               | Free CRM tier available; Starter $15/mo per seat; Professional $100/mo per seat; Enterprise custom pricing |
| Microsoft Integration        | Native to Microsoft 365, Teams, Outlook, SharePoint; Copilot embedded                              | Microsoft integrations available via native connector and third-party tools; no Copilot CRM AI native      |
| Lead Qualification           | Lead QualityCode, StateCode/StatusCode, and rating fields; manual qualification step               | HubSpot lifecycle stage (subscriber, lead, MQL, SQL, customer) or HubSpot lead status pick-list            |
| Customization Scope          | Sales Enterprise: unlimited custom tables; Sales Professional: 15-table limit                      | HubSpot custom properties: limited per plan; Enterprise offers broader custom object support               |

## Dynamics 365 to HubSpot field mapping

The 30 most-used fields of 49 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/hubspot.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Dynamics 365 HubSpot

1. `fullname` Contact `firstname` Contact
2. `fullname` Contact `lastname` Contact
3. `emailaddress1` Contact `email` Contact
4. `telephone1` Contact `phone` Contact
5. `mobilephone` Contact `mobilephone` Contact

| Dynamics 365 field                 | HubSpot field                  | Mapping                 | Note                                                                                                                                                                                            |
| ---------------------------------- | ------------------------------ | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Contact.fullname`                 | `Contact.firstname`            | transformed             | Dynamics fullname splits into HubSpot firstname and lastname. We parse the full name string and populate both fields.                                                                           |
| `Contact.fullname`                 | `Contact.lastname`             | transformed             | Dynamics fullname parsed to HubSpot lastname. If fullname has no space, it lands in lastname and firstname is left blank.                                                                       |
| `Contact.emailaddress1`            | `Contact.email`                | direct                  |                                                                                                                                                                                                 |
| `Contact.telephone1`               | `Contact.phone`                | direct                  |                                                                                                                                                                                                 |
| `Contact.mobilephone`              | `Contact.mobilephone`          | direct                  |                                                                                                                                                                                                 |
| `Contact.jobtitle`                 | `Contact.jobtitle`             | direct                  |                                                                                                                                                                                                 |
| `Contact.address1_line1`           | `Contact.address`              | direct                  |                                                                                                                                                                                                 |
| `Contact.address1_city`            | `Contact.city`                 | direct                  |                                                                                                                                                                                                 |
| `Contact.address1_stateorprovince` | `Contact.state`                | direct                  |                                                                                                                                                                                                 |
| `Contact.address1_country`         | `Contact.country`              | direct                  |                                                                                                                                                                                                 |
| `Contact.address1_postalcode`      | `Contact.zip`                  | direct                  |                                                                                                                                                                                                 |
| `Contact.statecode`                | `Contact.lifecyclestage`       | value\_mapping          | Dynamics StateCode (0=Active, 1=Inactive) and StatusCode determine HubSpot lifecycle stage. Unconverted leads map to 'lead'; converted leads with a related Contact map to 'sql' or 'customer'. |
| `Contact.leadsourcecode`           | `Contact.hs_analytics_source`  | value\_mapping          | Dynamics leadsourcecode pick-list values (Advertisement, Partner, Referral, etc.) map to HubSpot HubSpot Analytics source labels.                                                               |
| `Contact.ownerid`                  | `Contact.hubspot_owner_id`     | transformed             | OwnerId resolves by email match to HubSpot user. Unmatched owners flagged before migration.                                                                                                     |
| `Contact.createdon`                | `Contact.original_createdate`  | custom\_field\_required | HubSpot Createdate is set at migration time. Original Dynamics create date preserved as Original\_Create\_Date\_\_c custom datetime.                                                            |
| `Contact.modifiedon`               | `Contact.original_modifiedate` | custom\_field\_required | Original modification date preserved as a custom field for audit continuity.                                                                                                                    |
| `Contact.contactid`                | `Contact.dynamics_contact_id`  | custom\_field\_required | Dynamics contact GUID stored as a custom property for traceability and delta-run de-duplication.                                                                                                |
| `Account.name`                     | `Company.name`                 | direct                  |                                                                                                                                                                                                 |
| `Account.website`                  | `Company.domain`               | direct                  |                                                                                                                                                                                                 |
| `Account.telephone1`               | `Company.phone`                | direct                  |                                                                                                                                                                                                 |
| `Account.industrycode`             | `Company.industry`             | value\_mapping          | Dynamics industrycode pick-list maps to HubSpot industry pick-list. Non-matching values land as free-text industry.                                                                             |
| `Account.numberofemployees`        | `Company.numberofemployees`    | direct                  |                                                                                                                                                                                                 |
| `Account.annualrevenue`            | `Company.annualrevenue`        | direct                  |                                                                                                                                                                                                 |
| `Account.address1_city`            | `Company.city`                 | direct                  |                                                                                                                                                                                                 |
| `Account.address1_country`         | `Company.country`              | direct                  |                                                                                                                                                                                                 |
| `Account.parentaccountid`          | `Company.associated company`   | transformed             | Dynamics parent account hierarchy maps via HubSpot company associations. Parent must be migrated first; circular references flagged.                                                            |
| `Account.accountid`                | `Company.dynamics_account_id`  | custom\_field\_required | Dynamics account GUID stored as a custom property for traceability and foreign-key linkage during migration.                                                                                    |
| `Lead.fullname`                    | `Contact.firstname`            | transformed             | Lead fullname splits into HubSpot firstname and lastname using the same parsing logic as Contact.                                                                                               |
| `Lead.fullname`                    | `Contact.lastname`             | transformed             | Lead lastname extracted from Dynamics fullname field.                                                                                                                                           |
| `Lead.emailaddress1`               | `Contact.email`                | direct                  |                                                                                                                                                                                                 |

## What to watch for in a Dynamics 365 to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Dynamics business process flows have no native HubSpot equivalent and must be rebuilt

Dynamics stores pipeline stage as stepname within a business process flow — a separate metadata object linked to the Opportunity.

How we handle it

HubSpot deal pipelines handle stage sequencing differently: each stage has a default probability and optional automation triggers, but there is no concept of a named 'business process flow' that controls which fields are visible per stage. We extract stepname values and map them to HubSpot deal stage names in the correct order, but the process flow logic (required fields per stage, branching, and SLA timers) does not transfer. Your HubSpot admin will need to configure stage-specific required fields and any automation triggers inside the HubSpot workflow builder after migration. This is the highest-severity gotcha for Dynamics-to-HubSpot migrations because it directly impacts sales process consistency post-switch.

high

### Dynamics StateCode and StatusCode routing to HubSpot lifecycle stage requires explicit mapping rules

Dynamics Lead StateCode (New, Qualified, Converted) and StatusCode (the reason underneath StateCode) do not map directly to HubSpot's lifecycle\_stage pick-list values.

How we handle it

An unqualified Lead with StateCode=0 could mean 'subscriber' or 'lead' depending on your Dynamics configuration. We ask your team to define the StateCode-to-lifecycle-stage routing table before migration runs — this prevents mis-routing where, for example, a dead Lead lands in HubSpot as a 'customer'. Once the routing table is confirmed, we apply it consistently across all unconverted Leads. Custom StatusCode values require value-by-value mapping.

medium

### Dynamics opportunity contact roles (OpportunityContactRole) need explicit association rebuilding

Dynamics links Contacts to Opportunities through the OpportunityContactRelation entity with a RoleName field (Decision Maker, Evaluator, etc.).

How we handle it

HubSpot's deal-contact association uses a flat contact list with optional association labels rather than a dedicated junction object with role names. We migrate the primary contact as the default association on the HubSpot Deal. Additional contacts from OpportunityContactRelation are added as associated contacts — their RoleName is preserved as a custom property (Contact\_Role\_\_c) on the deal-contact link so the role context is not lost, but HubSpot's native UI will not surface it in the standard deal card.

medium

### Dynamics attachments stored in SharePoint require re-hosting to HubSpot Files or connected storage

Dynamics 365 Sales can store file attachments on notes and emails in SharePoint Online via the-notes-(images)-and-attachments pathway.

How we handle it

HubSpot Files stores attachments natively within the platform up to the file-size limit (250MB per file). Files stored in the Dynamics/SharePoint linked storage do not automatically transfer — they must be downloaded from SharePoint and re-uploaded to HubSpot Files or re-linked to a connected SharePoint library. Large attachment sets (hundreds of files) extend the migration timeline because each file requires a separate download-and-upload operation.

low

### Dynamics custom entities with Dataverse lookup relationships need HubSpot association-label planning

Custom Dataverse tables in Dynamics often have lookup fields pointing to Account, Contact, or other custom entities.

How we handle it

HubSpot's custom objects support associations via labels, but the label vocabulary (e.g., 'belongs\_to', 'associated\_with') needs to be designed per relationship type. N-to-N junction tables in Dynamics map cleanly to HubSpot many-to-many associations. However, if your Dynamics custom entity uses multiple lookup fields to the same entity type (e.g., Primary\_Customer\_\_c and Secondary\_Customer\_\_c both pointing to Account), you need to decide how to name each association label in HubSpot so the two relationships remain distinguishable. We surface these multi-lookup cases in the pre-migration schema plan.

## How the migration runs

1. ### Audit Dynamics data model and build the field mapping specification

   FlitStack AI connects to your Dynamics 365 instance via the Dataverse API and inventories all active tables — accounts, contacts, leads, opportunities, tasks, emails, notes, and custom entities.

   What this step covers

   We extract the business process flow definitions (stepname sequences per pipeline) and the StateCode/StatusCode pick-list values. We then produce a field mapping specification that documents exactly how each Dynamics field translates to a HubSpot property, including value mappings for pick-lists and routing rules for lead-to-lifecycle-stage assignment. Your team reviews and approves the specification before any data moves.

2. ### Create HubSpot properties and deal pipelines for the migration target

   Before data lands, we create all required HubSpot custom properties (custom fields) referenced in the field mapping — for example, Original\_Create\_Date\_\_c, Dynamics\_Contact\_ID\_\_c, Dynamics\_Lead\_ID\_\_c, and Territory\_\_c.

   What this step covers

   We also create the HubSpot deal pipelines that correspond to your Dynamics business process flows, defining each stage name and probability matching the Dynamics stepname sequence. HubSpot's pipeline stage order must be configured manually in HubSpot's pipeline settings, so we deliver step-by-step setup instructions as part of the pre-migration plan.

3. ### Resolve owners and map Dynamics users to HubSpot users by email

   Dynamics OwnerId (on every record) resolves by email match to HubSpot users.

   What this step covers

   FlitStack AI generates an owner-resolution report listing matched pairs and any Dynamics owners without a corresponding HubSpot user account. Unmatched owners are flagged before the migration — your team either creates HubSpot users for them or designates a fallback HubSpot owner. No record migrates with an unresolved owner. Team-owned records (Dynamics team sharing) are assigned to a designated HubSpot user or a HubSpot Sales team as you specify.

4. ### Migrate accounts and contacts first, then leads and opportunities

   We sequence the migration to respect HubSpot's foreign-key requirements: accounts (companies) migrate first so contact associations resolve, then contacts and unconverted leads land with their company links intact, then opportunities (deals) attach to their associated contacts and companies, then activities (tasks, emails, notes) attach to their parent records.

   What this step covers

   This ordering ensures that every deal in HubSpot has at least one associated contact and company when the migration completes — the minimum required for deal reporting to function correctly.

5. ### Run a sample migration with field-level diff and verify routing rules

   A representative sample — typically 200–500 records spanning each major entity type — migrates first.

   What this step covers

   We generate a field-level diff showing the source value in Dynamics, the mapped value in HubSpot, and any transformation notes. You verify the lifecycle-stage routing for converted vs. unconverted leads, the deal-stage mapping for each pipeline, and owner resolution. Any discrepancies in the sample are corrected in the mapping specification before the full migration runs.

6. ### Execute full migration with delta-pickup and one-click rollback

   The full migration runs against your HubSpot instance.

   What this step covers

   A delta-pickup window (24–48 hours after the initial run) captures any records created or modified in Dynamics during the cutover so HubSpot reflects the final state of Dynamics at go-live. FlitStack AI audit log records every operation — record count per entity, field-level mapping applied, and owner resolution summary. If reconciliation reveals unexpected gaps, one-click rollback reverts the HubSpot environment to its pre-migration state so your team can investigate without data loss.

![](https://flitstack.ai/platforms/microsoft-dynamics-365-sales.svg) Dynamics 365 ![](https://flitstack.ai/platforms/hubspot.svg) HubSpot

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**24–72 hours for under 50,000 records** Typical, smaller accounts

**5–10 days for over 500,000 records or heavy custom-entity / business-process-flow setups** Large or heavily customised accounts

A quote scales with Dynamics record volume, the number of custom entities, and how many business process flows need to be translated into HubSpot deal pipelines. Configurations with over 20 custom fields per entity or multiple active business process flows increase mapping complexity. Dynamics-to-HubSpot owner resolution by email adds validation overhead compared to same-vendor migrations. The lower end applies to straightforward SMB setups with under 10,000 records and minimal custom objects; the upper range covers enterprise configurations with 500k+ records, multiple custom tables, and five or more active business process flows that each require a dedicated HubSpot pipeline with stage-level probability mapping. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Dynamics 365 to HubSpot →](https://flitstack.ai/contact)

## Why teams move from Dynamics 365 to HubSpot

- Dynamics 365 Sales often requires engaging certified implementation partners to design custom entities, configure business process flows, and register plugin assemblies, each adding licensing cost and extending the project timeline. Smaller sales teams with limited IT budgets find that HubSpot's self-service admin console lets them build custom objects, define deal pipelines, and activate workflows without a partner engagement, cutting the initial investment and accelerating time-to-value. Ongoing adjustments can be handled internally, shortening the iteration cycle.
- The split lead‑contact architecture in Dynamics 365 Sales introduces duplicate‑record risk and forces reps to manually run a conversion workflow whenever a lead qualifies, adding steps that reduce sales velocity. In HubSpot, a single contact record with lifecycle stage consolidates prospect and customer data, giving reps immediate visibility into every account interaction from initial visit through closed‑won. This unified model also simplifies reporting on pipeline health and reduces the overhead of maintaining synchronization between separate lead and contact tables.
- Dynamics business process flows are tightly coupled to the underlying opportunity stage — changing one requires modifying the workflow in the Power Platform designer. HubSpot deal pipelines are more accessible to sales ops teams without developer involvement, reducing the maintenance burden on IT.
- G2 reviewers consistently note that HubSpot's onboarding is faster for new reps than Dynamics 365 Sales, with less training required before sellers can log activity and move deals through the pipeline independently. The guided setup wizard, pre‑built templates for deals, tasks, and emails, and intuitive navigation reduce the learning curve, allowing sales teams to become productive within days rather than weeks. HubSpot's knowledge base and community forums also supply quick answers, reducing ramp‑up time.
- Organizations that run Dynamics 365 Sales alongside a separate marketing automation platform incur double CRM licensing fees and must maintain data‑synchronization pipelines to keep contact and activity records consistent across systems. Consolidating onto HubSpot's integrated CRM with Marketing Hub removes the need for sync scripts, reduces licensing expense, and provides a single source of truth for all prospect and customer data. Reporting in one dashboard lets marketing and sales teams align on pipeline metrics without reconciliation errors, improving campaign ROI.

Questions, answered

## Dynamics 365 to HubSpot migration questions

How long does a Dynamics 365 Sales to HubSpot migration take?

Most Dynamics-to-HubSpot migrations complete within 24–72 hours of clock time for under 50,000 records. Complex setups with 500,000+ records or multiple custom Dataverse entities extend to 5–10 days. The pre-migration planning phase — mapping business process flows to HubSpot pipelines and defining StateCode-to-lifecycle-stage routing rules — typically adds 3–5 business days and is the longest dependency before data moves. Field-level diff validation on the sample migration run adds 4–8 hours.

Will my Dynamics 365 Sales workflows and business process flows migrate to HubSpot?

No. FlitStack AI migrates data and schema only — Dynamics workflows, business process flows, plugin assemblies, SLA configurations, and Power Automate flows do not transfer. HubSpot has no native equivalent to Dynamics business process flows, and your stage-specific logic, required-field rules, and SLA timers must be rebuilt inside HubSpot's workflow builder. We export your Dynamics business process flow definitions (stepname sequences and stage labels) as a rebuild reference for your HubSpot admin.

What does a Dynamics Lead become in HubSpot if it was never converted?

Unconverted Dynamics Leads become HubSpot Contacts at the lifecycle stage you specify in the routing table — typically 'lead' for new leads or 'MQL' for leads with a marketing attribution. We preserve the original Dynamics Lead creation date as Original\_Create\_Date\_\_c and the Dynamics StateCode and StatusCode as custom properties so the qualification history is visible in HubSpot. The Dynamics lead GUID is stored as Dynamics\_Lead\_ID\_\_c for traceability.

Can I migrate Dynamics custom entities to HubSpot custom objects?

Yes. Dynamics custom Dataverse tables migrate 1:1 to HubSpot custom objects. All custom fields on those entities transfer as HubSpot custom properties. Lookup relationships from custom entities to Account or Contact map to HubSpot association labels. N-to-N junction tables in Dynamics map cleanly to HubSpot many-to-many associations. We surface multi-lookup cases (e.g., two Account lookups on the same custom entity) in the pre-migration schema plan so your team can name each association label distinctly before migration.

How does Dynamics opportunity stepname map to a HubSpot deal stage?

Dynamics stores pipeline stage as stepname within a business process flow — not as a field on the Opportunity itself. We extract stepname for each Opportunity and map it to the corresponding HubSpot deal stage in the target pipeline. Stage probability from Dynamics closeprobability transfers to HubSpot stage probability. Stage entry dates map to HubSpot deal stage history timestamps. However, stage-specific required fields and branching logic from the Dynamics business process flow must be rebuilt manually in HubSpot's workflow builder.

Does the migration affect my Dynamics 365 Sales account during the cutover?

No. FlitStack AI uses read-only scoped access to Dynamics 365 via the Dataverse API — your team continues working in Dynamics throughout the migration. A delta-pickup window (24–48 hours after the initial run) captures any records created or modified during the cutover window so HubSpot reflects the final state of Dynamics at go-live. There is no downtime in Dynamics and no risk of data being locked or modified by the migration process.

What happens to my Dynamics opportunity contact roles (Decision Maker, Evaluator) in HubSpot?

Dynamics OpportunityContactRelation with RoleName maps to HubSpot deal-contact associations. The primary contact lands as the default association on the HubSpot Deal. Additional contacts and their role names are preserved as a custom property (Contact\_Role\_\_c) on the deal-contact link so the role context is retained for reference. Note that HubSpot's native deal card UI does not display role names by default — you can surface them in a custom HubSpot property on the contact record if needed.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot.webp) Migrate to **HubSpot** Every source we move into HubSpot, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/hubspot)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**HubSpot to Dynamics 365** The same pair in reverse](https://flitstack.ai/migrations/crm/hubspot/to/dynamics-365-sales) [**Cision to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/cision/to/hubspot) [**Yardi to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/yardi/to/hubspot) [**SendCloud to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sendcloud/to/hubspot) [**monday CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/monday-crm/to/hubspot) [**Clio to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/clio/to/hubspot) [**Aweber to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/aweber/to/hubspot) [**Dynamics 365 to Freshsales** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/freshsales) [**Dynamics 365 to monday CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/monday-crm) [**Dynamics 365 to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/zoho-crm)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
3. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
4. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
5. [Dynamics 365 environment strategy — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/environment-strategy-guidance-product)
6. [Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/basics/import-accounts-leads-other-data?view=op-9-1)
7. [Import data (all record types) — Power Platform | Microsoft Learn](https://learn.microsoft.com/en-us/power-platform/admin/import-data-all-record-types)

Get a quote

## Moving from Dynamics 365 to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
