Your practice
You scope the migration with your client, set the price, and decide the cutover window.
Migration capacity Capacité de migration
Migration capacity you can quote as its own project.
Margin and billing already names "quoted separately" without ever spelling it out for a specific case. This page does that for migration: moving workloads to Azure, between hypervisors, or off aging hardware — with its own scope, its own inventory, and its own price, distinct from the monthly per-user anchor.
Delivery team
We plan and execute the technical migration path — on-prem to Azure, or server moves between Hyper-V and VMware — and hand back what changed and what still needs validation.
Migration and server virtualization
For a client project that involves moving servers or workloads — to Azure, between hypervisors, or off aging hardware — rather than day-to-day administration of a stable environment.
What we need first
Access to source and target environments, a closed inventory of what’s moving, and your client’s tolerance for downtime during cutover.
What’s included
- Migration planning for the confirmed inventory
- Execution of the agreed cutover, with a rollback point where technically possible
- A post-migration validation pass against the inventory
Handled separately
- Deciding whether Azure, another cloud, or on-prem virtualization is the right target — that’s your advisory conversation with the client
- Licensing or commercial terms for Azure or any hypervisor platform
- Ongoing administration after cutover — that returns to the regular service line
What you get: A completed migration checked against the original inventory, with open items named rather than assumed closed.
What we hand back: A migration record: what moved, validation results, and anything still open.
What makes a migration quote real
A closed inventory before a price exists
"Quoted separately" only works once the list of what’s moving stops changing mid-project.
A downtime window your client has actually agreed to
Named upfront, not assumed on your side.
A rollback decision made before cutover
Agreed in advance, not improvised during the cutover itself.
Where the project ends
Write down where migration finishes and routine administration resumes, so nobody assumes a continuity that was never agreed.
What this line doesn’t include
- Advising which cloud or virtualization platform to buy
- A guaranteed migration timeline set before the inventory is closed
- Application-level compatibility testing beyond what’s agreed in scope
Straight answers on migration
Does this replace routine Microsoft 365 or server administration?+
No. This is project work with a start and an end; once validation is complete, the environment returns to the routine administration described on the services page.
What if the inventory changes mid-project?+
That’s a scope conversation, not a silent adjustment. An inventory that grows after the initial price deserves a new quote, not a quiet expansion of the same one.