Transfer G Suite to Another Account; Step by Step Guide to Follow

This is a step-wise guide on the best possible way to transfer G Suite to another account. Using this guide, a G Suite administrator can easily move email, contacts, calendars, and documents from one user to a G Suite account on the same or different domain.

Note: To move a full Google Apps (G Suite) workspace to another account/domain, you need a Super Administrator account. Before proceeding with the data migration task, make sure that you have administrative rights.

Different Methods to Transfer G Suite to Another Account / Domain

Depending upon whether you want to secure G Suite data of a leaving employee or transfer accounts to a different domain, there are several methods.

If in case, only one single G Suite account data needs to be transferred to a different account then it can be accomplished with the help of a data migration service in the Admin Center. This method is not suitable (not recommended) for multiple account migration, due to its complexity.

G Suite administrators often face either G Suite data transfer failed issues or other issues and are unable to complete the task.

Therefore, it is recommended to only use data migration services for a few account migrations only.

Still, if you face difficulties with a manual solution, then you can opt for an automated and professional tool such as SysTools G Suite Migration Tool.

To download the tool click on the below button and install it on your system. The tool is available for both Windows and Linux systems.

Download Now Purchase Now

This automated tool is created by professionals to overcome every limitation/hassle an administrator faces during the data transfer task.

First, try the demo version of the tool that comes with 2 free user licenses for testing. G Suite Admin can test it with all the necessary scenarios before opting for a complete migration.

Why Choose Automated Tool to Transfer G Suite Data to Another Account

Many administrators frequently ask about the benefits of opting for automated tools over manual migration services. The following are the benefits provided by the tool during data transfer:

• Automated tool transfers email, contacts, documents, and calendars all at once. Whereas the manual solution just moves the email to another G Suite account.
• Error handling comes with an automated tool whereas Data Migration Service does not have one.
• To migrate newly arrived emails, this professional tool provides a “Delta Migration” feature. This will skip the previously transferred data and transfer only the new and updated data from the mailbox.
• Quickly transfer G Suite to another account or domain using the tool.
• After the migration is complete, you can click on the Download Report button to get the details of the migrated data.
• If in any case, any file fails or is skipped to be transferred, you can resume the migration using the Re-run migration options of the tool.
• Furthermore, the tool provides permission options for the migration of calendars and documents.

Step-by-Step Software Guide to Move Google Workspace to Another Account

Step 1. Download and Launch the tool on your system and click on the Activate button at the left-side menu. In the activation window, either choose Demo or Full version and register your G Suite domain.

Step 2. Now, from the source and destination platform section, choose the “G Suite” option.

Step 3. Now scroll down to the workload section and select the Email categories as Emails, Contacts, Calendars, and Documents. Also, set a date-range filter for selective data transfer to new G Suite account.

Step 4. In the source tab, click on “Project Settings” and create the Google Cloud Console Project. After creating the projects, enter the Source G Suite admin ID, p12 file path, and application ID (created during project creation).

Step 5. Similarly, create a project for the destination G Suite domain and provide the required details. After that, click on the “Validate” button for authentication.

Step 6. Now for mapping of source and destination G Suite accounts, select the option from the User tab. There are two options provided by the tool:

• Fetch User: This feature automatically fetches all the source G Suite user accounts and lists them on the screen while keeping the destination field empty for mapping.

• Import CSV File: It allows to import a CSV file containing a mapping list of source and destination G Suite account IDs. You can get the sample CSV file by using the Download Template option.

Step 7. Finally, click on the Start Migration button to start transfer G Suite to another account. During the transfer process, the admin can stop the process using the Stop Migration button.

Using the Google Workspace Migrate to Transfer G Suite to Another Account

If you have to migrate 1,000 users or more, then manually you can migrate data from one G Suite to another G Suite environment using Google Workspace Migrate.

Different Stages of Google Workspace Migrate

• Stage 1. Before You Begin the Migration
• Stage 2. Set Up A Connection
• Stage 3. Scan & Analyze
• Stage 4. Set Up the Target Connection
• Stage 5. Set Up Your Migration
• Stage 6. Run A Migration

Stage 1. Before you begin

There are several system requirements that need to be met in order to transfer G Suite to another account using Google Workspace Migrate

Hardware Requirements 

• Supported Runtime – Microsoft .NET Framework 4.5 or later (with the exception of the CouchDB server, which necessitates Microsoft .NET Framework 3.5).
• Recommended Operating System – Microsoft Windows Server 2016 or 2019.
• Compatible Browser – Chrome Browser.
• Power Plan: Configure all Windows computers (whether virtual or physical) to the high-performance power plan.

