Skip to content
Dynamics 365 to HubSpot: A Field Mapping and Compatibility Guide

Dynamics 365 to HubSpot: A Field Mapping and Compatibility Guide

  • Ujjwal Ujjwal
  • Date: November 17, 2026
  • 9 min read

Most Dynamics 365 to HubSpot problems are not transfer problems. The records move. What goes wrong is that a value that meant one thing in Dataverse means something slightly different in HubSpot: a lead that is already a contact, an owner that is a team, a date that shifts by a day, a calculated column that arrives as a frozen number.

Field mapping is where those differences are found and decided. This guide covers how to audit your Dynamics 365 Sales data, how its objects and column types line up with HubSpot, which data needs a decision rather than a straight copy, and how to test the result before anyone relies on it. It also shows where SuprSwitch, SuprDense’s CRM migration platform, takes on that work through its four phases: Schema Analysis, Mapping Logic, Pilot Validation, and Final Execution.

Audit Your Dynamics 365 Sales Data

Start from what you actually use, not from what the system could store. Dynamics 365 Sales tables carry many columns that are empty, duplicated by a custom column someone added later, or only used by a process that no longer runs. Mapping all of them copies the clutter into HubSpot.

For each table you plan to move, record four things: the record count, the columns that are populated for most records, the columns that reports, views, or business rules depend on, and the columns that are custom. Mark each column as migrate, merge into another column, archive outside the CRM, or drop. Ask the people who use the data, because a column that looks dead in a database export can still be what a sales manager filters on every Monday.

HubSpot Smart Transfer, the data transfer tool HubSpot provides for Dynamics 365, includes an audit step that shows how each object maps, record counts, configuration details such as pipelines and fields, and settings such as users, currencies, and date formats. It is a useful starting inventory. It still needs a person to decide which columns deserve to be kept.

SuprSwitch’s Schema Analysis phase builds the same kind of inventory across the whole org. It scans Dynamics 365 and surfaces every custom field, record count, and property type, and flags duplicates, empty required fields, and broken associations before any data moves.

Compare Standard Objects and Properties

Dynamics 365 Sales and HubSpot do not use the same object model. The table below shows how HubSpot Smart Transfer maps Dynamics 365 tables, and it is the best starting point for your own worksheet. Check it against your own audit, because the supported list can change.

Dynamics 365 tableHubSpot objectWhat to check
AccountsCompaniesHubSpot matches companies by domain, so accounts without a website need another plan
ContactsContactsHubSpot matches contacts by email address
LeadsContactsQualified leads may already exist as contacts, accounts, and opportunities
OpportunitiesDealsStages, probability, close dates, and the open, won, or lost status
Products, BundlesProducts, BundlesOpportunity products can move as deal line items in a one-time transfer
Sales Orders, InvoicesOrders, InvoicesConfirm you need them in HubSpot before migrating
CasesTicketsConfirm you need service history in HubSpot
Emails, Phone calls, Appointments, Tasks, NotesEmail activities, Calls, Meetings, Tasks, NotesSee section 5
Users, SegmentsUsers, SegmentsUsers are created before records can be assigned to them

Two points matter before you map a single column. First, leads and contacts both land in HubSpot as contacts, so your lead process has to be redesigned as lifecycle stages and lead status rather than copied. Second, anything Dynamics 365 stores that is not in the table above, including custom tables, needs its own plan (see section 6).

Map Contacts, Companies, and Deals

Contacts and companies are the most straightforward objects because both platforms are built around people and organizations. The work is in identity and in hierarchy.

  • Contacts: HubSpot deduplicates contacts by email address. Dynamics 365 contacts without an email, or with the same email on several records, will merge or fail to match. Decide which record wins before you import, not after.
  • Companies: HubSpot deduplicates companies by domain name. Dynamics 365 accounts are often created by name only, so several accounts for the same organization can collapse into one company, while accounts without a domain stay separate. Clean or add domains first.
  • Parent and child accounts: A Dynamics 365 account can have a parent account. In HubSpot this becomes a parent and child association between companies, so check that the hierarchy is preserved and not flattened.
  • Leads: A lead in Dynamics 365 becomes a contact in HubSpot. Because qualifying a lead in Dynamics 365 can create an account, a contact, and an opportunity, a qualified lead may appear twice. Move unqualified leads as contacts and exclude those already converted.

