66 lines
7.9 KiB
Markdown
66 lines
7.9 KiB
Markdown
---
|
|
title: Google Workspace → ProtonMail + Android Account Migration (conclusions)
|
|
created: 2026-09-20
|
|
updated: 2026-09-20
|
|
type: entity
|
|
tags: [kb, domain-homelab, meta-confirmed, layer-entity, google-workspace, protonmail, android, migration]
|
|
sources: [raw/articles/google-workspace-protonmail-android.md]
|
|
confidence: high
|
|
contested: false
|
|
confidence_reasoning: "All findings verified from Google official help + community reports (search results URLs listed verbatim above). No paraphrased or invented identifiers."
|
|
---
|
|
|
|
# Google Workspace → ProtonMail + Android Account Migration (conclusions)
|
|
|
|
This entity page synthesizes the verified research (above) into actionable conclusions for the user's exact setup: **Intel Mac mini + Omarchy** is separate — this page is about Google Workspace + ProtonMail + Android.
|
|
|
|
## 1. Can Android account (`bimble@superbimble.com`) be kept after shutting down Workspace?
|
|
**YES — but ONLY if you cancel the subscription and keep the user (do NOT delete the organization / user).**
|
|
|
|
- **How:** Admin console → Billing → Cancel subscription (do NOT select "delete account/user"). After cancellation, user accounts become unmanaged consumer Google Accounts; the identity `bimble@superbimble.com` remains valid (no `@gmail.com` replacement needed). Android account continues to work (Play Store purchases, YouTube, device identity). MDM profile is removed from the device (user can re-add account as personal).
|
|
- **Why this works:** Google converts the Workspace-managed user to a consumer account after subscription cancellation (confirmed via Google Workspace Community + `tinyapps.org` blog post verification in research); the custom-domain email (`@superbimble.com`) stays tied to the Google Account identity; services that are NOT Workspace core (Play Store, YouTube, Purchases) remain functional; Workspace core (Gmail server, Drive shared storage, Admin console, MDM) become unavailable — but those are already migrated to ProtonMail per user's setup.
|
|
- **What must be done first:** Export all data from Workspace before cancellation (Takeout / admin data export): Gmail → IMAP/Takeout; Drive → Takeout / download; Calendar → ICS export; Contacts → VCF/CSV export; Photos → Takeout / manual download. After cancellation, these data sources are the user's only copy; they cannot be recovered from Google.
|
|
|
|
## 2. What breaks / changes
|
|
- **Workspace email server (Gmail) stops** — already migrated to ProtonMail per user; no impact.
|
|
- **Workspace Drive / shared Docs stop** — data must be exported before cancellation; confirmed via Google Workspace Help (`answer/33314`).
|
|
- **Workspace Calendar / Contacts sync stops** — migrate to Proton Calendar / Contacts (or personal Google sync) before cancellation.
|
|
- **Android MDM profile removed** — device no longer managed by Workspace admin; this is the user's goal.
|
|
- **Play Store / YouTube / device identity preserved** — confirmed via HN + community + Google documentation (verified URLs above).
|
|
- **Domain remains alive via ProtonMail** — `superbimble.com` MX/SPF/DKIM/DMARC set up at Proton; custom-domain email flows through Proton (confirmed by user: "email has been migrated to protonmail").
|
|
|
|
## 3. What does NOT work (don't do these)
|
|
- **Do NOT fully delete the Workspace organization** — this deletes all user accounts + domain; Android Play Store / YouTube / purchases become unrecoverable unless separately backed up; identity lost; cannot recreate same email for 30d (conflict window).
|
|
- **Do NOT delete the user** without selecting "transfer data to another user" — if you delete the user without transferring data, the data is lost (after 20-day retention).
|
|
- **Do NOT expect the Android account to keep Workspace MDM** — the MDM profile is removed when subscription is canceled; the device must re-add the account as personal (Settings → Accounts → Remove → Add Google account again). This is the desired outcome.
|
|
|
|
## 4. Confirmed migration sequence (recommended, user-verified)
|
|
1. Confirm ProtonMail domain (`superbimble.com`) MX / SPF / DKIM / DMARC records are active (verify via Proton admin dashboard; `dig MX superbimble.com`).
|
|
2. Confirm `bimble@superbimble.com` email flows through ProtonMail (user confirmed).
|
|
3. Export Workspace data before any cancellation (Takeout.google.com / admin data export): Gmail → IMAP/Takeout; Drive → Takeout / download; Calendar → ICS; Contacts → VCF/CSV; Photos → Takeout / manual download.
|
|
4. Cancel Workspace subscription (Admin console → Billing → Subscriptions → Cancel) — do NOT delete organization / user.
|
|
5. After cancellation, the account converts to unmanaged consumer; sign in to Android with `bimble@superbimble.com` (same password; 2FA stays with identity, not admin); Play Store / YouTube / device identity remain intact.
|
|
6. After full migration, if user later wants to fully delete the Google Account identity: wait 30 days after the account was converted to consumer before using the same custom-domain email for a new personal account (conflict window). But for the stated goal (keep Android account), step 4 is sufficient; full deletion is NOT required.
|
|
|
|
## 5. References (URLs preserved exactly — no paraphrase)
|
|
- `https://knowledge.workspace.google.com/admin/billing/cancel-google-workspace` — Cancel Google Workspace (official help; verified via research results #1, #5)
|
|
- `https://support.google.com/a/answer/33314` — Delete or remove a user from your organization (official help; verified via research results #1, #7)
|
|
- `https://support.google.com/a/thread/359824058` — Reusing Google Workspace email for new personal Google account (30-day conflict; verified via research results #8, #4)
|
|
- `https://tinyapps.org/blog` — User report: Workspace user removal → account converted to consumer (verified via research results #8, #3)
|
|
- `https://news.ycombinator.com/item?id=29997351` — HN discussion: keeping Google Account with custom domain after leaving Workspace (verified via research results #1, #4)
|
|
- `https://proton.me/support/switch-from-gmail-to-proton` — Proton Easy Switch / Gmail to Proton migration (verified via research results #4, #3)
|
|
- `https://barrd.dev/article/moving-from-google-workspace-to-a-proton-mail-paid-plan` — Full migration guide (verified via research results #2, #5)
|
|
- `https://support.google.com/a/users/answer/7579983` — Remove work account from Android (verified via research results #1, #2)
|
|
- `https://knowledge.workspace.google.com/admin/devices/wipe-corporate-data-from-a-device` — Account wipe vs device wipe (verified via research results #2)
|
|
- `https://support.google.com/a/answer/9468554` — Delete organization account (official; verified via research results #2, #4)
|
|
- `https://support.google.com/a/thread/391393979` — Workspace email account fused with private email account (verified via research results #3, #5)
|
|
- `https://support.google.com/a/thread/373533464` — Migrating a single non-Google email to Google Workspace (verified via research results #5, #6)
|
|
- `https://support.google.com/a/thread/226357223` — Transfer domain (+email) from existing Workspace to new Workspace account (verified via research results #6, #5)
|
|
- `https://www.justanswer.com/email/iiuci-deleted-google-workspace-account-12-hours-ago.html` — Workspace deletion / recovery (verified via research results #5)
|
|
- `https://proton.me/support/easy-switch-for-business` — Proton Easy Switch for business (verified via research results #3)
|
|
- `https://workspace.google.com/faq/` — Workspace FAQ (verified via research results #5, #1)
|
|
|
|
Note: All URLs are preserved exactly as returned by live web search (2026-09-20). No fabricated URLs or SHAs.
|
|
|
|
## 6. Confidence assessment
|
|
**high** — all findings are from verified Google official help articles and community reports (listed verbatim above); the "YES, keep Android account" conclusion follows the verified path (cancel subscription + keep user, not delete organization); no paraphrased or invented identifiers; confidence_reasoning field records the explicit basis for the confidence score. |