Syndeia 3.2 3 provides the following two migration paths from Syndeia 3.2.
Syndeia
...
Users can upgrade Syndeia data created using Syndeia 3.1 to work with Syndeia 3.2. This Syndeia data primarily includes connections stored in SysML model and repositories stored in .syndeia folder.
Syndeia 3.2 (local / SysML store) → Syndea 3.2 (Syndeia Cloud)
Users working with Syndeia 3.2 in local mode can also migrate data to Syndeia Cloud and start working in cloud mode.
...
Cloud 3.2 → Syndeia Cloud 3.3
If you are using Syndeia 3.2 with Syndeia Cloud, then all of your Syndeia data is persisted on the Syndeia Cloud server. Your Syndeia admin will be required to set up a new instance of Syndeia Cloud 3.3 and then follow the migration process described on Syndeia Cloud 3.2 -> 3.3 Migration to migrate data from Syndeia Cloud 3.2 to Syndeia Cloud 3.3.
Syndeia 3.2 Local store → Syndeia 3.3 Local store
If you are using Syndeia 3.2 with a local store, then all your Syndeia data is persisted locally on your machine and SysML models. Follow the steps on 3.2 Local -> 3.3 Local to migrate from Syndeia 3.2 local store to Syndea 3.3 local store. You will have to follow this process for each SysML model you are using with Syndeia 3.2.
Syndeia 3.3 Local store → Syndeia Cloud 3.3
If you start using Syndeia 3.3 with a local store and would like to migrate to Syndeia Cloud 3.3, follow the steps on 3.3 Local -> 3.3 Cloud to migrate your data to Syndeia Cloud 3.3.
If you were using Syndeia 3.2 with a local store and would like to start using Syndeia Cloud with Syndeia 3.3 release, then you need to first migrate from Syndeia 3.2 local store to Syndeia 3.3 local store (see above) before upgrading to Syndeia Cloud 3.3
| Child pages (Children Display) |
|---|
| Child pages (Children Display) |
|---|