HubSpot's new pricing has been live in EMEA since October 1. See what your team would pay

Dynamics to HubSpot · Shani Wolf, HubSpot, monday & Amplemarket partner

FromDynamics to HubSpot, up to SQL

You pay for HubSpot Pro and use it for website forms, while lead management lives in Dynamics. The migration moves the leads to HubSpot, from the form to the point where sales takes over, and leaves Dynamics doing what it does well. Three stages, with a plan before you commit.

Book a platform call The three stages
3stages1–2weeks for the plan$0onboarding fee, through a partner
A team working on laptops and tablets HubSpot Solutions Partner

Who it's for

Three situations I keep meeting

Paying, not using

HubSpot Pro for forms only

A full license at 10% utilization. Leads drop into Dynamics and disappear there. The decision: HubSpot owns the lead up to SQL.

The common case
Microsoft shop

Dynamics because it's Microsoft

Everything runs on Microsoft 365, so the CRM does too. But marketing needs automation, scoring and reports. HubSpot connects to Outlook and Teams just like Dynamics does.

Alongside Dynamics
Ongoing partner

Someone has to run the portal

After the migration, a fixed number of hours a month: automations, reports, the team's questions. A block of hours with the person who built it.

Ongoing support
Three stages

Discovery and plan, implementation, support

Stage one: discovery and a migration plan, at a fixed price. At the end you know the implementation scope and its price, before you commit. Stage three: ongoing support or a block of hours, only if you need it.

What's in the plan
  • What moves from Dynamics and what stays there
  • The lead path: form → scoring → nurturing → SQL → sales
  • The connection between the systems, and who owns each field
  • Implementation scope and price, in numbers
1discovery and plan: fixed price
2implementation: per the plan
3support: monthly or a block of hours
$0HubSpot onboarding fee

How does it work?

From forms only to full lead management, in a quarter

  1. Discovery

    Who works where, and what really has to move

  2. Plan

    Scope, price, timeline

  3. Build

    Leads, scoring, nurturing, handoff at SQL

  4. Connect

    Dynamics gets what it needs, nothing more

  5. Support

    Fixed hours, or the team runs it alone

Frequently asked questions

Why not just work in Dynamics?
You can, if marketing doesn't need automation, lead scoring and nurturing. In most B2B companies it does, and that is exactly what HubSpot does well. The common solution is to split rather than choose: HubSpot up to SQL, Dynamics from there.
What does the discovery and plan stage cost?
A short fixed-price project, one to two weeks. At the end there's a migration plan, and the implementation scope and price are known before you commit.
What does support after the migration include?
Two options: ongoing portal management for a monthly fee (three months minimum), or a block of hours. Both with the person who built the portal.
We're a Microsoft 365 organization. Does this work?
Yes. HubSpot connects to Outlook and Teams, and SharePoint stays the home for documents. It has a page of its own: HubSpot in a Microsoft 365 organization.

Last updated: October 2026

Shani Wolf

Written by

Shani Wolf
Fractional CMO · MarTech & CRM consulting · HubSpot, monday & Amplemarket partner

15+ years in B2B marketing, from global enterprises to high-growth startups. I get into the systems, the data and the automations and build and fix them myself, so the marketing budget turns into a predictable, measurable revenue engine.

LinkedIn About me Book 30 minutes

Still looking around? Fair enough

The calculator: what it would cost Microsoft 365 and SharePoint