Migration need?
Is there a need to migrate? Traditional Architecture is not being deprecated and with things like Innovating with Pega Constellation: Blending Traditional UI with Modern Architecture you can still leverage existing landscape with your new Constellation applications.
- See also https://docs.pega.com/bundle/platform/page/platform/user-experience/adoption-strategies-blended.html
Recommended approach when migrating
To help understand why Application Signature Tool followed by Blueprint Estimator would be the recommendation you need to understand what the Modernization Assistant is.
We had an Expert Circle webinar on this a year ago:
- Blog: https://community.pega.com/blog/mastering-pega-application-modernization-constellation-ui%26nbsp%3B
- Webinar: Transform Your Applications: Master the Constellation Modernization Assistant Tool | Pega
The Modernization Assistant will not do the migration for you, a lot of it has to be manually done AND it assumes a 1-to-1 mapping of assets. If you’ve done any Constellation previously, you’d know it isn’t a 1-to-1.
Application Signature Tool and Blueprint, preserves what it can BUT also gives you the chance to reimagine your application in the modern AI driven world we now live. By using Blueprint, you not only reimagine but you import that into Pega, so it will build the rules to support your Blueprint - giving you a huge headstart on the modernization effort.