Platform Server

• You will need one Windows server with a minimum of 4 cores, 16 GB of RAM, and a 200 GB solid-state drive (SSD).

Database Servers

• Two Windows servers, each equipped with at least 16 cores and 64 GB of RAM.
• Utilize a dedicated performance (SSD) persistent disk for the database data. We recommend approximately:
  • MySQL – 1 TB per 100 million objects to be scanned and migrated.
  • CouchDB – 1 TB per 40 million objects to be scanned and migrated.

Refer to the “Configure disks to meet performance requirements” and “Install the databases” sections for further information.

Node Servers

• You should have at least one Windows server with a minimum of 4 cores, 32 GB of RAM, and a 200 GB SSD.
• Refer to the section on “Consider how many node servers you need” for additional guidance.

Network Requirements

• Ensure that both the platform and all node servers have network connectivity to all data sources.
• Establish connections between servers within the same network.
• Keep servers in close physical proximity to each other.
• To avoid unintended server restarts during migration, manage Windows updates separately from ongoing migrations.

Port Requirements

Within your Google Workspace Migrate cluster, it’s recommended to have:

• Outbound internet access for software updates.
• Intra-cluster Server Message Block (SMB) access via TCP port 445.
• Admin Remote Desktop Protocol (RDP) access to all servers using TCP port 3389.
• Please refer to the “Securely Connecting to VM instances” section for details.

Make sure that the following ports are accessible:

• TCP port 5131 – Bidirectional communication
• TCP port 3306 (default) – Access to the MySQL server
• TCP port 5984 (default) – Access to the CouchDB server
• TCP port 443 – Connectivity to the target Google Workspace APIs

To reach the source APIs, open the following ports:

• Microsoft Exchange – Utilize Exchange Web Services on TCP port 443.
• Microsoft SharePoint or OneDrive – Use SharePoint Client-side Object Model (CSOM) API on TCP port 443.
• File shares – Utilize TCP port 445 (additional network access might be required for older environments).
• Box – Use Box API on TCP port 443.
• Google Workspace – Utilize Google APIs on TCP port 443.

Google Workspace Requirements

• A super administrator account in your target Google Workspace domain.
• Access to Google Cloud.
• A user account in your target Google Workspace domain for each individual whose data needs to be migrated.
• User licenses for your users to access Google products or services.

Refer to “Options for adding users” and “How licensing works” for detailed information.

In the Google Admin console for the target domain, enable Google Workspace services (e.g., Gmail, Google Calendar, and Google Drive) for users and the super administrator. If migrating from Google Workspace, activate services in the source domain as well. For instructions, consult “Turn a service on or off for Google Workspace users.”

Google Drive Requirements

• Enable the Drive and Docs service in the Admin console on the target Google domain for users, including the admin user. For guidance, see “Turn Drive on or off for users.”
• Confirm that your admin account possesses Drive and Docs privileges. The super admin role inherently includes these privileges. Details can be found in “Administrator privilege definitions (Drive & Docs).”
• Ensure that your target users, including the admin user, can access Drive files using the Google Drive API. If migrating from Google Workspace, the source users, including the admin user, must also have access. Instructions can be found in “Allow third-party apps for Drive files.”
• Familiarize yourself with Shared Drive Limits. For additional information, consult “Best Practices for Shared Drives.”

Install & Set Up Google Workspace Migrate

Verification

Establish authentication by:

• Creating a service account.
• Creating the OAuth web client ID.

Acquisition and Installation

Acquire the necessary installers and carry out the following installations:

• Install the required databases.
• Set up the platform and perform the installation.
• Install the node servers.
• Optionally, execute setup procedures for the node servers.

Migration Product Configuration

Configure the migration product as follows:

• Set up the encryption key.
• Adjust database settings.
• Configure the callback address.
• Integrate the node servers.
• Establish admin roles.
• Create a project.

For Complete Steps Refer to This Page. 

Google Workspace requirements

To perform the migration, make sure the following conditions are met:

Super Administrator Privileges 

• Ensure that you are signed in as a super administrator in both the source and target accounts.

Source Environment

• You must have a Google Workspace account in the source environment. This account can be on any edition.
• Ensure that the source Google Workspace account is active. Suspended accounts cannot be migrated.

Target Environment

