Find and manage existing accounts

Find and manage users with existing Google Accounts using the Transfer tool for unmanaged users. The tool checks whether any users in your organization have personal Google Accounts that share your organization's email address. Learn more about conflicting accounts.

If you find users with conflicting accounts, ask them to transfer their personal Google Account to your organization's managed Google Account. You can track who has been sent a request, who has accepted, and who has declined.

What happens when an account is transferred

Personal Google Accounts that are transferred to G Suite managed user accounts: 

  • Can't be changed back to a personal account.
  • Are added to the root organizational unit. After the account is transferred, you can move the user to another organizational unit. Read more about organizational units.

Transferred accounts get:

Services not listed in these articles aren't guaranteed to work with a personal account that is transferred to a managed account. Transferred personal accounts lose data and content for some Google services, including but not limited to:  Adsense, Google Analytics, Google Finance, Google Maps, Google My Business, Google Nest, Google Pay/Wallet, Google Play apps, and YouTube.

Your users might want to review and download their personal account info before transferring their account.

You must be signed in as a super administrator for this task.

Before you begin

  • Make sure your domain is verified with a TXT or CNAME record. Learn more about verifying your domain
  • If you changed your MX records before you created your Google Account, set up a forwarding rule or catch-all address so your users get their transfer request. Learn more about Avoid bounced messages from new MX records
  • When a personal account is transferred to a managed account, all current G Suite policies apply to the managed account. In some cases, this could result in account data loss. For example, data loss might occur if the account is assigned an insufficient license or is subject to retention rules.

Find potential conflicts and send a transfer request

Find users with potential conflicting accounts
  1. From the Google Admin console: at the top right, click Open "".
  2. Under Tools, click Transfer tool for unmanaged users. 
    The Unmanaged users page displays a list of all users that are currently unmanaged.
Why can't I find a user that I know exists?
  • A synchronization hasn't updated the data yet. This usually happens if you recently verified your domain. It might take a few hours for all accounts to appear.
  • The user is on an alias domain. These accounts can't be transferred. Accounts can only be transferred if the domain in the email address is a primary or secondary domain.
  • The user has their organization's email address as an alternate email on their account. Accounts can only be transferred if the primary email address of the user is an organization email address. When you create this user, their organization's email address is removed as an alternate from their existing account.
  • The user has unsupported special characters in their email address. The user must update their username to remove the special characters before their account can be transferred.
Send requests for users to transfer their account to your organization

Users that haven't been sent a request to transfer their account have Not yet invited in the Request status column.

To see only Not yet invited users:

  1. Click Add a filterand thenRequest status.
  2. Select Not sent, then click Apply
    The list displays the selected list of users.

To send a transfer request to a single user:

  1. Point to the user's email address.
    Email transfer request displays to the right of the last column.
  2. Click Email transfer request.
    After the transfer request is sent, you receive a confirmation message. The user's status changes to Invited

    Note: This action must be performed manually. You can send requests for multiple users at once, but you can’t use an API to send a bulk request.

To send a transfer request to multiple users:

  1. Click the User email box at the top of the list of uninvited users.
    The screen displays the number of users selected and the Email transfer requests button.
  2. Click Email transfer requests.  
    After the bulk transfer request is sent, you receive a confirmation message. Each user’s status changes to Invited.

    Learn more about How users accept transfer requests
Manage requests to transfer an account

Users that are asked to transfer their account to your organization's managed Google account have Sent in the Request status column. On the left, select Sent and click Apply to see all users with pending requests.

There are two actions you can take once you’ve sent a transfer request:

  • Resend transfer request
  • Cancel transfer request
To resend a transfer request to a single user:
  1. Point to the user's email address. 
  2. Click Resend transfer request.
    After the transfer request is sent, you receive a confirmation message. The user's Requests sent count is increased by 1.

    Note: This action must be performed manually. You can resend requests for multiple users at once, but you can’t use an API to send a bulk request.

To resend a transfer request to multiple users:

  1. Click the User email box at the top of the list of invited users.
    The screen displays the number of users selected and the Resend transfer requests button.
  2. Click Resend transfer requests.  
    After the bulk transfer request is sent, you receive a confirmation message. Each user's Requests sent count is increased by 1.

To cancel a transfer request for a single user:

  1. Point to the user's email address. 
  2. Click Cancel transfer request.
    After the cancelation request is sent, you receive a confirmation message. The user's email is removed from the Sent list and their Request status changes to Not yet invited

    Note: This action must be performed manually. You can cancel  requests for multiple users at once, but you can’t use an API to perform a bulk cancellation.

To cancel a transfer request for multiple users:

  1. Click the User email box at the top of the list of invited users.
    The screen displays the number of users selected and the Cancel transfer requests button.
  2. Click Cancel transfer requests.  
    After the bulk cancelation request is sent, you receive a confirmation message. Each user’s email is removed from the Sent list and their Request status changes to Not yet invited.

See what users decide to do

How users accept transfer requests

Users get an email when you send them a transfer request. In the email, they can click Transfer my account. If they do, they’re prompted to sign in to their personal Google account, if they are not already signed in. 

The user must agree to certain terms to start the transfer. To read details about the agreement, go to What happens to the user’s data.

If they transfer, the user’s status changes to Accepted. To see only these users, on the left, select Accepted.

What happens if a user declines to transfer?

If the user clicks Decline request in the email, their status changes to Declined. After you create their managed Google account, they're prompted to rename their personal account the next time they sign in.

To see all users who declined a request, on the left, select Declined. You can send a new transfer request if the user declined by mistake.

What happens if a user ignores the request?

You can create an account in your organization's managed Google account with the same email address as the user. After you create their managed Google Account, they're prompted to rename their personal account the next time they sign in.

What happens to the user's data?

If the user accepts the transfer request, you can:

  • Manage the account.

    Note: The new Google account can't manage any Sites or secondary calendars created by the user before the transfer. 

  • Access and delete data in the account.
  • Restrict access to Google services.

When a user renames their personal account, the data in their personal account:

  • Stays in their personal account.
  • Is safe and accessible only to them. 
Was this helpful?
How can we improve it?