The following measures can help to understand migration errors:

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.

Viewing the document logs

For each document, a <filename>.data.log and a <filename>.replaced.json file (if activated in the debug settings, see Create transformed metadata file) is created in the export directory during the migration process. The LOG file logs all the activities and error messages that occurred while processing a document. 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.