De-Googling Your Life: A Realistic, Step-by-Step Migration Plan

Every so often someone announces, with the zeal of the newly converted, that they have “deleted Google” — and then quietly admits three weeks later that they still use Maps, still use the Play Store, and have a Gmail address forwarding to their new account because everything they ever signed up for points at it. I’ve watched this fail enough times — and done a version of it myself — to be deeply suspicious of the all-or-nothing approach. De-Googling is not a single heroic act; it’s a migration project, and migration projects succeed when you sequence them properly and let nothing break in production.

So here is the plan I actually recommend, in the order that hurts least. The goal isn’t ideological purity. It’s reducing how much of your life one advertising company silently indexes, while keeping your day functional throughout. If at any point a swap is more painful than the privacy gain is worth, you stop and keep the old thing. This is a dial, not a switch.

Start with the inventory, not the deletion

Before you move anything, find out how deep the hooks go. Deleting first and discovering dependencies later is how people lock themselves out of their own bank. Google’s own Takeout is the honest mirror here — request an export of everything and look at the size of the archive. It is usually sobering.

There are three lists to build, in this order of importance:

1
2
3
4
5
6
7

# Map your Google dependencies before touching anything:
# 1. accounts.google.com -> Security -> "Your connections to third-party apps & services"
#    (every OAuth grant — the apps that can read your data)
# 2. accounts.google.com -> Security -> sign-in -> sites using "Sign in with Google"
#    (every login chained to this account — the real trap)
# 3. takeout.google.com -> select all -> export
#    (the data itself, and a brutal sense of the scope)

The “Sign in with Google” list is the one that ruins naive plans. Every site you logged into with that button is now chained to the account you want to abandon — delete the account and you lose those logins. You can’t safely delete until you’ve re-pointed them, so write them down now and treat the list as your migration backlog.

Email is the spine — move it first, carefully

Email is the hard dependency. It’s the recovery address for nearly everything else, so it must move first and it must not have a gap. The single most valuable decision is to buy a domain, because a domain you own means your next migration is just a DNS change. Stop having an @gmail.com identity and you never have to do this dance again.

Pick a destination. The realistic options, roughly in ascending order of effort:

• A privacy-focused paid provider (Proton, Fastmail, Tuta) on your own domain. Lowest effort, sensible default for most people. I’ve laid out the trade-offs in detail in Proton vs Tuta vs self-hosted email, assessed practically — read that before committing, because the encryption models differ in ways that matter.
• Self-hosting your own mail server. Maximum control, real ongoing cost in time and reputation management. Only sane if you go in clear-eyed; running your own mail server with Stalwart is the honest version of what that involves.

Whichever you pick, don’t cut over instantly. Point your domain’s MX at the new provider, then set Gmail to forward a copy to the new mailbox and live in the new account for a month while Gmail quietly catches stragglers:

1
2
3
4
5

# DNS for your new domain (values come from your mail provider):
@      MX   10 mx.your-provider.example.
@      TXT  "v=spf1 include:_spf.your-provider.example -all"
default._domainkey  TXT  "v=DKIM1; k=rsa; p=<your-public-key>"
_dmarc TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]"

Get SPF, DKIM and DMARC right before you start sending, or your first outbound mail lands in spam and trains every recipient’s filter against you. During that month, work through your password manager and change the contact and recovery email on every account, starting with the load-bearing ones: bank, government, domain registrar, the password manager itself. Only when forwarding has gone quiet for weeks do you stop relying on Gmail.

Replace the services, one tolerable swap at a time

Now work through the rest in descending order of how much grief each move causes. My rough order, easiest first:

• Search — switch the default to DuckDuckGo or a self-hosted SearXNG. Zero friction, instant win; do it on day one. If you want results from a private metasearch backed by your own infrastructure, replacing Google search with Perplexica and a local model is a surprisingly capable upgrade.
• Browser — Firefox, or a de-Googled Chromium build. This matters more than search, because the browser is where tracking actually lives. Move your bookmarks and saved logins out before you uninstall anything.
• Passwords — if you’re still relying on Chrome’s password store, move to a real manager first; everything else in this list depends on you being able to log in cleanly. Self-hosting Vaultwarden gives you a Bitwarden-compatible vault you control, and it becomes the spine of every other migration here.
• Drive / Docs — Nextcloud if you’ll self-host, or a paid alternative. Export from Takeout, import, verify file-by-file on the important folders, then delete the originals.
• Photos — Immich has become genuinely good, and it’s the service people miss most. Test it ruthlessly before trusting it; self-hosting your photo library with Immich covers the backup discipline that keeps this from being a single point of failure.
• Maps — OpenStreetMap-based apps (Organic Maps, OsmAnd) for navigation. Honestly the hardest habit to break; the data is excellent, the muscle memory is the problem.
• Android — the deepest hook. A custom ROM like GrapheneOS or LineageOS, or simply minimising Play Services, is a project of its own. Leave it for last, or accept it’s the one thing you skip.

