Need tool/ability to do mass migration of cards to other SFDC IDs -this will continue to be a migrat

Impact: Reparenting, 10 accounts, 4 hrs per week; 10K accounts reparenting in Aug!!

Regarding reparenting relationships to a different account, we did testing in our dev environment to understand the current behavior and did technical analysis on what is possible with the way MDA is instrumented. Based on all this work, the following is one of the possible solutions. Let me know what you all think and we could make the required product changes based on that.

1. Reparenting account on SFDC data:[list]
2. Salesforce has introduced the ability to allow changing the parent of a detail record. 
3. We will have to push a package upgrade to enable reparenting on Relationships, Call to Action and other detail objects. 
4. This is a trivial change from dev effort perspective but will need to go thru to regression cycle, so will be ideal for us include this change as part of the next Gainsight Release.

Reparenting account on MDA data:

• GS Connect will update the new Account ID on the Relationship Object in MDA and no additional effort is required
• For other data like Scorecard 2.0 and Timeline, we can use a backend script/job to update the data to point to the new Account / Company iD
• We do not store Account ID on the Scorecard tables in Relationship Scorecard, so no additional effort required if they are using Relationship Scorecard

While updating account will not be possible from the UI (which is also what Cisco asked for), if there was a file with the Old Account IDs and New Account IDs, we could then use that to update SFDC relationship and CTA records from the backend and then take TechOps help to run scripts and update Timeline and Scorecard data in MDA. 

While this is still a manual process, it is a fixed bulk process that will take the same amount of time to re-parent 100 records or 10,000 records. [/list]Summary: We will have to make an SFDC release to allow reparenting and then this upgrade should be pushed to Cisco. There will still be a manual effort to - 

1. Get a file with Old Account IDs and New Account IDs
2. Manually update the data in multiple SFDC objects via data loader or other similar tools. 
3. Take TechOps help to update the timeline and scorecard data to point to the new Account ID. 

This is not the final solution and only a temporary workaround for Aug timelines and we will continue to evolve and improve the re-parenting approach to remove all manual effort.

Murali/Issac to confirm which release we should create the patch for? e.g. Which release Cisco will land on prior to freeze. Our hope is that you can make it to 5.14 as it puts Cisco in an ideal position of being able to take up Encryption on Bionic S3 Fetch and minimizes risks in case we need to patch anything over the summer.

When you get out of the freeze in Sept, we will plan either another patch for the version you upgrade to, or make this function broadly available in the latest release at that time. 

Feature delivered. Even with the delivery and the current process in place, we will continue to optimize this for weekly/daily changes.