Deals need the most care. A Dynamics 365 opportunity has a sales stage, a probability, an estimated revenue, estimated and actual close dates, and a status of open, won, or lost. HubSpot deals have a pipeline, a deal stage, an amount, and a close date. The default HubSpot Sales pipeline has these stages: Appointment scheduled, Qualified to buy, Presentation scheduled, Decision maker bought-in, Contract sent, Closed won, and Closed lost. Your Dynamics 365 stages will not match these names, so map each one explicitly, and decide where won and lost opportunities land.

For Dynamics 365, Smart Transfer creates helper workflows that carry over the original created date of a deal and its close date, using the Created On, Actual Close Date, and Est. Close Date columns. If you map deals another way, plan how those dates will be set, because HubSpot sets the create date when the record is created.

In SuprSwitch, pipelines are mapped in the same step as fields. You can create new HubSpot pipelines, merge several Dynamics 365 pipelines and their stages into one, or map each stage to an existing HubSpot stage.

Handle Custom Fields and Data Types

Dynamics 365 columns are typed. HubSpot properties are typed too, but the types do not line up one to one. Map each custom column by its Dataverse type, then choose the HubSpot field type that keeps the data usable.

Dataverse column typeHubSpot property typeWatch for
Single line of text, multiple lines of textSingle-line text, multi-line textHubSpot text properties hold up to 65,536 characters in the CRM[1], so check the longest values
Choice (option set)Dropdown selectCreate the options in HubSpot first and keep the labels consistent
Choices (multi-select)Multiple checkboxesValues arrive as a list in a single property
Yes/No (two options)Single checkboxLabels other than Yes and No need a decision
Whole number, decimal, floating pointNumberDecide on formatted or unformatted, and check decimal places
CurrencyNumber (currency format)See the note on currencies below
Date only, date and timeDate picker, date and time pickerTime zone behavior can move a date by a day
LookupAssociationBecomes a relationship, not a field
CustomerAssociation to a contact or a companyCan point to either, so it needs a rule
OwnerContact, company, or deal ownerSee section 5
Calculated columnCalculation property, or a plain valueSee section 6
File, ImageFile propertyLimited to 10 files per property and a size cap per file[1]
Duration, Time zone, Language (whole numbers with formats)Number or dropdownDisplay meaning may be lost if you map the raw number

Three of these cause most of the trouble.

  • Dates and time zones: Dataverse stores date and time values in UTC and shows them in the user’s time zone unless the column is set to be time zone independent. A date-only column that adjusts to the user’s time zone can show a different calendar day to different users. Test birthdays, renewal dates, and close dates by comparing a known record in both systems.
  • Picklists: HubSpot dropdown and checkbox properties hold a defined list of options. A value that is not in the list will be rejected or ignored, so build the list from the Dataverse choices first, and decide what to do with retired options that still appear on old records.
  • Currencies: HubSpot supports multiple currencies on Starter, Professional, and Enterprise subscriptions. Set your company currency and add the others, with exchange rates, before importing deals, so deal amounts are recorded against the correct currency.

A tool such as the SuprSwitch CRM migration platform is built for this step: it lets you map objects and properties, create missing properties, and merge duplicates before the data moves. Whatever you use, do the mapping in a worksheet first (section 7). In SuprSwitch’s Mapping Logic phase, standard objects and default properties are mapped automatically, custom columns are mapped from a drop-down, and a missing HubSpot property can be created in a single click.

Map Owners, Activities, and Relationships

Owners, activities, and relationships are where a migration that looks complete often turns out to be unusable, because the records are there but nobody can see who owns them or what happened.

Owners

In Dataverse, the owner of a record can be a user or a team. In HubSpot, the owner of a record is a user. Teams in HubSpot group users for reporting and access, but they are not owners. So for every Dynamics 365 record owned by a team, choose a rule before the move: assign it to a named person, assign it to a default owner, or keep the team name in a separate property. Also deal with deactivated users. If a former employee owned a large share of your contacts, decide whether the records go to someone else, whether the former employee is created as a user so history stays intact, or whether the original owner is kept in a custom property for reporting. Users must exist in HubSpot before records can be assigned to them, and HubSpot also has a user-type property for any extra role you want to keep, such as a secondary owner.

