Skip to main content
LinkedIn
Copied!

Migration Checklist

This content applies only to Cloud environments.

Phase 1: Assessment and Planning

 

  DATE COMPLETED DATE COMPLETED
REQUIRED ACTIONS CLIENT PEGA
Register for migration: 
https://community.pega.com/form/register-modernization-interests
  N/A
Pega explains the detailed migration process. N/A  

VPC/VPN Provisioning:

Once the VPC is provisioned, Client can request for Pega Cloud VPN to connect to the servers hosted in Client network securely.

Client can choose either Pega Cloud VPN / VPC Peering / AWS Direct Connect options. Client needs to raise a Change request for VPN setup.

All the communication between Client and Pega Network team should be captured via an Incident raised by Client in the Pega Support Portal.

https://community.pega.com/knowledgebase/articles/pega-cloud/cloud/completing-your-environment-connectivity 
https://community.pega.com/knowledgebase/articles/pega-cloud/cloud/pega-cloud-vpn-service

   

Evaluate applications for upgrade to the latest version of Pega Infinity and migration to Pega Cloud focusing on the following areas:

  • Platform and/or strategic applications 
  • Cloud infrastructure
  • System configuration

Assess the impact and risk for upgrading your applications to the latest Pega version and identify any required remediations. 

https://community.pega.com/knowledgebase/articles/migrating-pega-cloud-services/assessing-your-infrastructure

Assess the readiness of your applications to be migrated to Pega Cloud. This process involves performing a gap analysis between the current on-premise deployment and the target deployment model in Pega Cloud. Then establishing a gap remediation plan for compliance with Pega Cloud standards. 

https://community.pega.com/marketplace/components/pega-cloud-readiness-tool

Pega team to review the output shared by the Client.

  N/A

Gap Remediation: Identify solutions for all gaps and document use cases, requirements, and solutions for all identified gaps.

Client to closely work with Pega to close all the gaps/workarounds as per Pega Cloud standards.

   

Migration strategy: Define migration phases and approach.  

https://community.pega.com/knowledgebase/articles/migrating-pega-cloud-services/migration-overview

N/A  

Create project plan using sample template

https://community.pega.com/knowledgebase/articles/migrating-pega-cloud-services/creating-migration-project-plan 

  N/A
Establish project governance and project calls need to be scheduled as follows:
  • Daily stand ups with the core project team
  • Weekly project plan and risk review meeting 
  • Monthly stakeholder meetings
N/A  

 

 

Phase 2: Application Migration and Upgrade

Preparing your Pega Cloud Development Environment

  DATE COMPLETED DATE COMPLETED
REQUIRED ACTIONS CLIENT PEGA
Pega to provision all the environments after the contract is signed. N/A  

Package application as a Rule-Admin-Product (RAP)

For more information, see Best Practices When Using RAP Files:
https://community.pega.com/knowledgebase/articles/migrating-pega-cloud-services/stage-1-preparing-your-pega-cloud-development-environment#RAP-files

Also see, Moving applications between systems:

https://community.pega.com/sites/default/files/help_v85/procomhelpmain.htm#tools/importexport/migration-con.htm

  N/A

Export RAP from source on-premise pre-prod/Prod like environment

https://community.pega.com/sites/default/files/help_v85/procomhelpmain.htm#tools/moverules/exporting-rules-tsk.htm

  N/A

Import RAP to target Pega Cloud Dev environment

https://community.pega.com/sites/default/files/help_v85/procomhelpmain.htm#tools/moverules/moverules4.htm

  N/A

 

Phase 3: Application Remediation and Testing

Remediate the identified application gaps

  DATE COMPLETED DATE COMPLETED
REQUIRED ACTIONS CLIENT PEGA
Implement application changes required for any cloud gaps and Pega Platform software upgrade   N/A

Identify potential rule conflicts

To identify potential conflicts between custom rules in your application and the upgraded version of Pega Platform, run the Final Conflicts report:

https://community.pega.com/knowledgebase/articles/system-administration/84/identifying-rule-conflicts

  N/A

Note:  This is required only if you are using Pega Customer Service.

Pega Customer Service Upgrade Checker helps identify overrides to critical rules in your application, and recommends solutions to ensure that your upgrade is seamless.

https://community.pega.com/marketplace/components/pega-customer-service-upgrade-checker
 

  N/A
Perform a full set of application regression tests to validate functionality.  Fix all the issues found during testing.   N/A

 

 

QA/Test Environment Migration

  DATE COMPLETED DATE COMPLETED
REQUIRED ACTIONS CLIENT PEGA

Promote Rules from Pega Cloud Dev environment.

Pega recommends using the Deployment Manager capabilities to sync the environments.

