Migrate a galaxy in a multi-galaxy environment​.

The migrate workflow in a multi-galaxy environment is the same as in a single galaxy environment.

Migrating the galaxy database leaves your object configurations intact. Although the object code changes when the underlying object type is updated, for example, if the $UserDefinedObject is enhanced to support a newly-introduced feature, these updates do not change any object configuration you made in the previous version.

Use the following procedure if you have an existing galaxy that was created in an earlier version of System Platform.

1. Run setup.exe from your installation media to Install the new version of System Platform, or upgrade an earlier version of System Platform to the new version, as applicable.

2. When installation and configuration are complete, open the IDE.

3. Connect to a galaxy that was created with an earlier System Platform version. The galaxy migration process begins automatically once the galaxy is connected.

4. If tagnames are duplicated between Automation Objects and graphics in the galaxy, a message about the duplicate tagnames is displayed in the progress dialog. A similar message is logged in the Logger, along with a list of the duplicate tagnames.

   Note: As of System Platform 2023 R2 SP1, you are blocked from duplicating tagnames between graphics and Automation Objects. However, duplicate names are not blocked during galaxy migration.

5. After the import is complete, rename either the graphic or object that share the duplicate tagname.

   If you are using Operations Control - connected experience, refer to Galaxy migration to support connected experience.