In the validation phase of a G Suite (formerly Google Apps) migration using Transformer, you will:

Review Results

Use the Bridge Information log and Transaction Log to review the results of your migrations.

The Bridge Information log provides summarized information for multiple Bridges, and the Transaction Log provides granular information for every object processed by the Bridge.

Resolve Failures

Use Bridge ReportsError Codes, and the Execution Log to track and resolve errors encountered during migration.

Note: Many failures do not require any action in the source environment to resolve. Example: Any class of Exponential Back-off failures can be repaired automatically by running a Repair Failures Action.

Migrations between two G Suite environments have a special set of additional Bridge Reports that can be used to identify additional information about Transactions that failed during migration.

To generate these reports, choose the Failed Transactions for Google option from the drop down menu when generating Bridge Reports. The following three reports will be generated:

ReportDescription
Error SummaryA list of all errors encountered, and the number of times each error was encountered.
Transaction FailuresThe full list of every error encountered, with all details.
User Permissions FailuresA list of every user that could not be accessed during the migration.

Resolve Failures with the Error Summary report

Failures can be resolved by consulting the Message field in the Error Summary report. 

  1. Export the Failed Transactions for Google Bridge Report.

  2. Open the Error Summary report

  3. Consult the Message field for the reason why the Transaction failed during the migration.

  4. Consult the Error Code documentation for instructions on how to resolve the failure.

Note: If the Error Code documentation does not have instructions on how to resolve the failure, please email support@appbridge.io and include the Error Summary report as an attachment.

Use the User Permissions Failures sheet to identify users that have been suspended, removed, or renamed.

Repair Failures

Once resolved in the source environment, failures can be repaired by executing a Bridge using a Retry Failures Action or Delta Action.

Use the Retry Failures Action to save time. This Action will only retry specific Transactions that failed in the previous execution, but won't pick up any new or changed Transactions.

Resolve Support Tickets

To help resolve support tickets post migration, individual Transactions can be tracked from Bridge Reports. To track down specific failed Transactions, use the Transaction Failures Bridge Report.

Locate Failed Object

  1. Ask users to provide the object owner, object ID, and object location (folder path) in their support ticket.

  2. Export the Failed Transactions for Google Bridge Report.

  3. Open the Transaction Failures sheet

  4. Locate the failed object by searching for any of the following attributes:
    1. Object owner
    2. Object ID
    3. Object name
    4. Object location 

Resolve Failure

  1. Consult the Failed Entry field for the reason why the Transaction failed during the migration, and retrieve the Error Code.

  2. Consult the Error Code documentation for instructions on how to resolve the failure.

Note: If the Error Code documentation does not have instructions on how to resolve the failure in your logs, please email support@appbridge.io and include the Error Code, Failed Entry, and Log fields in your message.

Congratulations! You have completed the G Suite to G Suite Migration walkthrough.