{"id":122,"slug":"google-workspace-no-cross-tenant-file-transfer","title":"Google Workspace: cannot transfer file ownership to external accounts; client separation requires IMAP+DNS migration","kind":"reference","scope":"business","status":"current","audiences":["kevin","claude-code","smb-owner","candid-team"],"topics":["agency-methodology","data-portability"],"reference_body":"**Claim:** **Google Workspace forbids transferring file ownership to external accounts** (cited as \"user and company data\" protection). When a client's email and Drive live in an agency's Google Workspace, separation requires:\n\n1. Create a new Workspace under a temporary domain\n2. Migrate mailboxes via IMAP with app passwords\n3. Transfer Drive file ownership *internally* before account deletion\n4. DNS cutover\n\nWithout the agency's cooperation at every step, the practical outcome is **data loss**.\n\n**Source:** <https://support.google.com/a/answer/1247799> (current Google Workspace admin documentation).\n\n**Confidence:** Verified (primary Google documentation).\n\n**For Candid client onboarding:** Workspace ownership is one of the most under-discussed ownership layers. If the client's email is on an agency Workspace, plan a multi-week separation BEFORE engagement ends. Item in [[ownership-checklist-at-agency-separation]].","rationale_body":null,"metadata":null,"links":{"outgoing":[],"incoming":[{"slug":"ownership-checklist-at-agency-separation","title":"Ownership Checklist: what an SMB must be able to walk away with at agency separation","kind":"reference","scope":"business","link_type":"depends-on"},{"slug":"research-brief-owning-your-stack","title":"Research brief: Owning your stack — why agency-managed platforms cost more than they save (piece 4 of 15)","kind":"reference","scope":"business","link_type":"relates-to"}]},"created_at":"2026-05-22T19:17:26.832Z","updated_at":"2026-05-22T19:17:26.832Z"}