Posted: 12 Apr 2015 20:11 EDT Last activity: 26 Aug 2016 14:01 EDT
Migrate Legacy data to be compatible with the new PRPC environment and process
Hello , We had a legacy .Net application interacting with SQL DB for creating general escalation tickets. As part of enhancement sometime back , we built an upgraded application in Pega with Oracle DB but with enhanced process flows and in compliance with Pega schemas and data structures.
Everything seems stable niow with the new application , but its high time to perform migration of the Legacy data to the new application. (cannot have business use two appliciations).The challenges we are running into are
a) The tables schemas/design are considerably different in the Legacy DB especially the case table is very different from pega specific pc_work, pc_history_work etc. tables
b) The process has been upgraded in the new application with some of the data fields merged and new fields added
How can we plan a smooth data migration , which will allow capabilities to search as well as reopening cases on the old data , but with the new process ?
Any experience with such scenarios , your inputs are highly appreciated !
Is there a Pega recommended data migration approach documented ? My organisation is embarking on BPMN based business transformation project using Pega. I would like to get an insight into the best practices and approach for a successful data migration involving Pega data structures.