Migrate projects from local to database mode

If you are using Syndeia in local mode for a project and wish to migrate Syndeia information for the project to the database and then continue to use Syndeia in database mode for the project, follow the steps below.

If the SysML project was using Syndeia 3.0, upgrade the project to the latest version of Syndeia using the local mode.
Create a backup copy of the project after the upgrade so that you have a version of the project with Syndeia information saved in the local mode.
Make a list of the names and URLs of all repositories being used by your project. You will need this in later steps.
Open the project and configure Syndeia to use database mode, before launching the Dashboard. Make sure that your database account has the privilege to create new keyspaces in Cassandra and write privileges to the syndeia_general keyspace if it exists already.
Launch the Settings window (right click on any element, select Syndeia > Settings) if not already open and check that the setting "Auto-load local connections" is true.
Now launch the Syndeia Dashboard. Syndeia will initialize a new keyspace for the project in the database, and it will detect that the SysML model has local connections which will be loaded.
Syndeia will also load the repositories from the database. If the database contains no repositories, or if it contains repositories whose names do not match the ones being used by your project (step 3 above), then go ahead and add new repositories with the same names and URLs as you had noted earlier.
Close the Syndeia Dashboard. Syndeia will push the repositories used by your project and the existing connections to the database.
Save and close the project.
Open the project, launch the Dashboard, and check the following:
1. All of your repositories should now be listed in the Repository Manager tab of the Dashboard.
2. All of your connections should now be listed if you go to the Connection Manager tab of the Dashboard and press "Get All".