# Migrating from a previous version

This topic provides high-level instructions on how to migrate your deployment application to the current version of the Deployment Template.

Due to the flexible nature of the Deployment Template and the opportunities for customization, specifying a comprehensive migration path to Deployment Template 3.2 from a previous version is not possible. It is the job of Deployment Template users to know how they have customized their deployment so that the appropriate modifications can be retained.

However, it is possible to follow high-level steps that guide your migration path. Above all, you must be aware of the customizations that you made to the previous Deployment Template files so that you can port them to the newer version.

To upgrade to Deployment Template 3.2 from a previous release:

1. Upgrade to Platform Services 6.1 and Oracle Endeca Workbench 2.1.
2. Optionally, upgrade to Content Acquisition System 2.2.
3. Install Deployment Template 3.2, as documented in the "Installation" topic in this chapter. Make sure you read the new release notes to see if any changes will affect your application.
4. Run the Deployment Template 3.2 deploy script to generate a new application folder.
5. Port the changes that you made to the old AppConfig.xml over to the Deployment Template 3.2 AppConfig.xml.
6. Replace the Deployment Template 3.2 pipeline with your custom pipeline.
7. Place your input source data in the appropriate directory.
8. Drop any custom Java packages into the Deployment Template lib/java directory.
9. Run the initialize_services script, load the source data, and run a baseline update.

If everything runs correctly, you can then migrate other components of your application, such as your CAS crawl configurations.