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 data | HubSpot Smart Transfer | Gap |
|---|---|---|
| Accounts, contacts, leads, opportunities | Yes | Leads and contacts both become HubSpot contacts; decide on lifecycle stages up front |
| Emails, appointments, notes, tasks, phone calls | Yes (appointments become meetings) | Custom activity tables aren’t listed |
| Opportunity products | One-time transfer as deal line items | Products must exist in HubSpot |
| Note attachments | Not listed | Extract from annotation.documentbody |
| Custom entities | Not supported | Need HubSpot custom objects (Enterprise) |
| Workflows, business rules, Power Automate flows | No | Rebuild 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
- List each custom table: its columns, lookups and row count. Decide whether it becomes a HubSpot custom object or just properties on a record.
- Create the custom object in HubSpot with a unique “Dynamics ID” property and association types to contacts, companies and deals.
- Extract rows through the Dataverse Web API, with the GUIDs of their lookups.
- Import the custom object records, matching each one to its parent company by Record ID or domain in the same row.
- Extract note files from the annotation table, upload them to HubSpot and link them to the records.
- 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.