Preserve/replicate configuration for MDA after Salesforce sandbox instance is refreshed

Adding on to this...had a similar situation happen when we spun up a developer sandbox.  Usage Measures did not display in  Usage Configuration yet when I tried to create them it said they already existed.

From support: 
"when you spin off another instance, it will carry over all the custom fields that are setup on the backend in SFDC. We don't, by nature auto map those for you which is what the feature request would be in this case."

Hi Brijesh,
We are currently developing functionality called Cross Org migration(Available in beta), where the next set of steps is to help you replicate MDA objects and rules and reports associated to it. I will update this thread with release information once we are close to it.

So if we refresh our sandbox (deleting our Gainsight data) we could copy production rules/reports back into the sandbox at a later date? Is that what this functionality would do?

Hi All, 
With Gainsight 5.5/Winter Release, users will have ability to migrate custom MDA collections/object along with ability to migrate Reports and Rules on them.
However on Rules front we have following limitations, we only support following actions - Create CTA, Set Score(1.0), Load to Customers, Load to Usage, Load to SFDC and Load to Relationships.
We are working on supporting more actions for Rules migration.

Thought this might help those following this conversation about the Migration Tool.

Read more here: "Migrating Schema and Assets from a Source Org to a Target Org"

Oh, and be sure to read up on Bionic Rules to learn how you to move your MDA data between SF Orgs by Exporting Data to an S3 Bucket, "Export to S3 from Bionic Rules".

MDA Migration does not work properly if field has lookup set.

@Praneet - is there any new enhancements to cross migration functionality

@Praneet - this is really causing issues for us as we do frequent refreshes on sandbox environment

We have a partial solution now vetted for this.  First, you must know your SFDC Org ID prior to refresh and your SFDC Org ID post refresh.  After the refresh, you need to authorize MDA for the new SFDC org.  Then submit a ticket to Gainsight Support and we can repoint your existing Sandbox MDA to your refreshed org.   LMA access is desired so we can verify success for this.
Important note:  The data in MDA will not be refreshed from Production - it will be the same data that was in your Sandbox.  If you made any other schema or MDA changes in your MDA Production, you would need to migrate these. 

We are planning to address a full solution sometime in the second half of this year.

The self sandbox management is a part of our roadmap. We are working to bring in sandbox managment to the admins