SuprSwitch’s ownership transfer engine resolves records owned by deactivated users before anything moves, and SuprSwitch can migrate deactivated users so historical ownership stays attached to the right records. Users whose email address matches in both systems are mapped automatically.

Activities

Dynamics 365 tracks activities such as emails, phone calls, tasks, and appointments, and notes are added from the timeline and can carry attachments. Smart Transfer maps them to emails, calls, tasks, meetings, and notes in HubSpot. Two cautions apply. Activities are hard to redo: HubSpot’s import tool cannot update existing emails, meetings, notes, or tasks, so run a small sample and check it before the full transfer. And check whether attachments are included for your case in the Smart Transfer audit, since the list of one-time transfers differs by source application.

SuprSwitch migrates notes, calls, meetings, and tasks along with email history, and its activity-type mapping keeps each Dynamics 365 activity on the matching HubSpot activity type.

Relationships

A lookup column in Dataverse becomes an association in HubSpot. Contacts to companies, opportunities to accounts and contacts, and activities to the records they belong to all need to survive the move. The Customer column on an opportunity can reference either an account or a contact, so map the two cases separately. A contact can be associated with more than one company in HubSpot, with one marked as primary, and association labels such as decision maker or billing contact are available on Professional and Enterprise subscriptions. If your Dynamics 365 relationships carry a role, decide whether to keep it as a label. SuprSwitch’s association integrity mapping preserves these one-to-one and labeled relationships as records move.

Identify Unsupported or Differently Structured Data

Some Dynamics 365 data has no direct home in HubSpot. List it early so the decision is made by the business and not by the migration team halfway through.

  • Custom tables: Smart Transfer does not support custom objects. HubSpot custom objects require an Enterprise subscription, so a custom table either needs that plan, needs to become a standard object with extra properties, or needs to stay outside the CRM.
  • Calculated and rollup columns: The values can be transferred, but the logic is not. Without a rebuild they arrive as fixed numbers that go stale. HubSpot has calculation and rollup properties, and calculation properties need a Professional or Enterprise subscription.
  • Business process flows and workflows: Dynamics 365 processes, plugins, and flows are not copied as data. Smart Transfer creates helper workflows for deal dates, not your automations. Rebuild the automations you still need in HubSpot, which requires Professional or Enterprise for workflows.
  • Status and status reason: Dynamics 365 splits state and reason. HubSpot has one deal stage, and closed won and closed lost are stages. Map the pair into a single stage.
  • Security roles and field security: Who can see what in Dataverse does not carry over. Rebuild access with HubSpot permissions and teams.
  • Files and images: Check sizes and counts against HubSpot’s file property limits, and decide whether the files should live in HubSpot at all.

Be clear in the plan about which of these are rebuilt, which are archived, and which are dropped. Dropped data should be exported and stored, not deleted.

SuprSwitch maps any field or object that lives in the source CRM, so custom tables can be rebuilt as HubSpot custom objects on an Enterprise account. Automations are different. Workflows, plugins, and business process flows are logic, not data, so they are rebuilt in HubSpot whichever migration tool you use.

Create a Field Mapping Worksheet

A field mapping worksheet is the single document that every migration decision ends up in. One row per column, filled in before any data moves, reviewed by the business owner of that data. A usable worksheet has these columns, shown here with two illustrative rows.

Dynamics 365 table and columnDataverse typeHubSpot object and propertyHubSpot typeTransformation or ruleStatus
Account: IndustryChoiceCompany: IndustryDropdown selectMap each value to the HubSpot list; merge retired values into OtherApproved
Opportunity: Est. Close DateDate onlyDeal: Close dateDate pickerCheck time zone behavior on a sampleTesting

Add columns for the record count, the owner of the decision, the sample value before and after, and any open question. Three habits keep the worksheet honest. Give every column a status, so anyone can see what is still undecided. Keep unmapped columns in the sheet with a reason, not off it. And version it, because mappings change when someone finds that a field was used in a way nobody expected.

The worksheet is one part of a wider plan. Our guide to CRM data migration best practices covers the checks that surround it, from cleaning the source to cutover.

