Skip to content
Get a quote

How do I migrate Microsoft Dynamics 365 data, including custom entities, to HubSpot?

Short answer

Use HubSpot Smart Transfer for standard Dynamics 365 records and activities: emails, appointments, notes, tasks and phone calls. It doesn't support custom objects, so custom entities need HubSpot custom objects (an Enterprise subscription) and a separate load via the Dataverse API and HubSpot's importer. Dynamics stores note files as Base64 data in the annotation table, so extract them separately.

By

What makes Dynamics different

Dynamics 365 Sales runs on Dataverse. Every activity type (email, phone call, appointment, task, plus any custom activities) is its own table, tied together by the ActivityPointer table, and participants are stored as activity parties. Notes live in the annotation table, which holds each file as Base64 text in documentbody. Custom entities are ordinary Dataverse tables with lookups to accounts, contacts or opportunities. All of these need mapping work.

What the native tools do / where they stop

Dynamics dataHubSpot Smart TransferGap
Accounts, contacts, leads, opportunitiesYesLeads and contacts both become HubSpot contacts; decide on lifecycle stages up front
Emails, appointments, notes, tasks, phone callsYes (appointments become meetings)Custom activity tables aren’t listed
Opportunity productsOne-time transfer as deal line itemsProducts must exist in HubSpot
Note attachmentsNot listedExtract from annotation.documentbody
Custom entitiesNot supportedNeed HubSpot custom objects (Enterprise)
Workflows, business rules, Power Automate flowsNoRebuild them as HubSpot workflows

Excel export from the Dynamics UI is capped at 100,000 rows at a time. That’s fine for a lookup table, but too low for activity history.

Steps for custom entities

  1. List each custom table: its columns, lookups and row count. Decide whether it becomes a HubSpot custom object or just properties on a record.
  2. Create the custom object in HubSpot with a unique “Dynamics ID” property and association types to contacts, companies and deals.
  3. Extract rows through the Dataverse Web API, with the GUIDs of their lookups.
  4. Import the custom object records, matching each one to its parent company by Record ID or domain in the same row.
  5. Extract note files from the annotation table, upload them to HubSpot and link them to the records.
  6. Reconcile row counts per custom table and spot-check associations.

Where FlitStack AI fits

FlitStack AI maps Dynamics custom entities to HubSpot custom objects and moves every activity table and note attachment, with timestamps preserved. See Dynamics 365 to HubSpot or HubSpot migrations.

Questions, answered

A few useful answers.

Can I export Dynamics data to Excel instead?

For small tables, yes, but model-driven apps export up to 100,000 rows at a time and don't include note attachments. For a full migration, use the Dataverse Web API.

How do Dynamics opportunity products come across?

Smart Transfer brings opportunity products over as a one-time transfer of HubSpot deal line items. Make sure the products exist in HubSpot's product library first.

What if we don't have HubSpot Enterprise for custom objects?

Flatten simple custom entities into properties on contacts, companies or deals, or use notes. Anything with many records per parent really needs a custom object.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote