RevOps + HubSpot 10 min read

Moving from Dynamics to HubSpot: what to plan first

Audit what your team uses, map each Dynamics entity to a HubSpot object, then list the plugins, workflows and integrations to rebuild. HubSpot's Smart Transfer and Dynamics 365 integration move the records; the logic is yours to rebuild.

Head of Client Success

Before you move from Microsoft Dynamics to HubSpot, plan four things in this order: what your team actually uses in Dynamics, where each Dynamics entity will go in HubSpot, which plugins, workflows and integrations have to be rebuilt, and how your people keep working in Outlook and Teams after the switch. The records are the easy part. The logic around them is where the time goes.

HubSpot gives you two built-in routes. Smart Transfer lists Dynamics 365 as a supported source and maps accounts, contacts, leads, opportunities, cases, products, activities, users and sales orders into HubSpot. HubSpot also builds a certified Microsoft Dynamics 365 integration that can sync both ways while you run the two systems side by side. Smart Transfer does not move custom entities, and neither tool converts plugins, classic workflows or Power Automate flows. You list those, decide what to keep, and rebuild the keepers in HubSpot.

If you are on an older Dynamics CRM on-premises, check your version first. HubSpot's integration needs a cloud-hosted Dynamics 365 environment, so an on-premises system usually moves by export and import. For a 50 to 250 person business with integrations and automation to rebuild, plan on roughly eight to twelve weeks from audit to cutover.

When does moving from Dynamics to HubSpot make sense, and when doesn't it?

The move tends to pay off when Dynamics has become a system only one or two people can change. The usual signs:

  • Your Dynamics partner or developer is a bottleneck. Every new field, form or report needs a ticket, and plugins nobody remembers writing fire on save.
  • Marketing already runs somewhere else. Leads come from HubSpot forms or another email tool, and the handover to sales is a sync someone babysits.
  • Your on-premises version is ageing out. Microsoft's extended support for Dynamics CRM 2016 ended in January 2026. Dynamics 365 Customer Engagement version 9.0 on-premises lost support in July 2023, and version 9.1 is supported until January 2031. If you have to upgrade or move to the cloud anyway, it is a natural time to ask which cloud.

Stay put, or connect the two instead of migrating, when Dynamics is deeply tied into Finance and Operations or Field Service, when your service team relies on complex entitlements and case routing you would have to rebuild from scratch, or when a Microsoft enterprise agreement makes the licence change a bigger decision than the CRM itself.

On-premises Dynamics is running out of support
  1. July 2023Dynamics 365 Customer Engagement 9.0 on-premises loses support.
  2. January 2026Extended support ends for Dynamics CRM 2016.
  3. January 2031Support ends for version 9.1 on-premises.

Microsoft lifecycle dates, as cited in the post.

How do Dynamics entities map to HubSpot objects?

This is the table to start from. The left two columns follow HubSpot's published Smart Transfer mapping for Dynamics 365, and the third is what to decide before you load anything.

Dynamics 365HubSpotWhat to decide
AccountsCompaniesThe matching key. Store the Dynamics account ID on the HubSpot company, and keep the ABN as a second check.
ContactsContactsOwners must exist as HubSpot users first, or records arrive unassigned.
LeadsContactsLeads and contacts both become HubSpot contacts. Qualified leads often already have a matching contact, so deduplicate and set lifecycle stage from the source.
OpportunitiesDealsAgree every HubSpot pipeline and stage before import. Products on opportunities come across once as deal line items.
CasesTicketsRebuild queues, SLAs and routing in Service Hub. Case history comes across, the rules around it do not.
Products and bundlesProducts and bundlesCheck GST treatment on each product.
Sales orders and invoicesOrders and invoicesOnly bring them if sales needs them in HubSpot. If an ERP issues them, sync status from there instead.
Appointments, phone calls, tasks, notes, emailsMeetings, calls, tasks, notes, email activitiesHow far back you need activity history. Older years can stay in an archive.
Custom entitiesCustom objects, or properties on a standard objectSmart Transfer does not move custom objects, and HubSpot custom objects need an Enterprise subscription.
Notes attachments and SharePoint documentsAttachments, or left where they areAttachments are not in HubSpot's Dynamics 365 Smart Transfer list. Plan them separately, or link to the SharePoint folder.
Users, teams and business unitsUsers and teamsUsers transfer. Security roles and business units are rebuilt as HubSpot permissions and teams.

Custom entities are usually where the licence question starts. Before you pay for Enterprise to recreate one, ask whether it could be a handful of properties on a company or deal. A "Site Visit" entity with five fields usually can. A "Sites" entity where one customer has forty locations usually needs a real custom object. HubSpot lists custom objects on the Enterprise tier of Sales Hub, Service Hub, Marketing Hub and its other hubs. Sales Hub Enterprise is A$240 a seat a month before GST, against Professional at A$140 a seat a month paid annually (A$155 paid monthly).

The field by field work, dates and record clean up are the same as any CRM move, and our data migration and field mapping checklist covers them in detail.

This session from our YouTube channel, recorded at a HubSpot User Group, covers HubSpot data migration and bringing your data home to Australia.

HubSpot data migration: bringing your data home to Australia, from our YouTube channel. Watch it on YouTube.

What do HubSpot's own tools move from Dynamics 365?

  • Smart Transfer is a migration tool. It lists Dynamics 365 as a supported source, syncs the objects in the table above one way into HubSpot, and adds workflows that backfill each deal's create date and close date from Dynamics' Created On and close date fields. Products on opportunities come across in a one-time transfer after the sync, which will not update if someone changes them in Dynamics later.
  • The Microsoft Dynamics 365 integration is an ongoing sync. HubSpot builds it, and it is a HubSpot Certified App with about 3,000 installs. It maps companies to accounts, contacts to contacts and leads, deals to opportunities, custom objects to entities, plus products, meetings, notes, tasks, calls, emails, invoices and sales orders, one way or two way. You can connect up to two Dynamics 365 instances.

Three conditions apply to the integration. Your Dynamics environment must be cloud-hosted on an official dynamics.com domain. The listing asks for a Dynamics 365 Sales Professional, Enterprise or Premium subscription. And custom field mappings need a paid Data Hub subscription, so budget for it if your Dynamics forms carry more than the standard fields.

Use Smart Transfer for the move itself, and the integration when you want both systems live during a phased cutover. On-premises Dynamics moves by export, by a third-party migration tool, or by upgrading to Dynamics 365 online first. We could not confirm that Smart Transfer connects to an on-premises server, so plan on files.

Records move with HubSpot's tools, the logic is rebuilt by hand
How data and logic get from Dynamics 365 to HubSpotDynamics 365 records go one way into HubSpot through Smart Transfer. The Dynamics 365 integration can sync both ways while the two systems run side by side. Plugins, workflows and custom entities do not move with either tool and are listed and rebuilt in HubSpot.Dynamics 365records and activitySmart Transferone-way move of recordsDynamics 365 integrationtwo-way sync while both runHubSpotcompanies, contacts, dealstickets and activitiesPlugins, workflows and custom entitieslisted, then kept, replaced or retired, and rebuilt in HubSpot

The two HubSpot tools described in the post. The integration needs a cloud-hosted Dynamics 365 environment. Dashed lines are work your team plans and does.

Planning a move off Dynamics?

Talk to Matt about moving your CRM to HubSpot.

Can your team keep working in Outlook and Teams?

Yes. HubSpot has apps for both.

  • Outlook. The HubSpot Sales Office 365 add-in lets reps track and log emails and use HubSpot sales tools from their inbox, in Outlook for Windows, Mac and the web. It is available on all HubSpot plans. A Microsoft 365 admin can deploy it centrally, so every user on the domain gets it without installing anything. Two catches: Outlook installed from the Microsoft Store is not compatible, and the older Outlook desktop add-in is in maintenance mode, so do not install both.
  • Teams. The HubSpot app for Microsoft Teams sends HubSpot notifications to Teams channels, adds Teams meeting links to meetings booked from HubSpot, and lets people create tasks and tickets from Teams. An admin-level install, which needs a Teams Global Admin, adds Teams Phone call logging, webinar sync and connecting support inboxes to Teams channels. You can connect one Teams instance per HubSpot account.

Switch the Dynamics App for Outlook off on cutover day, the same day the HubSpot add-in goes on. If both are logging the same email for a week, you get duplicate activity in one system and gaps in the other.

Plugins, workflows and ERP links: what has to be rebuilt?

None of your Dynamics logic comes across. Export a list from the Dynamics solution and mark each item keep, replace with a HubSpot feature, or retire:

  • Plugins. Microsoft describes a plugin as compiled .NET code that runs when a set event happens to Dataverse data, such as a record being saved. Many enforce rules HubSpot handles with required properties on deal stages. The rest become custom code actions in HubSpot workflows, written in JavaScript or Python (in beta), which need Data Hub Professional or Enterprise.
  • Classic workflows and business rules. Field updates, assignment, task creation and email alerts usually translate one for one into HubSpot workflows.
  • Business process flows. Rebuild the stages that matter as pipeline stages with required fields. Drop the steps people click through without reading.
  • Power Automate flows. Any flow that reads or writes Dynamics data breaks when Dynamics goes. Find each one, then repoint it at HubSpot or rebuild it as a HubSpot workflow.

