Migrating a parish church from Google Workspace to Microsoft 365

The challenge

A parish church running its email on Google Workspace wanted to move to Microsoft 365 — to sit alongside the Office tools they were increasingly using, and to bring their email under one familiar roof. It sounds simple, but an email migration is one of the jobs where the details matter: get the domain or DNS steps wrong and mail bounces, or years of messages go missing.

With ten mailboxes to move — and a congregation and staff who rely on them — they needed it done properly, not improvised.

What we did

Our team handled the migration end to end:

• Set up Microsoft 365 — created the new tenant and configured each of the ten users ready to receive their mail.
• Migrated the mailboxes — moved all ten mailboxes across from Google Workspace to Microsoft 365, bringing existing email with them rather than starting from empty.
• Verified the domain — added and verified the church’s domain in Microsoft 365 so mail would flow under their own name.
• Reconfigured DNS — updated the DNS records (including the mail routing) to point cleanly at Microsoft 365, timed so the cutover happened without a scramble.

Because the sequencing was planned rather than rushed, the handover from one platform to the other was smooth — staff carried on with their existing addresses, now on Microsoft 365.

The result

The church came off Google Workspace and onto Microsoft 365 with all ten mailboxes intact, users ready to work, and their domain and mail routing correctly set up. A change that can easily go wrong went quietly right — which, with email, is exactly the outcome you want.

Honest about who did the work

This work was delivered by our team. We’ve anonymised the client out of respect for their privacy — but the migration and the outcome are real. If you’re thinking about moving to (or between) Microsoft 365 and want it done without losing mail or nerve, it’s the kind of email setup and migration work we do regularly.