Off Google in about six weeks. Finished, not half-done.
Migrations rarely fail for technical reasons. They stall half-finished, people quietly go back to what works, and you end up paying for both. I do the move myself, and your old account keeps running until you cancel it.
The three things that actually break
Mail that stops arriving because the sending records were not moved, invites from outside that stop matching, a shared drive that does not come across. All three are predictable, and all three are handled before the switch.
Your staff do not run the migration
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 and does not add to it: the licence bill and the IT contract are the budget this comes out of.
How the move actually runs
Before you sign
A conversation, then a proposal
What you need, what you want to run, what matters most. Then the configuration I recommend; if you are in, I prepare a machine dedicated to you, included in the price.
Weeks 1–4
Your data, then the build
You hand me the data, or a sample of it, and I plan the import. Then I build everything and copy mail, files and photos while your current provider keeps running and receiving. Nothing is switched yet, so nothing can break yet.
Week 5
The switch, with a way back
Delivery moves to your server after a final sync, with the sending records changed and checked in advance. Everyone signs in once on each device.
Week 6
Cancel when you are satisfied
You cancel the old provider when nothing feels wrong. From then on I handle updates, backups and fixes, and your people just use the services, with a guide for each one.
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 train our staff?
Guides for every service and a one-page note on the day of the switch (an example, PDF), not classroom training. If something does not make sense, they ask me.
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. Nothing in it is read to sell you anything, and nobody else sits between you and your data.