Interpret Google Workspace Migrate error messages

CryptographicException

You might get this code when trying to edit a template. The template doesn't load. To resolve the issue, choose an option:

• If you have the Google Workspace Migrate platform encryption key, uninstall the platform and manually clear out the ProgramData/AppBridgefolder. Then, reinstall the platform. Go to Option 1: I have the encryption key .
• If you don't have the key, create new projects. Data encrypted with the old key is no longer accessible.

If you get this code with HttpStatusCode is Forbidden and the message  Method - CreateProject in the platform log file, and you can't create a project, check the admins' permissions. For details, go to the Troubleshootsection of Create a project . 

DisposalError

An error occurred while removing unused resources.

NoDataReturned

No data was returned from the provider. Check service host log for details.

UnexpectedDataAccessError

An unexpected error occurred accessing the data provider.

MySQLConnectionError

An error occurred while connecting with MySQL

Bad Request

There’s data corruption in the source environment. The source data causing the issue is probably defective. You might also see this error when migrating an attachment that is unsupported by Gmail, such as an executable file.

If you want to keep the data, analyze which objects are affected and move them manually to your Google Workspace account. For details on how to manually move objects, consult your source data documentation.

Unauthorized

Google Workspace Migrate doesn't have the required access to a source or target system.

During a Microsoft Exchange migration, you might see this error:

• When you try to set up or use a connection—You don’t have permission to impersonate a user on Exchange or your Exchange credentials are expired or incorrect. To fix the problem, edit the connection and make sure the credentials are correct. Then, try the Exchange connection again.
• In the execution logs for individual users—Usually means impersonation rights granted to an administrator are only valid for a subset of users (for example, a specific organizational unit), instead of all the users that you want to migrate.

Forbidden

For details about this error, point to the transaction and click More Transaction details. Possible causes of this error are:

• A Google Workspace service (such as Gmail or Google Drive) isn't turned on. In the Google Admin console, turn on the service .
• You exceeded your daily API quota levels. Apply for a higher quota level in the Google Cloud console. Or, wait until the following day to proceed.  Learn more
• You exceeded a shared drive limit (for example, you might have too many items in a shared drive or exceeded the limits for nested folders). For details, go to Shared drive limits .

Conflict

Google Workspace Migrate was unable to resolve a conflict with a data source.

If you are running an email migration, the label wasn't created on the target because its name conflicts with an existing label. To resolve the conflict, locate the email folder or label on the source environment and change its name.

Gone

Transient errors. Run a delta migration. If the error persists, contact Google Workspace support .

Request Entity Too Large

Migrating email messages

An email message and its attachment is larger than 50 MB (maximum size including attachments).

To migrate these messages, use the Upload the attachments of large messages to Driveoption in the settings template to send attachments directly to Drive. For details, go to Migrate Exchange content .

Migrating messages to Google Groups

An email message and its attachment is larger than 25 MB. You can't migrate messages over 25 MB to Google Groups. For details, go to  Message and posting limits . 

Too Many Requests

The migration is overloading a source or target system with too many requests.

Determine which service is overloaded and, if possible, increase the service limits.

StateInitializationFailed

Existing commit state couldn't be initialized.

InvalidResponseId

Commit response service is invalid.

StateCrawlRequestFailed

A request failed during target connection discovery.

RequiredPriorElementFailed

A required prior element couldn't be committed.

RequiredPathIllegal

The required parent object failed.

RequiredParentPathFailed

The required parent object failed.

UnexpectedErrorDuringCommit

An error occurred while evaluating the transaction's dependencies: {1}{0}{2}.

The placeholders in the error message expect the following values:

• The object type of the transaction
• The property of the object
• The parameter value

CommitServiceClosed

The commit service isn't available to process requests.

TargetIdUpdateFailed

Failed to write the target identity of an object to the database after a successful migration.

To resolve the issue, run a delta migration. Doing so, however, might create a duplicate of the object on the target system. The duplicate data can be deleted manually.

NoResponse

No response service was provided.

Unauthorized

The connector isn't authorized for that request.

MissingRequestType

No request type was defined for this request element.

TooManyRequestTypes

Only one request type may be specified for a single object fetch.

LocationNotFound

No object was found at the specified location. You might get this error if you're migrating:

• From Microsoft SharePoint and your location list doesn't include the affected location. Update your list and add it to your connection.
• From a Google Workspace shared drive to a shared drive on the target account and the target user doesn't have a Google Workspace license that includes shared drives.
• From a file share and the nodes don't have sufficient permission to access the object. 

LocationTypeMismatch

The object found at the specified location was not of the expected type.

ReadOnlyType

The request type does not allow write operations.

TooManyResponses

The request returned a collection when a single value was expected.

RequestConversionError

Type conversion failed for this request.

SerializationError

Could not serialize converted type objects.

ResponseRoutingError

The response service received an unexpected request.

ConnectionUnavailable

The requested connection is unavailable.

DispatchFailed

The intended response service was initially found, but the request could not be dispatched.

TryAgainLater

The request could not be currently completed. You should try again later.

WriteOnlyType

The request type does not allow read operations

InvalidWriteContext

The request could not be written in the current context.

You might see this issue if you attempt to migrate the same source content to more than location within Drive. For more information, go to Migrating files & folders to multiple locations in Google Drive for Sharepoint , file shares , Box , or Google Workspace .

InvalidElementData

The supplied element did not specify required data.

DataRequestFailed

A request for additional data failed.

You might see this error if you're trying to migrate files from SharePoint that are larger than 2 GB.

Make sure that the node servers have sufficient space available. The nodes must have more free space than the size of the largest file you're migrating. For more details on SharePoint file sizes, go to Items over 2 GB .

RequestInvalidated

The requesting service was invalidated.

UnexpectedException

An internal connector error occurred. You might get this error if:

• You have more than the maximum number of display lookup columns defined for a SharePoint list.
• You're migrating from a file share, and the nodes don't have sufficient permission to access the item. 
• Metadata is no longer available in the source.

Try these fixes:

1. Confirm that the failing source files are accessible and downloadable. 
2. Check the platform logs to see if your problem is combined with another error. 
3. If the error persists, follow the steps and provide the information in Contact support for Google Workspace Migrate issues .

OrphanedItem

The account for the user that created the SharePoint file or folder is permanently deleted, and the data is no longer available.

In the template, uncheck the Migrate versions to revisionsbox and try again.

InvalidRequest

An internal connector error occurred.

InvalidAction

A request for an unrecognized action was sent to a connector. You might see this if you have mismatched versions of platform and nodes, and a new action is sent to an old node.

SkippedByContext

A transaction has been skipped. It has been marked with this code for identification purposes.

WarnedByContext

The request could not be completed. Some data might not have been written correctly.

InvalidImport

The specified import string was invalid.

ResolvedByContext

A request was made to change an object that exists and is unable to be changed. No action was taken.

AbsoluteUriNotSupported

The location was an absolute URI which is not supported. 

NoMatchingSiteCollection

The mapping location did not match any known site collection.

InvalidLocation

The requested location is invalid.