Appendix: Migration Checklist
+
This content applies to On-premises, Client-managed cloud and Pega Cloud environments
Phase 1: Assessment and Planning
REQUIRED ACTIONS | DATE COMPLETED | DATE COMPLETED |
CLIENT | PEGA | |
Review the documentation, tools, and resources provided and consult with your Pega account team | N/A | |
Run Pega Cloud Readiness Tool on each application to be migrated and review tooling output with Pega. Identify and document changes and remediations required when updating to the latest version and Migrating to Pega Cloud | N/A | |
Review Pega Cloud Connectivity Options with Pega and decide on the appropriate solution to fit your business needs. |
|
|
Create Connectivity Plan outlining all integrations between Pega Cloud and other systems. (External, on-prem, other cloud providers) Review Connectivity Plan with Pega. |
| N/A |
Evaluate applications for update to the latest version of Pega Infinity and migration to Pega Cloud focusing on the following areas: Platform and/or strategic applications
Data & Database
Infrastructure & System Configuration
Assess the impact and risk for updating your applications to the latest Pega version and identify any required remediations. Pega team to review the output shared by the Client. |
| N/A |
Perform a gap analysis between the current deployment model and the target deployment model in Pega Cloud to assess the readiness of your applications to be migrated to Pega Cloud.
Complete the GAP Assessment worksheet to help identify GAPs. Review the analysis with the with the Pega team |
| N/A |
Plan gap remediations and required changes for target version compatibility and Pega Cloud compliance. Identify solutions, document use cases and requirements and define validation criteria for all gaps and incompatibilities. Client to closely work with Pega to close all the gaps/workarounds as per Pega Cloud standards. |
|
|
Migration strategy: Define migration phases and approach. | N/A |
|
Generate Route to Live plan outlining the following:
|
| N/A |
Create Migration Project Plan using sample template |
| N/A |
Review database and file storage entitlements for all target environments to ensure allocations meet business needs. |
|
|
Establish project governance and project calls required throughout the migration Project. To be scheduled as follows:
| N/A |
|
Phase 2: Application Migration, Update, and Remediation
Stage 1: Preparing your Pega Cloud Development Environment
REQUIRED ACTIONS | DATE COMPLETED | DATE COMPLETED |
CLIENT | PEGA | |
Pega to provision all the environments after the contract is signed. | N/A |
|
Establish infrastructure connectivity as defined in Connectivity Plan. |
| |
Package application as a Rule-Admin-Product (RAP) For more information, see Migrating Application from Source Prod environment
Also see, Packaging a release: |
| N/A |
Export RAP from source pre-prod/Prod-like environment |
| N/A |
Import RAP to target Pega Cloud Dev environment |
| N/A |
Import RAP from source Dev environment with any required operators, access groups, etc. |
| N/A |
Perform post update steps as required for the platform or strategic apps. | N/A |
Stage 2: Application Remediation
REQUIRED ACTIONS | DATE COMPLETED | DATE COMPLETED |
CLIENT | PEGA | |
Implement application changes required for any cloud gaps and Pega Platform software update as defined in the Migration Project Plan. | N/A | |
Perform a full set of application regression tests to validate functionality. Fix all the issues found during testing. | N/A |
Phase 3: Validating Applications on Pega Cloud
Stage 1: QA Migration and Validation
REQUIRED ACTIONS | DATE COMPLETED | DATE COMPLETED |
CLIENT | PEGA | |
Promote Rules from Pega Cloud Dev environment to QA/Test.
Pega recommends using the Deployment Manager capabilities to sync the environments. |
| N/A |
Import any test data from source QA environment using RAP files. | N/A | |
Import RAP from source QA/Test environment with any required operators, access groups, etc. |
| N/A |
Perform end-to-end application functional testing, including integration testing. Perform any additional regression testing as required. Review PDC for alerts and warnings. |
| N/A |
Stage 2: Staging Migration and Validation
REQUIRED ACTIONS | DATE COMPLETED | DATE COMPLETED |
CLIENT | PEGA | |
Promote rules from the Pega Cloud QA environment. Pega recommends using Deployment Manager to promote rules between Cloud environments. |
| N/A |
Perform Data Migration Pre-Requisites for source environment to establish connectivity. See Appendix: Data Migration Prerequisites. |
|
|
Client submits a CC request in MSP for data migration specifying source and destination environment details and table/schema info for the migration. |
| N/A
|
Migrate data from source stage/pre-prod environment | N/A |
|
Pega Performs post Migration Steps (as required)
| N/A |
|
Import RAP from source pre-prod environment with any required operators, access groups, etc. | N/A |
|
Perform post update steps as required for the platform or strategic apps. |
| N/A |
Update system name and PDC URL and reboot system. (If Required) |
| N/A |
Perform full set of application regression tests to validate functionality and fix any issues found during testing. Perform any additional testing as required in test plan. | N/A | |
Perform PDC review check | N/A | |
Perform security & penetration testing as required. For Pen testing, an Incident request (INC) will need to be raised in MSP. |
| N/A |
Phase 4: Data Migration and Production Go Live
Stage 1: Production Environment: Preparation and Dry Run
REQUIRED ACTIONS | DATE COMPLETED | DATE COMPLETED |
CLIENT | PEGA | |
Review database and file storage entitlements for all target environments to ensure allocations meet business needs. |
|
|
Synchronize any parallel development and promote through lower environments to test and validate. | N/A | |
Promote rules from the Pega Cloud Staging environment. Pega recommends using Deployment Manager to promote rules between Cloud environments |
| N/A |
Clone source Production environment (read only) | N/A | |
Perform Data Migration Pre-Requisites for source environment to establish connectivity. See Appendix: Data Migration Prerequisites. |
|
|
Client submits a CC request in MSP for data migration specifying source and destination environment details and table/schema info for the migration. | N/A | |
Perform data migration from cloned source Production environment | N/A |
|
Pega Performs post Migration Steps (as required)
|
N/A |
|
Import RAP with any required data instances or fixes from lower environments on Pega Cloud | N/A |
|
Perform post-update steps as required for the platform or strategic apps. |
| N/A |
Update system name and PDC URL and reboot system. (If required) |
| N/A |
Perform application sanity testing. | N/A | |
Execute thorough performance testing and review results. |
| N/A |
Perform PDC review check | N/A | |
Repeat dry run migration steps to optimize data migration, performance and address any issues. | N/A |
|
Client to provide signoff on dry run. | N/A | |
Prepare Production Cutover Runbook and review with Client. |
|
|
Stage 2: Production Environment: Final Migration and Go-live
REQUIRED ACTIONS | DATE COMPLETED | DATE COMPLETED |
CLIENT | PEGA | |
Perform Data Migration Pre-Requisites for source environment to establish connectivity. See Appendix: Data Migration Prerequisites. |
|
|
Client submits a CC request in MSP for data migration specifying source and destination environment details and table/schema info for the migration. |
| N/A |
The Pega Change Advisory Board will review and approve the request for data migration. | N/A |
|
Follow and execute all the steps mentioned in the production runbook. | N/A |
|
Perform application smoke testing. |
| N/A |
Schedule online bridge calls between Pega and Core Client team. |
| N/A |
Go-No Go Decision meeting with Client including all key stakeholders. |
|
Phase 5: Continuous Improvement and Evolution
Post go-live support
REQUIRED ACTIONS | DATE COMPLETED | DATE COMPLETED |
CLIENT | PEGA | |
Enter two week Hypercare period in which Client will monitor & review outputs from PDC monitoring and engage Pega performance experts if needed. |
|
|
Discuss what worked and what can be improved in future migration. |
|
|
Plan future work required to improve guardrail compliance, Keep Pega Current, and adopt the latest features. | N/A |
Previous topic Keeping Pega Current Next topic Appendix: Data Migration Prerequisites