Leaving without the migration stalling
Migrations rarely fail for technical reasons. They stall half-finished, people quietly go back to what works, and you end up paying for both.
The three things that actually break
Mail stops being delivered because the sending records were not moved properly. Calendar invites from outside stop matching. Somebody’s shared drive does not come across. All three are predictable, and all three are handled before the cutover rather than after.
Your staff do not run the migration
I move the data. They get a working account on a Monday and a page telling them what changed. Nobody is asked to export their own mailbox in their own time, which is how the last one stalled.
The old account stays alive until you say otherwise
We cut over with the previous provider still running behind us. If anything is wrong, you are back on it the same hour. You cancel it when you are satisfied, not before.
It replaces your provider rather than adding to it — the licence bill and the IT contract are the budget this comes out of.
How the move actually runs
1
First conversation
We figure out what you need. What services make sense, what you want to run, what matters most.
2
Proposal and hardware
I present the recommended configuration. If you are in, I prepare your dedicated hardware (included in the price).
3
Build and copy, with the old system still running
I configure everything and copy mail, files and photos across while your current provider keeps running and receiving. Nothing is switched yet, so nothing can break yet.
4
Cutover, with a way back
Delivery moves to your server after a final sync, with the sending records changed and verified in advance. Everyone gets a one-page note about what changed and signs in once on each device. The old account stays live behind it — if anything is wrong, you are back on it the same hour.
5
Cancel when you are satisfied, then ongoing support
You cancel the old provider when you are satisfied, not before. From there I handle updates, backups, security and troubleshooting, and your people just use the services. Guides for every service come with the handover.
Questions
What if something breaks?
Message me. Monitoring usually tells me before you notice, and what I owe you when it happens is written down rather than left to me.
What if you are ill or away?
Monitoring and backups keep running either way. What pauses is change, not the service — the response targets are written down, and what happens if I stop for good is too.
Do you move our data out of Google or Microsoft?
I move it. Your people get a working account on the other side, and import guides for anything they want to bring over themselves later.
Do you train our staff?
Guides for every service and a one-page note on cutover day, not classroom training. If something does not make sense, they ask me.
Can you manage our domain?
Yes — move it to my registrar, or give me access to yours. The account stays in your name either way.
What happens if we leave?
I ship you the SSDs. Your files, as they are, on drives you own, with the documentation to hand to whoever comes next.
Why trust you over Google?
Do not trust — verify. You get documentation for what runs, where your data sits and how it is configured. With Google you get none of that, and you are the product.