• You must also have a Google Workspace account in the target environment.
• The Google Workspace account in the target environment can use any supported edition. Refer to the “System requirements” for specific details on supported editions.
• Ensure that the target Google Workspace account is active. Suspended accounts cannot be used for migration.

By meeting these requirements, you can successfully carry out the migration process between the source and target Google Workspace accounts.

Stage 2. Set Up A Connection

• Add a source connection
• Create a sharding users list (Optional)
• Create a scoped view
• Verify the connection

For Complete Steps Refer to This Page.

Stage 3. Scan & Analyze

• Create & Run A Scan
• Analyze Your Scan

Create & Run A Scan

Within the Google Workspace Migrate platform, follow these steps to initiate a scan:

1. Click on “New” and then select “Scan.”
2. Provide a name for the scan.
3. Choose your source connection.
4. Under “Scan scope,” opt for a Full scan.
5. (Optional) Click on “More options” to access advanced scan settings. Proceed to step 2 below.
6. (Optional) To specify the reports you want the scan to generate, mark or unmark the checkboxes next to the desired reports under “Report types.” By default, all reports are generated. If you require additional information about each report or specific details, refer to the “Understand Scan Reports” section.
7. Click Create.

Now In Order to Run a Scan

• In the Google Workspace Migrate platform, click on the Menu button and then click on Scans.
• On the desired scan that you want to run, click on Run.

Analyze Your Scan

For Complete Steps Refer to This Page. 

Stage 4. Set Up the Target Connection

In order to create a Google Workspace target connection, follow the below steps:

• Create the service account (Optional)

• Authorize the service account
• Set up the target connection

For Complete Steps Refer to This Page.

Stage 5. Set Up Your Migration

• Schedule your migration phases
• How to map data
• Build & manage a mapping
• Create & manage identity mapping
• (Optional) Set up a calendar resource migration
• Set up or select a settings template

For Complete Steps Refer to This Page.

Stage 6. Run A migration

• Build & run a bridge

To create a bridge in the Google Workspace Migrate platform, follow these steps:

1. Click on “New” and then select “Bridge.”
2. Provide a name for the bridge.
3. Complete the following information:

• •    Source connection
  •    Target connection (select the service account you are using to connect to Google Workspace)
  •    Settings template (choose between default or a customized template)
  •    Mapping
  •    Identity mapping

4. (Optional) To add a sharding users list, click “More options,” and then next to the option, click the down arrow, and select the mapping or list you want to use.
5. Finally, click “Create.”

Run a bridge

To run a bridge in the Google Workspace Migrate platform, follow these steps:

1. Click on “Bridges.” If you don’t see “Bridges” directly, you may need to click on “Menu” first to access it.
2. (Optional) To make changes to the bridge settings, click on “Settings.”
3. Click on “Run,” and then select “Run.”

These steps will initiate the execution of the selected bridge in the Google Workspace Migrate platform.

• Observe migration progress
• Get ready to go live

For Complete Steps Refer to This Page. 

• Clean up steps

For Complete Steps Refer to This Page.

As it is now evident from the above manual method, using the manual method is not practical for all users. As it requires technical knowledge and execution.  Furthermore, it becomes time-consuming and error-prone at the same time. However, it a user wants to transfer G Suite data to another account using the manual method then he/she can use the above points to execute the same.

Conclusion

The process of migrating email from G Suite account to another account can be quite difficult when using the data migration service provided by Google. There are many limitations to it too, this is why we have explained the step-wise working of an automated tool to easily transfer G Suite data to a new account or domain. Several G Suite administrators also suggest users to use the above software over the manual solution to avoid any data loss.

Frequently Asked Questions

Q- I tried to do the migration but facing data migration is stuck at 99 , how can I complete the migration?

To prevent such errors or any complications during migration, we recommend you use an automated G Suite to another account migration tool.

Q- How do I migrate G Suite to another account for multiple users at once?

Follow the below 5 simple steps to transfer G Suite to another account:

• Step 1. Download & Install the Tool on a PC.
• Step 2. Select G Suite as Source & Destination.
• Step 3. Select the Category & Set Date Filter.
• Step 4. Fetch Users & Hit Start Migration.
• Step 5. Save the Generated Report to the Desktop.

Q- Can I move only 2 years of emails from one G Suite account to another account/domain?

Yes, the tool provides all of your date filter options to move selected emails from the mailbox. For this, you can set the date range in the “From” and “To” fields and proceed with the migration.