Test and Reconcile Migrated Records

Do not test with the full dataset. Move a representative sample first: a few hundred records that include the awkward cases, such as contacts with no email, accounts with a parent, opportunities in each state, records with several activities, and records owned by deactivated users.

This is SuprSwitch’s Pilot Validation phase, which checks relational integrity, activity formatting, field truncation, and association chains on the sample before the full load.

Then check the result against the source in three ways.

  • Counts: Compare the number of records per object in Dynamics 365 and in HubSpot. Smart Transfer’s audit gives you a count per object for the source, and you can run a second audit to see what has changed. Account for records you intentionally excluded, so every difference has an explanation.
  • Values: Pull a sample of records and compare each mapped column side by side, including dates, amounts, picklists, and owners. Add the totals: the sum of open deal amounts by stage should agree in both systems, after allowing for currency.
  • Relationships: Open several records in HubSpot and check that the contact, company, deal, and activities are connected the way they were in Dynamics 365.

Fix the worksheet, not the data, whenever you find a pattern, and run the sample again. Keep the error log from each transfer, because it lists the records that failed and why. When you are satisfied, run the full migration, and then repeat the same three checks on the whole dataset before you switch users over. Smart Transfer allows a transfer to be reverted, which is worth knowing before the first full run.

During Final Execution, SuprSwitch’s real-time record validation flags any record that does not appear in HubSpot within the expected window, and its retry mechanism re-runs failed records without restarting the whole job. Its no-storage architecture means your Dynamics 365 data is never held on SuprSwitch servers.

Treat sign-off as a business decision. Ask a sales manager and a marketing owner to look at their own records, because they will notice what a count never shows.

Conclusion

Dynamics 365 to HubSpot field mapping is mostly a matter of making decisions early: which columns matter, how leads and contacts merge, who owns records that belonged to a team, what happens to custom tables and calculated columns, and how dates and currencies are read. Write each decision in the worksheet, test on a sample, and reconcile counts, values, and relationships before go-live.

SuprSwitch simplifies Dynamics 365 to HubSpot migration with a structured process: data mapping, sample migration, and full migration with real-time validation. Looking to migrate your Dynamics 365 data to HubSpot seamlessly? Contact SuprDense to discuss your CRM migration requirements and get expert assistance from our team.

References

[1] HubSpot Knowledge Base, Understand property field types in HubSpot. https://knowledge.hubspot.com/properties/property-field-types-in-hubspot

Frequently Asked Questions

01 Can Dynamics 365 Sales data be migrated to HubSpot?

Yes. Contacts, accounts, leads, opportunities, products, activities, notes, and users can all be moved. HubSpot Smart Transfer supports Dynamics 365 as a source and maps accounts to companies and opportunities to deals, and a migration platform or a consultant can handle what it does not cover. Custom tables, automations, and security settings need separate planning. SuprSwitch, SuprDense’s migration platform, maps custom fields and custom tables as well as owners, activities, and associations.

02 How do you map custom fields between the platforms?

Map each custom column by its Dataverse type to a HubSpot property type: choices to dropdown or checkbox properties, numbers to number properties, dates to date pickers, and lookups to associations. Create the HubSpot properties first, rebuild picklist options, and record the rule for each column in a mapping worksheet.

03 What happens to unsupported data types?

It does not move automatically. Custom tables need a HubSpot Enterprise subscription for custom objects or a different design, calculated columns arrive as static values unless rebuilt as calculation properties, and automations must be recreated as HubSpot workflows. Anything dropped should be exported and kept.

04 Can owners and activities be transferred?

Yes. Users are created in HubSpot so records can be assigned to them, and emails, calls, tasks, meetings, and notes are mapped to HubSpot activities. Team-owned records need a rule, because a HubSpot record owner is a user, and activities should be tested on a sample first.

05 How should field mapping be tested?

Test a sample that includes your difficult records, compare counts, values, and associations against Dynamics 365, update the worksheet, and run the sample again. Run the same checks on the full migration before users switch.

Manual migrations cost more than engineer hours.

Skip the QA cycles, data cleanup, and errors found weeks after go-live. SuprSwitch runs the full migration in 3-4 days, validated record by record.