1. If the new and old Apama are on different machines, update deployment scripts (for example, Ant scripts and properties files) to specify the correct host names for the new installation.

2. If the new and old Apama are on the same machine, make sure all processes from the old installation are shut down.

3. Re-run any build or deployment scripts to make sure generated artifacts such as Apama queries, plug-ins, and scenarios from your projects are up to date. This task could include re-exporting and re-running Ant scripts, executing engine_deploy, rebuilding Docker images, and re-running custom scripts. Review the output for errors and warnings.

4. Inject your migrated applications into the new Apama by running them in your user acceptance testing (UAT) environment. Scan the correlator logs for any errors or warnings. Re-run all your system tests (for example, PySys test cases) and ensure your application behaves as expected.

5. If you are using Command Central, re-create Apama instances in the new installation using the same command line, GUI, or composite template procedure you used to create the instances in the old installation, with modifications to accommodate any deprecated or removed items mentioned in the Apama release notes.