Migrate to SaaS
This section provides you with important information on how to migrate OpenText Enterprise Performance Engineering or OpenText Application Quality Management (ALM) from on-premises to SaaS. This is only relevant if you are planning to run OpenText Enterprise Performance Engineering in a SaaS environment.
Migration plan overview
The following table provides an overview of an OpenText SaaS migration plan. Tasks specific to the migration are based on customer readiness. The final project plan should be agreed to between OpenText SaaS and the customer following project kickoff.
Phase | Customer | OpenText Action Items |
---|---|---|
Set up new OpenText Enterprise Performance Engineering (1-2 weeks) |
|
|
Upload data (1-2 weeks) |
|
|
Upgrade sample projects (1-3 weeks) |
|
|
Dry-Run validation (3-8 weeks) |
|
|
Upgrade product (2-4 weeks) |
|
|
Environment diagram
This diagram illustrates the SaaS environment and interaction between the OpenText Enterprise Performance Engineering and customer AUT environments.
Migration tasks
For details about migrating OpenText Enterprise Performance Engineering or OpenText Application Quality Management from on-premises to SaaS, see the following instructions: