How to Migrate Unmanaged Google Accounts to Workspace Without Data Loss?

PWA By islever Editorial Last updated

Short answer

C Use the Transfer Tool for Unmanaged Accounts to send requests to the former users to transfer their account to your domain as a managed account.

Question

In the years before your organization moved to Google Workspace, it was relatively common practice for users to create unmanaged Google Accounts with their corporate email address (for example, to monitor Analytics, manage AdSense, and collaborate in Docs with other partners who were on Google Workspace). How do we provision users who previously owned unmanaged Google Accounts without having to lose access to their data?
  1. Provision former user accounts with Cloud Identity licenses, generate a new Google password, and place them in an OU with all Google Workspace and other Google services disabled.
  2. Contact Google Enterprise Support to provide a list of all accounts on your domains that access Google services outside Workspace, and have them converted to managed accounts.
  3. Use the Transfer Tool for Unmanaged Accounts to send requests to the former users to transfer their account to your domain as a managed account. Correct Answer
  4. Provide a list of all active employees to the managers of your company's Analytics, AdSense, etc. accounts.

Key Takeaways

This question tests knowledge of the unmanaged account migration workflow, trapping candidates who might consider manual provisioning or direct support conversion instead of using the standardized transfer request process.

Migrating legacy unmanaged Google Accounts to a managed Workspace domain requires using the official Transfer Tool to preserve user data seamlessly. The certification community unanimously agrees that initiating transfer requests via this tool is the only supported method to retain access while converting accounts to managed status.

Common mistake: Option A is often chosen by those assuming administrative password resets and OU restrictions suffice, but it fails to address the fundamental need to migrate ownership and data from an unmanaged domain to a managed one without breaking existing integrations like Analytics or AdSense.

Expert Analysis

Why the Answer Is Correct

The Transfer Tool for Unmanaged Accounts is specifically designed to handle this exact scenario. It allows administrators to initiate a migration request that notifies the former user, guiding them through a secure process to hand over account ownership to the organization's managed domain. This method preserves all historical data, including Drive files, Gmail messages, and linked service permissions, ensuring zero disruption to business operations. Official Google documentation confirms that this automated workflow is the standard procedure for converting legacy unmanaged accounts.

Why the Other Options Are Wrong

Option A incorrectly suggests creating new Cloud Identity licenses and resetting passwords, which would orphan the original unmanaged account rather than migrate it. Option B misdirects candidates toward Enterprise Support, as Google does not manually convert unmanaged accounts en masse due to security and verification requirements. Option D proposes a manual handover list, which bypasses technical migration entirely and leaves data fragmented across separate domains. None of these alternatives guarantee data retention or proper domain management.

Community Comment Notes

Exam takers consistently validate Option C as the definitive answer across multiple study forums. Several contributors referenced the official Google Admin Help Center articles detailing the unmanaged account transfer process, emphasizing its reliability. The unanimous 100% voting distribution reflects strong alignment between the exam objectives and real-world Workspace administration practices. Candidates are advised to bookmark the provided support links for quick reference during exam preparation.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

Focus on mastering Google Workspace migration workflows, particularly the distinction between manual provisioning and automated transfer tools. When encountering scenarios involving legacy accounts or cross-domain data preservation, always prioritize solutions that explicitly mention preserving user data through official migration utilities.

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. indrajithgihan 👍 3 Answered C
    https://support.google.com/a/answer/11112794?hl=en https://support.google.com/a/answer/6178640
  2. mostafa97 👍 1
    C is the correct answer
  3. dija123 👍 1 Answered C
    C is correct

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How to Fix Non-Google File Access Issues in Google Drive?

S-grade

How to First Troubleshoot Google Meet Video Issues?

S-grade

How to Restrict Temporary Employees' Email Domains in Google Workspace?

S-grade

How to Securely Share Files with External Users Without Google Accounts?

S-grade

← Back to PWA Study Guide