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. Run your ant scripts to force a rebuild of any generated artifacts within your projects (for example, Apama queries, scenarios or Java\C\C++\.NET code using Apama APIs). Check the build 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, recreate 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.