When you organize it like that, then I think the easiest thing to do is this:
Back up all databases. (You shouldn’t actually need these backups. But, just… you know.)
Transition to 1 DB on Enterprise Edition. To use project move, all your existing instances need to be at the same SonarQube version. They’re all already at 7.9.3, so just take advantage of that. Do the in-place version upgrade on all servers and consolidate.
Now that you have 1 DB, do the version upgrade. You’ve only got one instance to upgrade so you’ve already saved time and effort. (Woo hoo!)
Now do the move to Docker. You’re pointing to the same DB whether you’re running on Docker or as a service so getting this far before you make the Docker move has saved you the uncertainty of handling multiple changes/variables at once.
HTH,
Ann
P.S. I guess you’re already aware that you’ll need to work with the folks on the sales side to handle the temp licenses you’ll need for your Project Move step. They’ll be happy to help you out.
Thanks for your reply. Need a clarification though.
Like I mentioned, we already have SQ instances running as docker containers. To upgrade SQ to EE to merge the databases into one (I understand a temp license should be fine here) do I need to use the enterprise zip in the docker image or is the CE version with a valid EE license enough to get going with the Project Move functionality?