Troubleshoot Google Workspace Migrate

1. To find the logs:
   • On a platform installation—Go to C:\Program Files\Google Workspace Migrate\Google Workspace Migrate Platform\AppBridgeServiceHost.log.
   • On a node installation—Go to C:\Program Files\Google Workspace Migrate\Google Workspace Migrate Platform Node\AppBridgeServiceHost.log.

     If you're running an earlier version of Google Workspace Migrate, you might need to use G Suite in the path instead of Google Workspace.

2. Open the log and scroll to the end.
3. If there are relevant issues, troubleshoot the issues.

   You can safely ignore the "Access denied: Symmetric encryption is required for this service request but not configured" message.

4. If you can't fix the issue, go to Contact support for Google Workspace Migrate issues.

1. Sign in to the Google Workspace Migrate platform and, in the top-right corner, click Servers.
2. Verify your nodes appear in the list.
3. Check that the status of the nodes is Ready (green).

If you get an error when trying to associate a node with the Google Workspace Migrate platform, check if the node is running:

1. In a browser on the machine that is running the platform, enter the node's IP address and port (for example, http://192.0.2.1:5131).
2. If the platform can reach the node and the node service is running, you'll get a "Node is running" message.
3. If you receive an error, try the following options:
   • If it's a network error, resolve it and try again.
   • Restart the node service.
   • Reinstall the node application. For details, follow the steps in Install the node servers.

If you get this error: 

1. Go to the service host log for the node server.

   For details, go to Check the service host logs.

2. Check for the following error: The provided platform host address https://platformserver:443/Hub was unreachable.
3. If you see the error, try the following options:
   • Check the network connection to the platform server. If there's a network issue, resolve the issue and restart the node service.
   • If the platform is configured with a TLS certificate, in a browser on the computer that is running the platform, enter the platform's IP address and port (for example, https://192.0.2.1:5131). Also, check that the TLS certificate is valid and that it hasn't expired.

If you get an invalid_grant message in the host log, check whether:

• You enabled all API scopes for your target account. For details, go to Use the Google Cloud Console to turn on APIs.
• The service account is authorized for the required scopes in the Google Admin console. Use your OAuth 2.0 client ID for authorization and not your service account's client ID. For details, go to Create the OAuth web client ID.

If your migration is running slowly or not at all, the error might be related to Google Workspace's API quota levels. For details, go to Work with quotas.

As you run a scan or bridge, you can monitor the status of the partitions.

1. In the Google Workspace Migrate platform, click Scans or Bridges.
2. On the scan or bridge you want to check, click Logs Partition log.
3. Under State, check the status of the partitions:
   • Ready—Ready to begin.
   • Starting—Preparing to migrate or scan.
   • Crawling—Reading data from the source system.
   • Processing—Preparing to write data to the target system.
   • Committing—Writing data to the target system.
   • Cancelled—Failed. Proceed to Troubleshoot canceled partitions.
   • Completed—Finished working.
   • Skipped (displays when retrying failures)—Skipped because no failures. 

If you find a partition with Canceled in the partition log, troubleshoot using these options below.

Option 1: Check error codes

To find the error codes, point to a row in the partition log and click More Partition log. Use the error code associated with the failure to troubleshoot the issue. For details, go to Interpret Google Workspace Migrate error messages.

Option 2: Check the nodes

Use the partition log to check whether all partitions on a node are canceled. All nodes canceled usually indicates connection issues, for example, the source service is temporarily unavailable. Complete the steps in Error associating a node. Then, retry the scan or run a delta migration.

Option 3: Check the partition execution log

If the issue affects multiple nodes, you can examine the partition execution log. To view the execution log associated with a partition:

1. Open the partition log.
2. Point to a row in the log and click More Execution log.
3. Click StateFailed.
4. Review the failures to isolate and troubleshoot the cause of the problem.
5. Retry the scan or migration.

If there's an increase in similar failures in the migration summary, your migration configuration is probably incorrect.

Check the following configuration items to make sure they're correctly set up:

1. Ensure the APIs, particularly the Admin SDK, are correctly enabled in the Google Admin console. For details, go to Use the Google Cloud Console to turn on APIs.
2. Make sure the user account exists on the source account and in Google Workspace. Verify the account is not frozen, suspended, or renamed.
3. Verify that all users have the necessary Google Workspace services (for example, Gmail or Google Drive) turned on. For details, go to Google Workspace requirements.

If you get this error in the host logs, you might need to allow third-party apps for Drive files.

To fix the issue, follow the steps in Allow third-party apps to work on files stored in Drive.

You can often fix many errors by running a delta migration. A delta migration identifies persistent errors and cleans up temporary issues, such as rate limiting and quota levels, networking issues, and 401 errors. You can run a delta migration multiple times to troubleshoot. For details, go to Get ready to go live.

1. In the Google Workspace Migrate platform, click Scans or Bridges.
2. On the scan or bridge that you want to check, click Logs Transaction log.
3. Point to the transaction and click More Transaction details.
4. Use the table to locate common transaction errors and steps to troubleshoot.

A transaction in your transaction log might be skipped for the following reasons:

• You're running a delta migration, and the object hasn't changed since the previous migration.
• The object was excluded by a filter condition in the settings template.
• You're migrating email content to a group, and a large message attachment is skipped.
• You're using a shared drive settings template but migrating content to My Drive.

Depending on the migration source, other reasons that an item could be skipped are:

• SharePoint—A folder is skipped because it isn't part of a document library.
• Exchange—Draft emails are skipped when they're migrated to Google Groups.
• Box—A file revision is skipped because the revision is empty.
• File shares—An item is skipped because the nodes don't have sufficient permission to access the item. 
• Gmail—Chat messages (items under the Chat label) are skipped.