Hi Ann,
Thank you for your answers. See I did it in parallel (i actually described the strategy in my earlier post, but its super simple) - I restored 6x to another new server (db and app servers both restored on corresponding pair of new servers), then upgraded the new ones to 7x. At that point 7x had the same data. But, as time went by, and adoption was slow, still is, old projects were using 6x for several weeks now, and accumulated data not in 7x, while 7x was used by pilots and new projects, which also accumulated data in 7x that is not in 6x. We understood the risk of this gap happening and my manager offered that as long as we can extract the data somehow, we should be fine. Now SQL based extract is not recommended or supported (that would have been my first option, I used this approach on a couple of other projects upgrading other software - just a report that had flattened data for us to play with if need arises), and now as I’m staring at various API responses I am really in over my head as to how to join them into something simple we could use. I understand that the underlying datamodel is tremendously complex and reflexts power and flexibility and extensibility of Sonarqube which I genuinely recognize and respect, but my goal is so humble in comparison - I just need to know that com.mycompany.MyClass had issues A, B, C found on MM/dd/yy - and the A,B,C to be human readable (long description or short or even commonly recognized code I could Google ). Do you have any thoughts on how I could do that - for my overlap period? Also a note that since we do not use SQ properly yet, we are unlikely to be closing issues, overriding priorities, manually ignoring anything and such - data is as pristine as it can be. Thanks again for your help!