Migrating Projects from Earlier Versions

Read this chapter carefully and follow all migration steps that apply to your case.

For non-project related actions required for various situations, see Post Installation Tasks .

Migration of add-on products is also included, so that all migration information is available in one place.

Many of the actions you must take to migrate projects to the current release depend on the version you are migrating from, and the features you use. Some manual steps are required. More manual steps are required for earlier versions than for 4.x projects due to the changes in architecture.

Read the rest of this section and then check the section for the release from which you are migrating:

• If you are upgrading from 5.0 to 5.1, the CDD model needs to be refreshed. See Migration from 5.0 to 5.1 for details.
• If you are upgrading from 4.0, first upgrade to 4.0.1 and then migrate to 5.1. See Migration of 4.x Projects, and referenced sections.
• If you are upgrading from 3.x, you can migrate directly to 5.0 and then to 5.1. Follow the manual steps as required. See Migration of 3.x Projects, and referenced sections.
• If you are upgrading from a version earlier than 3.0, first upgrade to the latest 3.x version, following directions in the 3.x documentation.
  Note: No migration steps are required for JDBC backing store implementations or data. JDBC backing store was first made available in 3.0.1 Hotfix 6.