You can specify how MigrationExceptions should be handled during migration. Examples of migration errors include missing users or organizations, and missing required properties.
The EserverMigrationService.solutionValidationLevel setting controls how errors are handled. This setting has three possible values:
fail– This is the highest and recommended setting. A Migration Exception is thrown and logged, and migration halts.error– This is the least preferred setting. A Migration Exception is printed and logged, and the current solution is ignored.off– This setting is not recommended. No solution validation occurs. Any mismatched property mappings are ignored and solutions are saved with null values in these properties.
See Troubleshooting Migration for more information on error conditions and how to resolve them.
