Moves without downtime
outcome
The team keeps working as normal, and the old environment waits untouched until you confirm the new one works.
what I do
- A list of everything we're moving and everything that depends on it.
- A written plan, including a way back if something goes wrong.
- The switchover in the evening or at the weekend.
- A checked backup of the data before every switchover.
- A list of old services you can switch off and stop paying for.
What I usually see
A move is the moment when it’s easiest to lose data, email or a few days of the whole team’s work. Changing email provider. Merging two companies into one Microsoft 365. Leaving VMware after the licensing changes. Moving a domain to another company.
Each of these looks simple until something comes up that nobody thought of. An old server that still sends out invoices. Or a domain setting that email depends on.
What I do
First I list what we’re moving and what depends on it. Which programs use the server, what handles email, who signs in with which account.
Then you get a written plan. The order of the steps, the dates, the risks and how to go back to the old setup if something goes wrong. I do the switchover in the evening or at the weekend. In the morning the team simply starts work in the new place.
This is what one of my projects looked like. I moved 50 mailboxes, 150 accounts and 5 virtual servers to a new environment, along with the domain settings. Staff didn’t notice any break.
Before the switchover I check the backup of the data. The old environment stays untouched until you confirm the new one works.
Who it’s for
For businesses across the EU that are planning a change and want to do it once, and do it properly. I do most moves remotely.
When it’s done, you get a description of the new environment and a list of old services you can switch off. So you don’t pay for the old ones longer than you need to. If it’s about email and Microsoft 365, a free audit of email and accounts is a good place to start.
technical details
- Microsoft 365
- email and file migrations, including tenant-to-tenant (acquisitions, company mergers)
- DNS
- moving domains and zones between providers, including to AWS Route 53
- VMware ESXi
- moving to Proxmox or Hyper-V
- Azure
- moving virtual machines between subscriptions
- Plan
- written cutover and rollback, maintenance windows after hours