Gmail Migration for Business
Every message can arrive intact and the migration still be remembered as a bad one. What decides that is not the mail — it is the list of things that never migrate at all.
Filters, signatures, delegation, aliases, out-of-office. None of them come across, all of them are noticed within an hour of people sitting down, and every one is straightforward if it was dealt with the week before rather than the morning after.
What Google's migration service carries across
Four data types, selectable individually, from four families of source system. This part is documented, predictable and rarely the thing that goes wrong.
Data types
Supported sources
From Google's own data migration documentation, checked September 2026. We do not name a specific tool version on this page — which route fits depends on your source and scale, and we confirm the current position at the time of your project rather than repeating something written months earlier.
What does not move
Six things, none of them technically difficult, all of them noticed within the first hour. Handled in the week before cutover they are invisible. Handled on the morning after, they are what the migration is remembered for.
Filters and rules
Years of accumulated server-side rules that quietly sorted somebody's inbox do not come across, and their absence is felt immediately. The useful approach is not to recreate them all — most were built for a problem that no longer exists — but to ask each person which three actually matter and rebuild those.
Signatures
Trivial individually, and a genuine irritation across forty people on the first morning. Prepare a standard signature in advance, send it out before cutover rather than after, and the issue disappears before anybody raises it.
Delegation and shared mailbox arrangements
If two people currently open the same mailbox, or an assistant manages a director's mail, none of that structure transfers. It has to be redesigned as groups and delegated access — which is usually an improvement, but it is design work, not a setting to copy.
Aliases and forwarding
Every address that currently reaches somebody needs to be found and recreated deliberately. The ones nobody remembers are the ones that matter — the address on an invoice template from 2019 that a bank still writes to.
Out-of-office and vacation settings
Small, and worth a moment's thought if anybody is on leave across the cutover. An auto-reply that stops working while somebody is away produces silence exactly where a customer expected an answer.
Distribution lists as they were built
Lists generally have to be rebuilt as Google Groups, which behave differently and better. Take the opportunity to check who is still on them — most distribution lists contain at least one person who left.
Redesigning shared mailboxes and delegation properly is a structural exercise rather than a copy — it is covered as part of implementation, alongside the group structure it depends on.
Gmail is not Outlook with a different logo
Four differences account for nearly every complaint in the first fortnight. All four are easier to explain in advance than to defend afterwards, and one of them is the most useful sentence you can say to an office on day one.
Folders become labels, and a message can have several
The nearest thing to a folder in Gmail is a label, with one important difference: a message can carry more than one. People who have spent fifteen years filing into a single correct folder find this disorienting for about a week and then stop refiling things entirely.
Search replaces filing
The honest advice to give an office is to stop organising mail. Search across a decade of correspondence is faster than any filing system anybody maintained, and the hour spent teaching people three search operators returns more than the whole migration.
Archive is not delete
The single most useful thing to explain on day one. Archiving takes something out of the inbox and keeps it findable forever; deleting removes it. Most people coming from Outlook assume the button that clears their inbox is destroying things, and either hoard or destroy accordingly.
Conversations group by thread
Replies collapse into one conversation rather than sitting as twenty separate messages. Almost everyone prefers it once used to it, and a small number of people genuinely do not — it can be switched off per person, which is worth knowing before somebody concludes the new system has lost their mail.
The day the MX record changes
This is the only genuinely irreversible moment, and the failure mode is almost never the migration tool. It is switching the old system off before anybody has properly checked the new one.
Lower the DNS time-to-live first
Days before the move, not on the day. A long TTL means the internet keeps sending mail to the old server for hours after you change the record, and there is nothing you can do about it at that point except wait.
Expect a window where mail lands in both places
This is normal rather than a fault. Different mail servers around the world pick up the change at different times, so for a period some messages arrive at the old system. Plan for somebody to watch the old mailbox for a few days rather than assuming the switch is instantaneous.
The old system stays, read-only, until it is verified
Not until the transfer finishes — until somebody has actually checked. Those are different tests and only one of them protects you. Keeping the old system available for a few weeks costs very little and removes the entire category of irreversible mistakes.
A delta sync after cutover catches the tail
Mail that arrived at the old system during the changeover still needs to reach the new one. A second pass after the MX change is the difference between a clean migration and somebody finding a missing week in March.
The MX change is also the right moment to get SPF, DKIM and DMARC correct rather than leaving them for later — the reasons are on the email security page.
Gmail migration — common questions
What does Google's migration service actually move?
Email, calendar events, contacts and tasks, selectable individually. Google's supported sources include Microsoft Exchange Online, IMAP-based webmail providers — it names Yahoo, iCloud, GoDaddy, Zoho and Titan among them, which covers most cPanel and website-bundled mail — plus other Google Workspace accounts and personal Gmail accounts. Additional Outlook calendars come across as Other calendars in Google Calendar rather than merging into the main one. Checked against Google's own documentation in September 2026.
What does not come across?
The list that actually determines how day one feels: filters and server-side rules, signatures, delegation and shared mailbox arrangements, aliases and forwarding, out-of-office settings, and distribution lists as they were built. Every message can arrive intact and the migration will still be remembered as a bad one if forty people spend the first morning without their signature and without the rules that sorted their inbox. These are preparation items, not surprises, and handling them in the week before cutover is what makes the difference.
We are moving from Zoho Mail. Is that supported?
Yes — Google lists Zoho among the IMAP-based providers its migration service supports, so the mail itself moves by a documented route. Worth thinking about separately is whether you are moving everything or only the mail: if your CRM, books or projects are on Zoho, those can stay exactly where they are and connect to Google Workspace. We are a partner on both sides, so that is a genuine conversation rather than a sales pitch in one direction.
Will we lose any email during the changeover?
Not if the cutover is handled properly, and the technique is unglamorous. Lower the DNS time-to-live several days in advance so the change propagates quickly. Expect a window where some mail still reaches the old system, because servers around the world pick up the change at different times. Keep the old system running and read-only rather than switching it off, and run a second pass afterwards to collect anything that arrived during the transition. The failure mode is almost never the migration tool — it is switching the old system off too early.
Why do we get duplicate contacts?
Because an import was run more than once. Google states plainly that a new import duplicates any contacts already imported, and that contact labels are not duplicated. It is an easy mistake to make when a first attempt appears to have failed or somebody decides to be thorough. The remedy is to treat contact imports as a single deliberate action with somebody responsible for it, rather than something anybody can re-run to be safe.
How long does it take?
The transfer usually runs in the background over days rather than hours, and it does not stop anybody working — people carry on in the old system while it copies. The elapsed time depends on mailbox sizes and how quickly the source system will hand data over, which for older IMAP servers can be the binding constraint. The part worth planning carefully is not the copying but the cutover day itself and the week either side of it.
Should we move everything, or start fresh?
Move it. Email is the business's memory, and the confidence that a decade of correspondence is searchable is most of what people value once they have it. The argument for starting fresh usually comes from wanting to leave behind a mess, and the mess is better handled by moving everything and then not filing it — Gmail's search makes an untidy archive perfectly usable in a way that a folder hierarchy never did.
Related pages
Google Workspace Migration
The hub — process, risks, timeline and cutover across all sources.
Microsoft 365 Migration
When the whole tenant is moving, not only the mailboxes.
Business Email on Your Domain
What you are moving to, and why the address matters.
Google Workspace Email Security
SPF, DKIM and DMARC — set correctly as part of the cutover.
Plan your mail migration
Tell us what you run today, how many mailboxes there are and roughly how large they have grown. The questions we will ask back are about aliases, shared mailboxes and who is on leave — because those decide how the first morning goes.
Every alias and forwarding address found before cutover, not after
Shared mailboxes redesigned as groups with delegated access
Signatures prepared and issued in advance
The old system kept read-only until the new one is verified
Migrations run remotely for businesses across India — Kerala and its fourteen districts has the local picture. Or call +91 99467 89916 and email admin@techgeum.com.