If you want to abort the migration, you can simply close the application with the X at the top right corner.
Note: Aborting the migration prematurely could leave the target site in a non-functional state. Only do this if you can restore the target environment from a snapshot.
The migration application uses log4net to write information to a log file. This file includes analysis and migration information that can be useful for debugging and troubleshooting.
The log file is by default created in the same folder the application and is called ImageVault.Migration.Log.txt. For advanced usages, if the default values should not suffice, the logging behavior can be controlled by modifying the configuration file log4net.config.
In addition to logging, the migration tool also saves various data files. These files contain XML formatted output data from the analysis and perform steps. Since the application directly uses these files they should not be modified by hand, but can be viewed in order to see more details about the different data objects.
Note: Saving the data files for later reference might be a good idea, since the data included might be needed to migrate the Episerver content.
Analysis and perform data grids
The migration application will present a data grid controller, storing information both in analysis and perform steps. The data presented is read only, but it can be exported to the clipboard by selecting specific rows and using Ctrl+C.
The entire contents of the data grid can be selected and copied to the clipboard by selecting any row, then hit Ctrl+A followed by Ctrl+C.
For tracability and in order to make it easier to convert information published in Episerver the migrations tool adds some metadata to the migrated files.
|IV3_DataObjectId||The unique id used in ImageVault 3.|
|IV3_AddedBy||The username of the user that uploaded the file to ImageVAult 3|