In most Dynamics systems a fair chunk of that list can be retired. Our guide to Zoho to HubSpot migration walks through the same keep, replace or retire exercise for Zoho's Blueprints and Deluge.

Business Central and other ERPs. If Business Central is connected to Dynamics 365 Sales today, that connection goes when Sales is switched off. HubSpot builds a certified Business Central app with 400 plus installs that syncs customers, items, opportunities and sales orders both ways. Its listing says Business Central customers sync to HubSpot contacts and not yet to companies, so check that fits how you sell before you plan around it. Our guide to connecting HubSpot to your ERP covers which system owns which record and what to sync first.

What does a realistic Dynamics to HubSpot plan look like?

A typical plan for a 50 to 250 person business with a couple of integrations. Your plugin count, custom entities and data quality set the real length.

PhaseWhat happensTypical length
1. Audit and decideList entities with record counts, fields in use, plugins, workflows, Power Automate flows, reports and every integration. Decide what stays behind.1 to 2 weeks
2. Design and build HubSpotUsers and teams, properties, pipelines, custom objects if needed, the Outlook add-in and the Teams app.2 to 3 weeks
3. Test migrationLoad a sample, check record counts, associations, owners and dates against Dynamics, fix the mapping, load again.1 to 2 weeks
4. Rebuild logic and integrationsWorkflows, the keep list from your plugins, ERP and website forms pointed at HubSpot.2 to 4 weeks
5. Cutover and parallel runFinal load, Dynamics set to read only, training, then a week or two of checking before access ends.1 to 2 weeks

Some of those phases overlap, which is how the total lands at roughly eight to twelve weeks. On cost, NBH's published HubSpot implementation ranges run from about $7,000 plus the licence for a guided build, to $15,000 to $35,000 for multi-hub work with integrations, ex GST. See HubSpot implementation for what sits in each range. The Salesforce version of this plan, with its own renewal timing questions, is in moving from Salesforce to HubSpot at 100 plus seats.

Dynamics to HubSpot cutover checklist

  • Full export taken and stored before anything is switched off, including notes attachments and anything in SharePoint, with a named owner and an agreed retention period.
  • Consent and unsubscribes moved first, before any HubSpot marketing email goes out. Our Pipedrive to HubSpot guide covers running both systems during the switch.
  • Every Dynamics user mapped to a HubSpot user, including people who have left, with a decision on who inherits their records.
  • Record counts matched per object between Dynamics and HubSpot, and a sample of twenty records checked by hand for owners, associations and dates.
  • Dynamics set to read only on cutover day, so nobody updates the old system by habit.
  • Dynamics App for Outlook removed and the HubSpot add-in deployed on the same day.
  • Every integration repointed: website forms, ERP, phone system and Power Automate flows, each with an owner who has tested it.
  • Reports rebuilt and compared against last month's Dynamics numbers before your next pipeline meeting runs from HubSpot.
  • Licence end date confirmed in your Microsoft agreement, with the final export done well before it.

Frequently asked questions

Can HubSpot import data from Microsoft Dynamics 365? Yes. HubSpot Smart Transfer lists Dynamics 365 as a supported source and maps accounts, contacts, leads, opportunities, cases, products, activities, users and sales orders into HubSpot. Custom entities are not moved by Smart Transfer and need a separate import.

Does HubSpot integrate with Dynamics 365? Yes. HubSpot builds a certified Microsoft Dynamics 365 integration that syncs companies, contacts, leads, deals, products, activities, invoices and sales orders one way or two way. It needs a cloud-hosted Dynamics 365 environment, and custom field mappings need a Data Hub subscription.

Can I migrate from Dynamics CRM on-premises to HubSpot? Yes, usually by exporting the data and importing it into HubSpot, or with a third-party migration tool. HubSpot's Dynamics integration only connects to Dynamics 365 hosted on a dynamics.com domain.

Does HubSpot work with Outlook and Microsoft Teams? Yes. The HubSpot Sales Office 365 add-in tracks and logs emails in Outlook for Windows, Mac and the web, and the HubSpot app for Teams sends notifications, adds Teams meeting links and creates tasks and tickets. Both are available on all HubSpot plans.

How long does a Dynamics to HubSpot migration take? For a 50 to 250 person business with integrations and automation to rebuild, roughly eight to twelve weeks from audit to cutover. The number of plugins, custom entities and integrations sets the real length.

Sources


Our CRM implementation page sets out how we plan and run a move like this one.

Weighing up a move from Dynamics to HubSpot?

Talk to Matt about your Dynamics migration. He can explain how we work and whether our CRM implementation work fits what you need.

Neighbourhood

Neighbourhood is a HubSpot Diamond Partner in Brisbane. We build AI systems and the revenue operations they run on, for businesses across Australia and New Zealand.