Backup your 2.0.2 database. Once you have done this run the upgrade scripts from "Upgradev2-1.sql" to "Upgradev4-1.sql" against the database. Attached the database to your Gemini 4.1 instance. Delete any projects that you do not wish to keep in Gemini 4.1.

Hi,

Thank you for your response. Another detail I forgot to mention, once I migrate the DB I don't want to lose the existent projects in the instance of Gemini 4.1.

What would be the best solution to add them to the migrated DB?

Do you want to import a few projects from 2.0.2 into a 4.1 Instance that already has projects that you wish to keep?

Yes that's exactly what I'm want to accomplish.

You can upgrade the database and then use the data import utility to import the projects you wish to import into your current 4.1 instance.

I'm a little bit confused here with the online documentation. It seems to place 4.2 as the hinge-point here http://community.geminiplatform.com/docs/all/page/15/upgrading-2-0-x-to-4-2/

Do I have to upgrade from 2.0 to 4.2 (scripts and web files) as mentionned in the doc or do I have to run all the upgrade scripts from "Upgradev2-1.sql" to "Upgradev4-1.sql" against the DB?