Some older applications have been incorporated into the Pega Platform, or into other applications.  Other applications require some type of remediation when migrating to Pega Cloud.  If your system includes any of the applications listed below that require remediation, add the necessary remediation for each application to your Migration Project Plan.

NOTE:  Beginning with Version 8.1 for Pega Platform, all Pega strategic applications which were built on that platform have version numbers that match the Pega Platform version (example:  “8.2”).  These applications include:

• Pega Customer Service
• Pega Sales Automation
• Pega Marketing / Customer Decision Hub (CDH)
• Vertical applications (“Pega Customer Service for Healthcare,” etc.)
• Other applications (Field Service, Warranty, etc.)

For version 7 and earlier, some Pega applications may have had different versioning patterns.  For these older applications, check the Application Definition record to find the version of each of your Pega applications.

Admin Studio (and System Management Application)

Admin Studio provides all functionality provided by the System Management Application (SMA), and has replaced it.  Admin Studio is included with every Pega Cloud deployment.    

Required action:  
No action required.  SMA functionality is available through Admin Studio.

Agile Studio (and Project Management Framework)

Agile Studio and Project Management Framework (PMF) are essentially the same application.  PMF is older and has been replaced by Agile Studio.  Agile Studio is included with every Pega Cloud deployment.

Required action:
Migrate your Agile Studio or PMF database to Pega Cloud.  The database used by PMF is the same as the database used by Agile Studio, however this is separate from the main Pega database and must be migrated separately.  

If you have customized any of the rules in Agile Studio or PMF, export those customized rules in a RAP, and import them into the Agile Studio node on Pega Cloud.  If you have not customized Agile Studio or PMF, but are using one of them “out-of-the-box,” this step is not necessary.   

Test Agile Studio on Pega Cloud with your migrated data.

Business Intelligence Exchange  

Business Intelligence Exchange (BIX) is available both on-prem, on client-managed cloud, and on Pega Cloud.  If you are licensed to run BIX on Pega Cloud, a separate node is set up to run batch processes, such as BIX, when your Pega Cloud instance is provisioned.  If you use the BIX CLI on-prem, you need to change the BIX rules to use the BIX agent.

BIX places the extract files into your Pega Cloud File Storage repository. You do not have direct access to the Pega Cloud File Storage repository.  Therefore, you can either get your BIX extract files from the Pega SFTP server, or the extract files can be sent to your SFTP site.

For more information, see:  Overview of BIX extractions in Pega Cloud environments.  This provides more information about extract files and how to get them from Pega Cloud.

Customer Decision Hub (and Pega Marketing)

Customer Decision Hub (CDH) and Pega Marketing are essentially the same application. Pega Marketing is older and has been replaced by CDH.

Required action:
CDH and the Pega Platform are migrated at the same time. This requires a four-phase migration approach, similar to the approach used when migrating the Pega Platform alone.  For more information, see:  Appendix:  Migrating Pega Marketing/CDH.

Decision Strategy Manager

Decision Strategy Manager (DSM) is no longer a separate application.  It has been incorporated into the base Pega Platform.

Required action:
No action required.  If you have DSM as a separate product you automatically receive that functionality after migrating to Pega Cloud.

Deployment Manager

Deployment Manager is included with every Pega Cloud deployment.

Required action:
Migrate your Deployment Manager database to Pega Cloud.  The Deployment Manager database is separate from the main Pega database and must be migrated separately.  

If you have customized any of the rules in Deployment Manager, export those customized rules in a RAP, and import them into Pega Cloud.  If you have not customized Deployment Manager, but are using it “out-of-the-box,” this step is not necessary.   

Order Management for Communications

Order Management for Communications is no longer a separate application.  It has been incorporated into Pega Customer Service.

Required action:  
No action required.  If you have Order Management for Communications as a separate product you receive that functionality with Pega Customer Service, or any of the industry-specific Customer Service applications.

Pega Card Customer Process Manager

Pega Card Customer Process Manager (CPM) (Financial Services) is no longer a separate application.  It has been incorporated into Pega Customer Service.

Required action:  
No action required.  If you have Pega Card CPM as a separate product, you receive that functionality with Pega Customer Service, or any of the industry-specific Customer Service applications.

Pega Chat and Pega Co-Browse

Pega Chat and Pega Co-Browse are available both on-prem and on Pega Cloud.  

If you are using Pega Chat or Pega Co-Browse without the Collaboration Services Cloud, reconfigure them to use the Collaboration Services Cloud.

If you are already using the Collaboration Services Cloud with your source Pega Solution, check that the configuration still works after migrating to Pega Cloud.

If you have recorded Pega Co-Browse sessions that you want to keep, migrate the Pega Co-Browse database to Pega Cloud.  The Pega Co-Browse database is separate from the main Pega database and must be migrated separately.  

Pega Customer Relationship Management

For Pega Customer Relationship Management (CRM) applications, including Pega Customer Service, Pega Customer Service for Healthcare, and Pega Customer Service for Insurance, see:  Pega CRM Update Guide 

Some product changes require user action before updating, to ensure a successful update.  Before updating any Pega CRM applications, review the important information about product changes for each release. For more information, see Crucial update information for Pega Customer Relationship Management.

Pega Predictive Diagnostic Cloud (and Autonomic Event Services)  

Pega Predictive Diagnostic Cloud (PDC) provides all the functionality provided by Autonomic Event Services (AES), and has replaced it.  PDC is included with every Pega Cloud deployment.  

Required action:
No action required.  Your Pega Cloud environment includes Pega PDC.

For more information about PDC, see:  Pega Predictive Diagnostic Cloud  

Pega Web Mashup (and Internet Application Composer)

Pega Web Mashup provides all the functionality provided by Internet Application Composer (IAC), and has replaced it.  Pega Web Mashup is included with every Pega Cloud deployment.

Required action:  
As part of your application migration, implement Pega Web Mashup to provide this functionality.   IAC is not supported on Pega Cloud.  

The mashup code must be regenerated if IAC was being used in 7.x  or older versions.  

For more information about Pega Web Mashup, see:

• Pega Web Mashup  -  This is part of the Senior System Architect mission on Pega Academy.  It includes a short video of the concept, how to generate the code, and non-production authentication.
• Pega Web Mashups for embedding traditional UI in external web pages - This is more extensive than the Pega Academy mission, it includes:
  • Creating a mashup
  • Mashup attributes
  • Mashup JavaScript page actions
  • Mashup action objects
  • Best practices for using mashups
  • Troubleshooting mashup issues
• Migrating existing mashups  - Migrating mashups to the latest release

For more information about modernizing IAC, see the Internet Application Composer (IAC) section of the Pega Modernization Implementation Guide.

Spend Management

Spend Management (Life Sciences) is deprecated.  There is no migration path.

Required action:  
Review your application to identify any assets that can be reused to leverage the latest capabilities of the Pega Platform.

Additional Documentation

Pega recommends that you review all documents for each interim release of all Pega applications in the stack (for example, Sales Automation for Insurance, Sales Automation, Foundation for Insurance).   You may find the following document types helpful:

Release notes	Provides an overview of changes in a release, which is helpful in determining new functionality, integration, UI changes, deprecated or withdrawn rules, etc. Release notes are available on docs.pega.com.
Update guides (most available starting with 7.22)	Defines steps to be conducted from release to release, as well as pre- and post-update steps
Implementation guides	Provides insight into new features/capabilities introduced into each release.