The discipline that makes this work: never have more than one thing broken at a time. Migrate Photos fully, confirm nothing’s lost, then start on Drive. One front at a time means you can always roll back the single thing you just touched.

The bit nobody warns you about: account inertia

The real enemy isn’t any single service — it’s the thousand small dependencies. The smart-bulb app that requires a Google login. The work calendar invite that assumes Gmail. The two-factor recovery codes you never saved and now can’t regenerate because the recovery email is the account you’re trying to delete.

Two safety nets, both cheap:

1. Keep the dead Gmail account alive but empty for a year before deleting it. Set forwarding, strip the data, but leave it logged-in-able. Check the forwarding logs occasionally to catch the dependency you forgot — there’s always one.
2. Export and store your account recovery codes somewhere durable before you change a single recovery email. The number of self-inflicted lockouts that trace back to a skipped backup is depressing. This is exactly the “have a way back” thinking from why every side project should have a backup plan, applied to your own identity.

Troubleshooting the migration

The predictable failures, and how to climb out:

• New domain’s mail goes to spam. SPF/DKIM/DMARC misconfigured, or your sending IP has no reputation. Verify the records with dig TXT yourdomain.example and a mail-tester service; if self-hosting, warm the IP slowly and check it isn’t on a blocklist.
• A site won’t let you change the login email because it only offered “Sign in with Google.” Some sites have no email/password path at all — you may need to create a fresh account and migrate data manually, or accept that one service keeps you tethered. This is why the inventory came first.
• Calendar invites still arrive at the dead address. Update your calendar’s primary address and re-share any calendars others subscribe to; the old address lingers in their copies until you re-invite.
• “I deleted Takeout data and now a file’s missing.” Restore from the Takeout archive you exported — which is exactly why you verify imports before deleting originals, and keep the archive until you’re certain.

The honest cost ledger

It helps to look at this as a budget rather than a crusade, because the numbers are what kill the all-or-nothing version. A rough annual picture for the “paid provider on your own domain” path:

• Domain: a handful of pounds a year, and the single best money you’ll spend, because it makes every future move a DNS change rather than another full migration.
• Mailbox: a paid privacy provider runs in the region of a few pounds a month for a personal plan. That’s the recurring floor.
• Storage: if you self-host Drive and Photos, you’re buying disk and, more honestly, paying in time — setup, updates, the occasional 9pm “why is this container restarting.” If you go paid instead, it’s another small monthly line.
• The real cost is attention. Every swap is a few evenings of moving data, verifying it, and re-pointing logins. Spread over months it’s bearable; attempted in one weekend it’s how people rage-quit.

If you self-host any of this, go in with eyes open about the ongoing burden — I’ve made the case at length in self-hosting is not free: accounting for your own time, and de-Googling is precisely where that bill comes due. The convenience you’re leaving was subsidised by surveillance; replacing it means paying the unsubsidised price in cash, time, or both. That trade can absolutely be worth it. It’s just not free, and anyone who tells you otherwise hasn’t done it.

A useful framing I keep coming back to: you’re not buying privacy, you’re buying ownership of the dependency. The reason Gmail is so hard to leave isn’t that the email is good — it’s that twenty years of accounts point at it. What you’re actually paying for, with the domain and the staged migration, is the right to never be that trapped again. Move once, properly, onto something you control, and the next provider switch is an afternoon instead of a saga. That durability is the real return, and it’s why the unglamorous step — buy a domain, move email first — matters far more than which shiny privacy app you pick for any single service.

Is it worth it, and who is this for?

If you want a clean, zero-cost, frictionless life, no — Google’s product is convenient precisely because it’s integrated, and you will pay for that convenience in money and effort to replace it piecemeal. Budget a real cost: a domain, a paid mailbox, perhaps a small server. If privacy isn’t something you actually feel strongly about, this is a lot of work for an abstraction, and that’s a perfectly defensible reason not to bother.

But if you’ve decided you’d rather not have one advertising company hold your email, your location history, your documents and your photos in a single profile they monetise, the staged plan above gets you there without a single day of broken email. Move email first, own a domain, swap one service at a time, keep a way back at every step — and accept that “de-Googled” is a direction, not a finish line. I’m years in and I still occasionally open Maps. That’s fine. It’s a project, not a purity test, and the point was always less surveillance, not zero.