Migrating data from a current Orchestrator instance to a new one

You can migrate data from an existing Orchestrator instance to a newly-installed Orchestrator instance.

Current instance and new instances that have the same version of Orchestrator

If the (existing) source and (new) target instances have the same installed version of Orchestrator, migrate the database using one of these methods:

Run a backup of the database using a mysqldump export on the source, then run a database mysql import on the target. This method preserves the work orders but may take a long time if the database is large.
To run the backup:
```
/opt/aspera/common/mysql/bin/mysqldump -h IP_address –u root –p orchestrator > /tmp/orchestrator_db_backup_timestamp.sql 
```
To run the import:
```
mysql -h <MYSQL HOST> -u root -P <PORT; DEFAULT IS 3306> -p orchestrator < /tmp/orchestrator_db_backup_timestamp.sql
```
If necessary, manually copy the configuration files from source to target.

Current instance and new instances that have the different versions of Orchestrator

If the source and target Orchestrator instances do not have the same Orchestrator versions (for example, the target is on higher version), choose one of these options:

Follow the same procedure as above, then run the Orchestrator setup after the database migration.
Create a new installation on the target instance with the same version as the source instance, then do an upgrade to the higher version of Orchestrator on the target instance.