You read your business email inside Gmail? That stops in January 2027

Is this you? The two-minute check

You have a business address — info@, accounts@, or your own name @yourbusiness.co.za — sitting inside a hosting package. You've never actually logged into that mailbox directly. Instead, for years, it has just shown up as a second tab inside a free @gmail.com account, because someone once ticked "Check mail from other accounts," and you reply from Gmail with the business address showing at the top. A notice about "Gmailify and POP" has landed in that Gmail account, or is about to this quarter, and it reads like it's addressed to somebody else.

It isn't. If that setup is yours, this is you.

Two Google features are being switched off: Gmailify, which applies Gmail's own spam filtering, categorisation and search to a third-party account, and "Check mail from other accounts," the POP-based fetching that pulls that hosting mailbox into your Gmail tab in the first place.

One line lets half of you stop reading here: if you already pay for Google Workspace on your own domain, none of this touches you. This is specifically about a free personal Gmail account fetching mail from somewhere else.

What Google is switching off, and when

The dates are exact, not a vague "coming soon." After the first quarter of 2026, Google stopped letting new users turn on POP fetching or Gmailify — if you already have it running, you kept it. This quarter, Q3 2026, is when the in-product notice goes out to everyone still using it: that's the notification landing in your inbox right now, which is the reason to read this before December rather than after. Q3 through Q4 2026 is a transition window — the old setup keeps working, but Google says it "may restrict new configurations" during this period. Then, in January 2027, Google removes "Send as" for third-party accounts, Gmailify, and POP fetching in one pass.

From your side, that removal looks small at first: the Gmail tab that used to show your business mail simply stops pulling in anything new. No crash, no error message — the hosting mailbox keeps receiving mail exactly as before, it just no longer arrives inside Gmail.

The reassurance first, because it matters: nothing you've already read is going anywhere. Google states plainly that "all messages synced before the deprecation stay in Gmail," and separately, that "any messages you've already imported from a third-party account into Gmail will remain in your mailbox." This isn't a case of your archive disappearing on some date in January — it's forward-looking. New mail stops showing up; old mail stays put.

That gap between "notice lands" and "removal happens" is the runway. Use it to get the new setup running and tested before the December quiet period, not in the first week of January when the mail has already stopped arriving where you're used to checking it.

The part the notice does not spell out: replying

Most people's first instinct, reading Google's notice, is to reach for the option it lists first: set up forwarding from the hosting mailbox to Gmail. That solves receiving — the mail keeps landing in your tab. It does not solve the other half of the job.

"Send as" for third-party, non-Google addresses is going in the same removal, in January 2027. Once it's gone, you can no longer send mail from your business address inside Gmail on the web or in the Gmail mobile app. Forward the mailbox and keep replying from Gmail, and every reply now leaves as your personal @gmail.com — not accounts@yourbusiness.co.za.

Say the actual consequence plainly: a customer emails accounts@yourbusiness.co.za about an invoice, and the reply lands in their inbox from a gmail.com address they don't recognise. For a business, that's not a formatting inconvenience — it's the moment your correspondence stops looking like it came from you.

There's an obvious workaround a lot of people will be tempted by in December: a browser extension or third-party tool that promises to bring "send as" back. Google's own notice tells you not to. It warns that these tools "often require access to your email credentials or OAuth tokens" — handing a stranger's extension the keys to your business mailbox to save yourself a proper migration is a worse trade than it looks.

Mail that carries your business name should leave from your own domain — and be set up so receiving servers can confirm it actually did. That's a separate piece of DNS configuration this post doesn't cover; our post on stopping email spoofing does.

Your four routes, with the catch on each

Google lists three official options and answers two more in its FAQ. Here are the four that matter for a hosting-package mailbox, plus the catch on each.

• A desktop mail client — Outlook, Thunderbird, Apple Mail — connected straight to the hosting mailbox over IMAP/SMTP. Replies leave from your real address, no workaround needed. Catch: it's configured per machine, and you're now living inside your hosting package's own mailbox, with whatever spam filtering and storage came with it — which is exactly what Gmailify was quietly covering for. (Google's other official option here is your provider's own webmail interface — same idea, same catch, just in a browser tab instead of an app.) We're not naming specific host quotas or settings here; check your own provider's control panel.
• Add the mailbox in the Gmail app on your phone. This connects over ordinary IMAP and is unaffected by any of this — Google says the mobile app keeps supporting third-party accounts as it does today. Catch: it's phone-only. The Gmail tab on your computer still won't show it, so anyone who writes long replies or attaches invoices from a desktop is stuck.
• Forward the mailbox to Gmail. One of Google's FAQ answers, not a headline option. Keeps mail arriving in the tab you already use. Catch: as above, every reply now goes out as @gmail.com. Fine for a mailbox you only monitor; wrong for one you answer customers from.
• A paid mailbox on your own domain — Google Workspace or Microsoft 365. Google's own first suggestion for a business is a desktop client (above); its FAQ names Workspace on a custom domain as the other route. We'd go further and call this the one that actually removes the problem: mail, calendar and files under your business name, one login, and it works identically on web, phone and desktop because the address is native, not borrowed. Catch: a monthly fee per user, and someone has to actually move the old mail across and set up every device — it isn't automatic. We're not quoting a rand figure here; check current pricing from either provider directly.

If the address is the one printed on your invoices and quotes, that's route four. If it's an address you only glance at occasionally, routes one or two are enough.

Do this before December

Five things, this week:

1. List every business address currently sitting inside a free Gmail account — yours and any staff member's.
2. Pick a route per address, using the four above. Not every address needs the same answer.
3. If you're moving a mailbox to Workspace or Microsoft 365, get the old mail out of Gmail and into the new home before you switch over. The imported copies stay in Gmail either way, but a business shouldn't keep its only working archive sitting in someone's personal account.
4. Test it from a phone, on mobile data: email the business address, reply, then check what address that reply actually arrives from. That one check is the whole post.
5. Tell staff once, in writing: which app they now open, and which address their replies go out from.

One more line worth adding if you land on Microsoft 365: its default retention is not a backup the way you might assume — that's a separate conversation, covered on our cloud backup page.

Want the business mailbox moved off the free-Gmail workaround properly before January — the right route chosen, the old mail carried across, every phone and laptop set up once, and staff told what changed? Get in touch.