Service 02
We inventory every workload, build the target environment first, rehearse the cutover against production-scale data, and shut the old infrastructure down on a written schedule.
Overview
Migrations fail in two predictable ways. Either the cutover takes far longer than anyone planned and the business loses a weekend it cannot afford, or the migration succeeds and the first cloud invoice is double what the board approved.
We plan for both. Every workload is assessed and costed before anything moves, the target environment exists and is tested before the first byte of data is transferred, and the cutover is rehearsed end to end so the real one is boring.
What we provide
If something you need is missing from this list, it is a conversation during the proposal rather than a change request halfway through the build.
An inventory of every workload, dependency, data store and licence, with a per-workload recommendation to rehost, re-platform, rebuild or retire, and the reasoning behind each one.
Accounts, network topology, identity, logging and guardrails built and tested before a single workload moves into them.
A replication and cutover strategy sized to the downtime your business can actually absorb, with the exact sequence of steps written out and timed.
A full dry run against production-scale data, with the rollback path executed and timed, so the decision to proceed on the day is based on evidence.
A projected monthly bill per workload agreed before migration, then reconciled against the real invoice sixty days after cutover so any drift is caught early.
Old infrastructure retired on a written schedule with verified backups, so you stop paying for two environments as quickly as it is safe to.
Typical engagement timeline
A typical migration for a small or mid-sized company runs ten to twenty weeks, driven mostly by how many workloads move and how much data has to follow them. Nothing moves until the target environment has been built and tested.
Weeks 1 to 3
Full inventory, dependency mapping and a costed target architecture. You get a migration plan with a per-wave schedule and a projected monthly bill before committing to the build.
Weeks 3 to 7
Accounts, networking, identity, backup and monitoring built as code, with the guardrails that stop the environment drifting once teams start using it.
Weeks 6 to 10
One low-risk workload moved end to end to prove the tooling, the runbook and the cost model against reality. The plan is corrected here, not later.
Weeks 9 to 18
Remaining workloads moved in scheduled waves grouped by dependency, each with its own rehearsal, cutover window and rollback point.
Weeks 16 to 20
Final cutover, thirty days of parallel monitoring, then a staged shutdown of the old estate with backups verified before anything is deleted.
Key benefits
These are the outcomes clients tell us mattered most six months after the engagement ended, rather than the ones that sound best in a proposal.
Because it has already been run once against real data volumes, the window you announce to customers is a measurement rather than an estimate.
Costs are modelled per workload before migration and checked against the real invoice afterwards, so nobody discovers the number at the end of the month.
Seasonal or campaign-driven load stops requiring hardware decisions made months ahead of the traffic.
A written decommissioning schedule means the old estate is genuinely switched off rather than quietly running for another year.
Questions we are asked
If your question is not here, ask it on the introductory call. We would rather answer it before a proposal than after one.
That is an input to the design rather than an outcome of it. Tell us the window your business can absorb and we build the data strategy to fit it. Most of our clients land between fifteen minutes and four hours for the final cutover, and we confirm the real figure during the rehearsal before you announce anything to customers.
Sometimes it is, and we say so during the assessment rather than after the migration. The costed target architecture in week three is the point where you decide whether to proceed. Where the numbers do not work, we have recommended staying put, moving only part of the estate, or choosing a cheaper provider than the obvious one.
Yes, and it is often the right answer. Hybrid arrangements are common where hardware still has useful life left or where data residency rules make a workload awkward to move. We design the network and identity so both sides work as one environment rather than two disconnected ones.
Fixed-scope engagements from EUR 24,000. 10 to 20 weeks.
Send us the shape of the problem and we will come back with a written scope, a timeline with dates, and a fixed price. The introductory call is free.