Migration Output Files

All migration log files are written to the directory specified on the command line when running the script. These files are created during the migration steps. The same set of log files is created for pre-migration (step 3) and migration (step 5), but in separate directories.

Related Topics
About the FTR Schema Migration Tool
Running the Migration Tool
Migration Property File Settings
Log File Description
Migration.log This file contains output on the status of the migration. It logs all status, successes and failures, as well as debug information when turned on.

You can use this file as the starting point for information on the status of the migration.
filesStatus.csv This file contains completion status and execution times. It includes the name of the file, the status of the file (COMPLETE or FAILED), and on success, the migration time or on failure, the reason for the failure.

You can use this file to determine which input files had problems in order to decide whether additional migration steps are necessary.
Convertedids.txt This file contains a list of the IDs that were successfully converted. This is an informational file to cross check the IDs that were successfully migrated.
unConvertedObjectIds_XX.csv This file contains a list of objects that could not be converted. XX represents a sequential number, starting with 01. Each file can contain up to 50,000 unconverted objects, and there is a new file for each chunk of 50,000. The file contains the Type, Name, and Revision of each object that was not converted, along with an additional classification code. The current classification codes are either MixedUsage or MixedComposition.

You can use this file for informational purposes, to get an understanding of the objects that were not converted.
unConvertedObjectIds_xx.txt This file contains a list of object IDs that could not be converted.

You can rename this file to objectids_XX.txt in order to re-run it through the migration script when the reason for a failure has been addressed.