Open Documentation Menu

Understanding migration errors

The following measures can help to understand migration errors:

Viewing the migration interface and the migration report (PDF file)

You can obtain an overview of the number of errors that occurred in the migration interface, which displays the errors that occurred during the last migration run in a table. A full overview of all errors in all migration runs is available in the migration report. You can download the migration report under Migration Report. The following section provides more details about how to understand migration errors.

Detailed errors overview on the “Migration Errors” page

The errors overview shows all migration errors from the last migration run and consists of the two following sections:

  • Graphical representation: Shows the distribution of the error types that occurred. The size of the segments corresponds to the number of errors.

  • List of errors: Contains all types of error that occurred. The number of documents in which the error occurred is shown in parentheses after each error type. Multiple errors can occur in each document. Accordingly, documents can be counted for multiple error types. However, each document is only counted once within a single error type.

Further details are available for each error type listed; you can access these details by clicking on the corresponding area of the chart or the error type in the list. The details view includes the following sections:

  • Error description: Description of the cause of the error.

  • Number of affected documents: Total number of documents with this error.

  • Sample documents: File paths to up to three documents where the error type occurred.

  • Troubleshooting: Recommendations for correcting the error.

Additional information may be displayed, such as the list of unassigned users. An action button may also be available. Click on the button (e.g., Edit mappings), to go directly to the relevant configuration page.

Viewing the log and the error log of the connector

The connector logs provide further help when errors occur. The connector uses d.3 logview for logging as standard. A log can also be written to a file if this is enabled in the configuration of the connector.

Viewing the document logs

For each document, a <filename>.data.log and a <filename>.replaced.json file (if activated in the error correction settings (debug settings) is created in the export directory during the migration process. The LOG file logs all the activities and error messages that occurred while the document was being processed. The REPLACED.JSON file logs the document metadata record that was created and transferred to the cloud.

Activating the debug log

If the current log is not sufficient for understanding why an error occurs, you can increase the log level. You can activate the debug log while configuring the migration.

Deactivating the virus scanner for the export directory

A virus scanner may cause performance problems. To increase performance, you can add an exception for the export directory. However, you must assess the risk of deactivating it beforehand.