Phase 3: Migration and Testing
The migration process moves your application through the following three stages:
- Prepare your Pega Cloud development environment
- Package the application using a Pega Rule-Admin-Product (RAP) and export from your on-premises environment to a local server.
- Import the RAP into your target Pega Cloud development environment. As part of the import process, Pega automatically upgrades the application rules. As part of this step, you should perform application regression testing and make any application modernizations identified in the testing.
- Move the application into a Pega Cloud staging environment, using Deployment Manager. In this environment, you:
- Set up Deployment Manager and complete the move to the staging environment using a standard CI/CD pipeline.
- Work with the Pega Cloud Services team to migrate your redacted staging data, and run all your testing in that environment. Any changes resulting from this testing must be made in the development environment only.
- Conclude this phase of your migration after your applications in the staging environment pass your testing.
- Deploy your application into a Pega Cloud production environment. During this phase, you will work with the Pega Cloud Services team to:
- Create a “cut-over” plan
- Complete a “practice run” of the data migration
- Remediate any data issues discovered by the migration process
- Complete performance testing using your full practice data
When all phases are complete, the final data migration can be done. You will work with the Pega Cloud Services team, using your cut-over plan, to migrate your production data and then have the production system “go live” for your users.
Preparing your new Pega Cloud Services environment
There are a series of "Getting Started" articles on Pega Community, which were written for clients who are new to Pega and have subscribed to Pega Cloud Services. Although you are not "new to Pega," you are new to Pega Cloud, so you will need to follow most of the steps in the Getting Started with Pega Cloud Services series.
NOTE: Since you are not “new to Pega,” you already have applications to migrate to your new Pega Cloud environments. Some of the “Getting Started” articles, such as Implementing Your Applications will not apply to you.
Deploying changes to Rules and Data in Pega Cloud development
Your Pega Cloud Services subscription includes several environments:
- Development (“dev/test”)
- Staging (”pre-production” or “pre-prod”)
Some clients subscribe to a “production mirror” environment, or multiple QA environments, such as a QA environment for their QA team testing, and a User-Acceptance-Testing (UAT) environment for user testing. If you have a QA environment, you should certainly include testing in that environment. For the purposes of this article, however, we will not refer to any of these other environments, as they are not part of the “standard” Pega Cloud Services subscription.
When working with your application, Pega very strongly recommends that you make all changes in the development environment. The concept behind having multiple environments is that changes are made and tested in the development environment, and then these changes are deployed into the staging environment for additional testing and performance testing. After the changes have successfully passed all testing, you move the changes into production. If there is not a controlled method for migrating changes, the different environments can get out of sync, which would lead to invalid results during the testing process.
To control this process, Pega provides Deployment Manager. Deployment Manager is a simple, ready-to-use application that offers built-in DevOps capabilities. It leverages the Pegasystems case management technology to manage an automated orchestration engine, enabling you to efficiently build and run your CICD pipelines.
For details on using Deployment Manager in a Pega Cloud environment, see the “Getting Started” article Moving your application into production: DevOps and Pega Deployment Manager.
For an overview of Deployment Manager itself, see Getting Started with Deployment Manager.