Custom settings in configuration files are not migrated. You can merge your source configuration files with their equivalent configuration files in the target system to recreate many of the settings.

When you update customized configuration files before starting the migration process and taking the source system offline, you allow more time for the migration tool and post-migration tasks in your migration downtime window.

Commonly customized settings include machine provisioning limits, timeout intervals, and reclamation request intervals.

Because the user name format was changed between vCloud Automation Center 5.2 and the current vRealize Automation version, you must change the user name formats in associated customization scripts. The user name format in the source vCloud Automation Center 5.2 environment was domain structure, for example, test\username. The user name format in the target vRealize Automation environment is UPN structure, for example username@test.local.

If you made configuration setting changes in the following source configuration files, consider merging your changes with the files in your target vRealize Automation system.

  • ManagerService.exe.config

  • DynamicOps.DEM.exe.config

    This file exists for each DEM service in each DEM folder.

  • VRMAgent.exe.config

    This file exists in each folder.

For more information about settings that you can customize in vRealize Automation configuration files, see Installation and Configuration and Machine Extensibility in vRealize Automation documentation. Some configuration file settings that were available in vCloud Automation Center 5.2 might not be available in the target vRealize Automation system.