In order to reduce project risk and ensure timely delivery, a thorough analysis of your current Pega deployment is critical for designing a migration strategy suitable to your business needs. This proactive, holistic assessment requires that you define the features and functionality in your current deployment that will be migrated to your deployment in Pega Cloud environments.
Pega requires that before beginning your update or migration, you complete a holistic assessment of your current application implementations and deployments, and create a detailed change plan. Assessment and planning determine the overall approach for migrating your Pega applications and data to Pega Cloud as efficiently as possible, thus reducing the risk of potential roadblocks.
Assessment and planning include:
- An in-depth review of the current Pega deployment, including applications, data, and existing environments.
- Capturing requirements for the migration and target Pega Cloud deployment, such as security policies, compliance policies, and performance SLAs.
- A gap analysis to identify any modernizations that must be made to your application and deployment as it moves to Pega Cloud (see Pega Cloud Services and Legacy functionalityin the Migration Overview)
- An application testing strategy that includes both functional and a performance tests
You will use this assessment to formulate your applications and data migration approach and execution plan. This step produces a list of gaps with a weighting for each, based on the complexity of change/implementation. This gap analysis lead to a detailed project plan for migrating your applications to Pega Cloud environments.
You should involve Application owners, System Administrators, Database Administrators, Network Engineers, and other stakeholders to collect the information necessary to perform the assessment. The data points captured in the Migration Assessment are used to compile a project plan to track the key milestones and tasks. After the project plan is in place, you will be ready to hold a kickoff meeting to commence the project and initiate project governance.
There are three main areas that must be assessed:
- Your Pega applications
- The database where your Pega application(s) and all Pega data is stored
- Your current environment or infrastructure
Pega provides the Client Cloud Migration Gap Assessment questionnaire to guide you through this process. This is a manual questionnaire which lists all the information which must be gathered before a migration, and highlights potential legacy functionality issues that must be addressed.
The Cloud Readiness Tool is also available from the Pega Exchange. This tool contains two utilities: The Application Readiness utility, and the Database Readiness utility. Note that since this tool is available from the Exchange, it is unsupported – any errors or problems will not be supported by GCS.
IMPORTANT: Since these utilities are used to document and measure your Pega application and data, they require that you run them in your production environment, or in an environment that is similar to production (staging or pre-production). If such an environment does not exist, then Pega recommends that you create a duplicate, where possible, of the on-premises production environment where you are running your Pega application(s), including a separate duplicate database. (Pega calls this duplicate setup the “pre-production” or “pre-prod” environment.) The utilities involve adding RuleSets and .jar files to the environment; therefore, it is strongly recommended that you do not do this in your production environment.
The Application Readiness tool includes a RuleSet, GapAnalysis 01-01, which must be added to the Application rule for each application you wish to migrate. This RuleSet contains an activity, “GenerateApplicationGapsReport,” which generates the application gaps report as an Excel file.
The Database Readiness tool is a .zip file (DBReadiness.zip) which must be extracted on your database server. The .zip file contains a .jar file: DatabaseReadiness_V4.jar. This .jar file is run from a command-line prompt, and will create an Excel file with database information.
For details on these tools, see the User Guide on the Cloud Readiness page (link above).
NOTE: There is no tool or utility for assessing your existing infrastructure – that must be done manually.
There are two main steps involved in moving your applications to Pega Cloud: updating (if you are not running on the latest version) and migrating. Different types of remediation may be required for each of these projects.
In older versions of Pega applications, or just older applications, the assessment should identify the legacy functionality and features that are no longer supported, and, in some cases, how that functionality is now provided in an improved and updated way in the latest Pega applications.
Pega recommends that as part of the assessment of your application and environment, you consider the changes required by updating to our latest version.
For details on the Update Assessment, please see Remediation.
The migration assessment begins with a comprehensive review of your Pega applications and the systems that support them. This includes analysis of your Pega software, including:
- The Pega Platform version
- A list of your Pega strategic applications by version
- Pega deployment type (i.e. high-availability, single schema, shared with other apps), and the usage profile (number of users, case volume)
- An integration profile that captures how your application interacts with other systems (for details, please see Integrating Pega applications with external systems)
- Details regarding your additional services (BIX, PDC, etc.)
Performing an application gap analysis is a vital milestone activity, during which you identify any potential modernizations required in order to migrate your deployment to a Pega Cloud environment, including a plan to implement these changes.
For details on the remediations needed to migrate your application, see Remediating for migrating to Pega Cloud.
The assessment process also includes performing an analysis of the data managed by your Pega application, in order to determine which data must be migrated, and the approach for migration with respect to the overall size, rate of change, and acceptable cut-over window. The data migration plan must identify all of your database schemas and tables that require migration to Pega Cloud.
As mentioned in the Pega Cloud Services and Legacy Functionality section of the Migration Overview, you must create and manage all database customizations using the database tools in the Pega Platform application. As custom database objects – any objects which were not present in the Pega-provided database deployment - are not supported in the Pega Cloud environment and will not be migrated, the following types of customized objects must be remediated.
- custom schemas
- stored procedures
Note: Stored procedures, triggers, and so on that are shipped with Pega software are fine; it is just the customizedversion of these objects which are not supported by Pega Cloud.
IMPORTANT: After the approach for the data migration has been defined, it must be reviewed by the Pega Cloud Migration Team. This review is very important, as that team will be responsible for executing this plan during the data migration and go live phase.
For details on the Database Gap Analysis, please see Assessing your on-premises database for migration.
You must also evaluate your current infrastructure at the operating system level. The infrastructure assessment must identify the following configurations and components currently supporting your Pega deployment:
- Operating system
- Application server
- Network topology
Your assessment must also determine whether there are custom system objects which will not function properly in a Pega Cloud environment. Since the file system in a cloud environment is transient and may cause data loss if relied upon, any Pega application functionality that writes files or other information to disk must be updated to modern strategies that support standard cloud operations.
In addition, since there is no command-line access in a Pega Cloud environment, for security reasons, you will need to update these types of customizations to use Pega application functionality:
- Custom shell scripts
- Cron jobs
- Custom schedulers
- Custom scripts to move files
- Configuration file customizations
For details on the Infrastructure Assessment, please see Assessing your infrastructure.