How to migrate Traditional Pega SA application to Constellation Incremental approach?

We have the Pega traditional applicatio in-place. There is a need to migrate the sales automation traditional to Constellation application incrementally.

Considering the user should access the exisitng traditional casetypes with a increamental roll out of each casetypes (ORG,ACC,CON,Renewal,Endorsement)

What is the best approach to move ?

Sorry you didn’t get a reply @MatheswaranRavi — have you seen the Constellation Adoption Strategies Playbook? If not, I’d suggest perusing that for an initial overview.

The best approach is Pega’s Blended UI, or coexistence, strategy: your current traditional application keeps running, while selected processes are rebuilt to use new Constellation features inside that same application. Use the Constellation Modernization Assistant to check readiness, then migrate case types one at a time in priority order — for example ORG, ACC, CON, Renewal, then Endorsement — moving business-critical case types first and modernizing the rest afterward. Test and launch each case type before starting the next, so users always have full access to whatever hasn’t moved yet, until the entire application runs on Constellation.

Thanks everyone for the suggestions and related articles. We were able to set up the application architecture to align with the C11N design by understanding the different approaches.