The cost of the migration depends on the number of overwritten XML elements in the standard configuration and on the classes implemented according to customer requirements. If the customizing attribute at the <version> element is required in custom XML files, the database must be migrated in order to use the customizing in a new ARIS Risk & Compliance Manager version. (For detailed information, refer to Overwrite the schema version.) To avoid a database migration, customizing of attributes and object types should not be supported. If attributes are not customized, the database is migrated automatically to the new version. Please note that the migration of user-defined data must be performed and tested very carefully.