Guidance on Implementing Common Data Model (CDM) During Customer Service Migration to Constellation

General
,
1

Hello Everyone,

We are currently planning to migrate our Pega Customer Service application from the Traditional (UI-Kit) architecture to Constellation.

Our existing Customer Service application was built on the Traditional (UI-Kit) architecture and does not use the Common Data Model (CDM). As part of our migration to Constellation, we’ve found that CDM is a key component of the target architecture.

I’ve reviewed the Constellation migration documentation along with several Pega Community articles describing different CDM implementation strategies, but it remains unclear which approach is appropriate for our situation. An existing, already-built Customer Service application that needs to retrofit CDM.

Could anyone please provide guidance on the following?

  • What is the recommended approach for introducing CDM into an existing application?
  • How should our existing custom data classes be mapped or migrated to their CDM equivalents?
  • Are there any best practices or reference documentation for this scenario?

Environment:

  • Pega Customer Service (Constellation) '25.1.3
  • Pega Common '25.1.2
2

Hi Sahana. I’ll be reaching out to you via email to discuss in more detail. For other readers, we’ll provide answers to the questions in this post once we have discussed further. - Thanks.