How to Transfer or Migrate Google Workspace Account 2026 Easily

Everything begins at admin.google.com, signed in as a super admin on the target account. The home screen's Users, Billing, and Groups tiles give you a map of the organization you're migrating into. A regular admin role isn't enough here; authorizing a cross-account data transfer specifically needs super admin permissions on both sides of the move.

Google's Data import tool moves Gmail, Contacts, or Calendar, one data type at a time and one user pairing at a time; it does not move Drive files. Drive works under a different rule entirely: an admin can reassign file ownership between two accounts only inside the same organization.

Moving Drive content to a different domain isn't something the standard admin console offers, so it needs either Google Workspace Migrate (Google's own tool for larger migrations) or a third-party Drive-to-Drive tool. The app switcher in the top corner is worth knowing about here, since a migration means bouncing between the Admin console to configure each job and Gmail or Drive to spot-check where data landed.

In the left-hand navigation, go to Data, then Data import and export, then Data import. Pick the data type you're moving: Business Gmail for an org-to-org email move, Contacts, or Calendar, then click Import.

Each is a separate job. If you're coming from on-premises Microsoft Exchange rather than another Workspace account, the console points to Google Workspace Migration for Microsoft Exchange instead of this tool.

Enter the source super admin's email address and click Request authorization. Google emails that admin a link, valid for 24 hours, that they need to open, sign in through, and confirm with Authorize.

Until then, the job sits at Pending authorization. If nobody acts in time, the request shows as expired and you click Refresh request to send a new one; only the admin address you entered can approve it, so double-check that address before sending. If you're moving between two organizations you control yourself, have that source admin login ready to go the moment you send the request, since nothing else proceeds until this clears.

Once authorization clears, upload a CSV pairing each source address with its target address, then start the import. The console tracks progress live: discovered, successful, failed, skipped, and warning counts per item, so a partial failure is visible while the job runs rather than only at the end.

Repeat this whole process separately for Contacts or Calendar if you need those too; there's no combined job that carries all three at once. While mail is mid-migration, set up routing or forwarding on the old domain so messages to addresses that haven't moved yet still reach the right person. Hold off on changing MX records or shutting the old domain down until that routing is confirmed working.

For a small number of users moving Drive content into a different organization, the practical option is often for each user to share or copy their own files into the new account, since there's no admin bulk transfer across domains. For a full company migration, Google Workspace Migrate is built for this, but it's a separate download that runs on its own Windows server rather than living inside the admin console, and Google positions it for organizations around 1,000 users or more. Below that scale, a third-party Drive migration tool from the Workspace Marketplace is usually the faster route.

A job reporting complete isn't the same as one that preserved everything correctly. Spot-check message counts against the source mailbox, open a handful of Drive files that had specific sharing permissions to confirm those permissions carried over, and check that Calendar events with multiple attendees still show the full guest list. Sharing permissions and attendee lists are the details most likely to need a manual fix, so leave time for this check before retiring the old account.