Skip to content
Migrations to Dynamics 365
Move to the cloud without losing what works.
From CRM 4.0, on-premises Dynamics or Salesforce to Dynamics 365 online, with a cutover the business barely notices.
The largest in its country
4.2 TB
Migrated for a national healthcare service, live in one weekend for 7,500+ users
A FastTrack load, then a month of delta migration.
- A FastTrack initial load from on-premises to Dynamics 365 online.
- A .NET delta migration harness on the Dataverse SDK with real-time mapping, at over 2 million transactions an hour.
- Validated table by table, record by record and column by column, then a one-weekend Big Bang go-live with no disruption.
The client calls it “the largest Dynamics CRM migration ever carried out” in its country.
Where you are starting from
Four starting points, each with its own route.
01Dynamics CRM 4.0 and 2011
Long-serving, usually heavily customised, well past support. Usually a rebuild on Dataverse with a data migration.
02On-premises CRM 2013 to Dynamics 365 9.x
Closer to the cloud. From 9.0, often one Microsoft-assisted lift through FastTrack.
03Salesforce and other CRMs
A different platform, so always a rebuild and a mapped data migration, never a lift.
04Several Dynamics 365 tenants
After a merger, an acquisition or years of separate buying. The goal is one tenant and one view of the customer.
01 · Delta migration
Shrink the cutover to a weekend.
Load the history weeks ahead, keep the target in step, and move only the last changes at cutover.
02 · Validation
Proved, record by record.
Every table reconciled and every record accounted for, rehearsed until the cutover is routine.
03 · Tenant consolidation
Several tenants, one source of truth.
No button merges two tenants. Map identities, reconcile duplicates, keep record IDs, then retire the old systems.
Track record
From CRM 2011 to the cloud, at every scale.
2026A national healthcare serviceFor Microsoft
On-premises Dynamics CRM to Dynamics 365 online: 4.2 TB, 100+ integrations, one weekend.
2026Principality Building Society
Proof-of-concept migrations of on-premises Dynamics CRM in hours instead of weeks, using automated build MCPs.
2019AllianzFor Microsoft
CRM 2011 to Dynamics 365 Customer Service online and Azure.
Ways to start
An assessment first, then the right route.
2 to 3 weeks · fixed scopeMigration assessment
The source, the scope, the right route and the risks, before any data moves.
Ask about this
Contract · multi-monthMigration lead
I own the migration design and lead its build, rehearsals and cutover, inside your team.
Ask about this
ProjectCutover support
A focused push to bring a migration to a clean go-live.
Ask about this
Planning a move to Dynamics 365?
Find the route that fits.
Ask me about Hugo's work, books or labs.
Hello. I can answer questions about Hugo's work, his books and OnDynamics Labs. Pick a question to start.
