Best Practices for refreshing our eBS Dev to still work w/G-Invoicing QA current state?

Hi All,

We have an upcoming initiative to rebuild our eBS "G" development environment where we've been doing all our eBS G-Invoicing testing with the G-Invoicing QA environment. The new dev environment will be from a new, recent Prod clone.

This will be the first time standing up a new eBS environment integrated with the existing G-Invoicing-QA state. I'm a bit concerned about the impacts the change will have to our G-Invoicing integration processes, since we'll be missing a lot of test data from our prior eBS Dev, yet that data will still be on the G-Invoicing-QA side. Hopefully it won't be too big of an issue though.