Pre-installation project migration steps

This section describes the pre-installation steps.

Pre-installation project migration considerations

Review and perform the following before migrating existing projects.

  • To work with projects earlier than 12.60, you first need to upgrade to version 12.6x before you can migrate to 2023; direct migration is not supported. You can then upgrade your projects to the latest version. For details, see Upgrade existing projects to newer versions.

  • Migrating projects from one database type in version 12.60 to another database type is not supported.

  • Review the Support Matrix to make sure that you meet the requirements for working with the version being used.

  • Review the list of features that are not available or fully implemented in this release. For details, see Deprecated features.

  • Before beginning the installation, back up the projects, the database, and the repository. For details, see Back up projects in installation.

    Note: During the migration process, data is taken in read-only mode; therefore, no changes should occur on the database level.

Back to top

Upgrade existing projects to newer versions

The following tables describe how to upgrade projects from earlier versions. Note that not all projects can be migrated directly.

From version: To latest version:
2020 or later

  • MS SQL or PostgreSQL database: Any version supports direct upgrades.

  • Oracle database: 24.3 is the latest version to support direct upgrades. If you are using version 24.1 or earlier on an Oracle database, you must first upgrade to 24.3.

For details, see Upgrade projects to the latest version.
12.6x

Direct migration to 25.x is not supported. Instead, you must migrate to version 2023, and then upgrade to the latest version.

For details, see Migrate projects.

Back to top

Back up projects in installation

Back up all your projects in the existing installation that you plan to migrate. We recommend that you deactivate projects before backing them up.

If you must back up while your project is still active, you must back up the database before the file system. We also recommend backing up the file system as soon as possible after backing up the database.

Note:  

  • Before you run the migration process, perform a full backup of your projects that includes the project database schema and the project repository.

  • Version Control: Version control enabled projects cannot be backed up while there are checked out entities. All entities must be checked in to the corresponding version of Quality Center or ALM. To determine if there are checked out entities, see this KB article.

To back up the project database schema on the database server:

  • Microsoft SQL database. To back up the project database schema on the database server, see this KB article.

  • Oracle database. To back up the project database schema on the database server, see this KB article.

Back to top

Overview of migration process

This section describes how to migrate projects from versions earlier than 12.60.

Upgrade projects to 12.60 (pre-installation)

To migrate ALM projects, you first need to upgrade your projects to version 12.60. For details, see Pre-installation project migration steps.

During the installation process, you need to migrate the configuration data that was stored in ALM Site Admin and LAB to OpenText Enterprise Performance Engineering. For details, see Configure servers and hosts.

Note: You can also perform this step post-installation from the Configuration wizard, provided that you specify a new Site Admin and LAB schema; if you use the existing schemas nothing happens. For details, see Post-installation configuration steps.

Migrate project data (post-installation)

After installation, you need to migrate project data and the file repository from existing projects using the migration tool in Administration.

Project data which includes scripts, attachments, run results, .xml files, and templates is migrated from ALM Site Admin and LAB to the OpenText Enterprise Performance Engineering server.

For details, see Migrate projects.

Back to top