We upgraded a locally hosted Dev environment to v16 back in January, and have since decided to delay upgrading Test and Live for several more months. This data has of course become stale. I asked support if, given the underdone state of v16, they had contemplated creating code to push v15 data to v16, even partially, but it appears that they have not.
If someone has ever done a table-by-table copy from Live to Test or the like, I bet it could be altered to fit this situation. I'm imagining a "move just these orders from Live to Test" sort of situation...
A crazy idea, I know, but has anyone tried something like this? It would be a lot of code (seasons, perfs, transactions, constituents, etc..), but it seems tantalizingly possible, if very time consuming. ;-)
I haven't, but I swear I saw this done during v12-14 or 14-15 on a locally hosted.
also, at what point is it worth trying to figure this out vs blowing up your dev completely and doing a new install?
We started our Dev VM with a v15 install which we upgraded to v16, which was painful. We wouldn't have to start from a bare VM this time, but I see no way to avoid the v15 install -> v16 upgrade journey again.
Kathleen Smith said:I swear I saw this done during v12-14 or 14-15 on a locally hosted.
I have the nagging feeling that this sort of thing has been done before, too. Long ago and on a smaller scale perhaps...
This is what we did: wiped the Dev environment, reinstalled a v15 instance, and then re-upgraded.
Trying to add just this or that sounds insanely painful: orders will include reference to new customer records, who will have various attributes that require conversion to v16, for instance.
Gawain Lavers said:This is what we did: wiped the Dev environment, reinstalled a v15 instance, and then re-upgraded.
Yep. Trying to avoid.
Gawain Lavers said:Trying to add just this or that sounds insanely painful:
Agreed. And yet...