https://community.pega.com/knowledgebase/articles/devops/85/getting-started-deployment-manager

  N/A

Import any test data from source QA environment using RAP files.

https://community.pega.com/sites/default/files/help_v85/procomhelpmain.htm#tools/packagework/aboutpackagework.htm

  N/A
Perform end-to-end application functional testing, including integration testing.   N/A
Client signs off, certifying that the application is running in Pega Cloud.   N/A
Provision data migration tooling environments in the VPC for connecting and working directly with the environments and databases in the VPC. N/A  
Pega shares the windows box and replication instance IP with the Client. N/A  
Client to whitelist the IP shared by the Pega at their end on Source DB to allow remote connections   N/A

Create a user with the appropriate permissions to access the source database and share the Database details.

Oracle

Database Migration Service

https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.Oracle.html

Schema Conversion Tool

https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.Oracle.html

 

Postgre SQL

Database Migration Service

https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html

Schema Conversion Tool

https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.PostgreSQL.html

 

MySQL

Database Migration Service

https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MySQL.html

Schema Conversion Tool

https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.MySQL.html

 

SQL Server

Database Migration Service

https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.SQLServer.html

Schema Conversion Tool

https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.SQLServer.html

 

DB2 (LUW)

Database Migration Service

https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.DB2.html

Schema Conversion Tool

https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.DB2LUW.html

 

  N/A
Pega tests connectivity between data migration tools and Source Database and troubleshoots connectivity issues, if any. N/A  
Download DB clients based on the requirement and install them on the Windows box. Additionally, download DB driver jars as required. Also download the target version Pega build.  N/A  

Download and install the latest version of AWS SCT tool in the windows box for DB schema conversion.

https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Installing.html

N/A  
Run queries in the source DB to identify any tables without primary keys, and those having BLOB data.  Share the results with the client. N/A  

Apply primary keys to tables that have BLOB data.

Check for Database partitioning tables used in the application.

Note: Partitioning is not supported in Pega Cloud. Pega recommends converting to flat tables before migration.

  N/A

 

 

Stage Environment Migration

 

  DATE COMPLETED DATE COMPLETED
REQUIRED ACTIONS CLIENT PEGA
Promote rules from the Pega Cloud QA environment. Pega recommends using Deployment Manager to promote rules between Cloud environments.   N/A
Export RAP from source pre-prod environment with any required operators, access groups etc.   N/A
Migrate data from source pre-prod environment N/A  
Perform data only upgrade for Pega Cloud Staging environment N/A  
Perform Strategic app upgrade, if any. N/A  
Import RAP from source pre-prod environment with any required operators, access groups etc. N/A  
Perform full set of application regression tests to validate functionality and fix any issues found during testing.   N/A

Execute performance test and review results.

https://community.pega.com/knowledgebase/articles/performance/ten-best-practices-successful-performance-load-testing

  N/A

Client to raise Incident request for Pen testing.

https://community.pega.com/knowledgebase/articles/pega-cloud/cloud/vulnerability-testing-policy-applications-pega-cloud

  N/A

 

 

Phase 4: Data Migration and Go Live

Perform DRY RUN Migration
 

  DATE COMPLETED DATE COMPLETED
REQUIRED ACTIONS CLIENT PEGA
Disable Agents/listeners/QPs on the Pega Cloud production environment. N/A  
Restore PegaRULES schema from the Pega Cloud Staging environment to the cloud Production environment. N/A  
Clone source Production environment (read only)   N/A
Perform data migration (PEGADATA, CLIENTDATA schema) from cloned source Production environment
https://community.pega.com/knowledgebase/articles/migrating-pega-cloud-services/stage-3-production-environment
N/A  
Perform data only upgrade on Pega Cloud Production environment and upgrade Strategic apps, if any. N/A  
Perform application sanity testing   N/A
Perform PDC review check   N/A
Repeat DRY RUN migration to optimize data migration, performance and address any issues N/A  
Client to provide signoff.   N/A
Prepare production runbook and review with Client. N/A  

 

 

Production Data migration and Go-live
 

  DATE COMPLETED DATE COMPLETED
REQUIRED ACTIONS CLIENT PEGA
Client to submit SR for data 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.

https://community.pega.com/knowledgebase/articles/migrating-pega-cloud-services/stage-3-production-environment

   

 

 

Post go-live support

  DATE COMPLETED DATE COMPLETED
REQUIRED ACTIONS CLIENT PEGA
Two weeks Hypercare period in which Client will review outputs from PDC monitoring and engage Pega performance experts if needed.    
Discuss what worked and what can be improved in future migration.    

 

 

 

Suggest Edit
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us