Seats
Every Dynamics Sales licence, including the ones assigned to people who left, the ones for reps who live in Outlook, and the ones bought at renewal "in case."
We sell outcomes. Not hours.
It comes in the same contract, priced so the seats look close to free, and it stays because switching feels like a project nobody has time for. Meanwhile the real cost sits in three places the invoice never shows: reps who log the minimum, a forecast that gets rebuilt in a spreadsheet, and a partner ticket for every field and report. We move sales and marketing to HubSpot for a fixed, published price. Dynamics 365 keeps doing the finance and operations work it is good at.
The seat price is the smallest number on this list. Work out your own.
Every Dynamics Sales licence, including the ones assigned to people who left, the ones for reps who live in Outlook, and the ones bought at renewal "in case."
A new field, a new stage, a new dashboard. Each one is quoted, scheduled and billed. Most companies we meet cannot say what they spent on Dynamics changes last year, because it arrived across a dozen invoices.
Dynamics Marketing, Customer Insights, or a separate platform with an overnight sync. Another licence, another integration to keep alive, and lead handoff that still happens by email.
Someone rebuilds the forecast every week from exports because nobody trusts the pipeline view. That is a salary line, and it never appears on a software budget.
Adoption is where the licence money goes to die, and it is not the reps' fault. Dynamics CRM was configured for the finance-led rollout it arrived with. Screens carry fields sales never fills in. Logging a call takes more clicks than the call took. Mobile is an afterthought.
So reps do what reps do: they keep the real pipeline in their head, their inbox and a spreadsheet, and type the minimum into the CRM on Friday afternoon. The forecast then reflects Friday afternoon. Management stops believing it, the RevOps lead rebuilds it by hand, and the CRM becomes a compliance record rather than the place work happens.
CyberProof ran marketing and its SDR team in HubSpot and sales in Microsoft Dynamics, joined by the native connector. Every qualified lead meant an SDR switching systems to re-convert it, open the account and create the opportunity by hand in Dynamics, and the connector kept producing sync errors between the two. The security business was scaling faster than that process could. How it was fixed →

No. Dynamics 365 stays the system of record for finance, inventory and fulfilment. HubSpot becomes the system of record for contacts, companies, deals, quotes and marketing. Between them sits an integration that carries the fields each side needs.
Other partners will quote you "move everything." Everything is expensive, takes a year, and produces a copy of your ERP data that drifts within a quarter. Sales needs three fields from the ERP, and we have written about which three: Manufacturers Don't Need the ERP in HubSpot. They Need Three Fields.
The Dynamics 365 integration is priced here, before any call: $2.5k on the native connector, $10k for a custom integration. The same figures as the pricing page and the migration calculator.
Four phases, the same ones in our statements of work. Most mid-market full-stack migrations complete within four months, with ongoing support after go-live if you want it.
Many of the manufacturers we talk to run Dynamics 365 or Dynamics CRM. What changes when the quote is the unit of work is on the manufacturing page.
We added Sales Hub to the HubSpot portal CyberProof already had, rebuilt the Dynamics sales process and deal-stage automations in HubSpot, migrated every object plus tasks and appointments, and disconnected the connector once each property was mapped. Dynamics stayed where the parent company needed it: project IDs and resource planning, with the ID written back onto the HubSpot deal.
Different source system, same discipline.

About 2,000 duplicates removed and roughly 50 campaigns rebuilt.
So every outcome has a price on it, published here, on our pricing page and inside our calculators. Same figures in all three places. Most partners would rather you booked a call before you saw a number. We would rather you saw the number first.
Starts at $40k for one hub and rises with scope. The migration fee is flat however many systems you are leaving, so Dynamics CRM plus a separate marketing platform costs the same as Dynamics alone. Typical two-hub moves land around $80k; a full revenue stack with CPQ and custom integrations around $150k.
Native connector where the field set is simple. A custom integration where the business logic is not, including the project-ID handoff we built for CyberProof.
A report and a roadmap for the portal you already have. Every dollar of it is credited if we go on to do the work.
A named team with SLAs, running the CRM as part of operations. Worth putting next to your current partner tickets.
Work out your own figure before you talk to anyone.

Three situations where we will tell you so on the first call.
The seat price is usually the smallest part. The larger costs are partner tickets for every change, a separate marketing layer, and the time spent rebuilding forecasts outside the CRM because the pipeline in it is not trusted. The migration calculator lets you put your own numbers against the move.
Yes. That is the most common shape of the work. Dynamics stays the system of record for finance, inventory and fulfilment; HubSpot takes contacts, deals, quotes and marketing; an integration carries the fields each side needs.
Accounts, contacts, leads, opportunities, activity history, notes and attachments, plus the custom entities that hold real data. We map each Dynamics entity to a HubSpot object during discovery and reconcile counts before go-live.
Through the native connector where the field set is simple ($2.5k), or a custom integration where the business logic is not ($10k). Same figures as the pricing page.
Most mid-market full-stack migrations complete within four months, with ongoing support after go-live if you want it.
From $40k for one hub. The migration fee is flat however many systems you are leaving. The calculator shows the working without asking for an email.
Work out what the move costs for your portal first. When you want it checked against your actual Dynamics setup, that is what the call is for.