You can migrate existing My Edited Content and Workflow Lists stored in MongoDB or the In-Memory replacement to SQL persistence.

For migrating the data, you must make sure to stop and reconfigure all Workflow Server, User Changes Application, and Studio Server instances before restarting them again.

To migrate data from MongoDB, keep the configuration for MongoDB as before.

Alternatively, to migrate data from the In-Memory replacement's persistence file, you should keep using the Spring profile in-memory to start Workflow Server and Studio Server applications as documented in Section 4.2.4.10, “In-Memory Replacement for MongoDB-Based Editorial Services (Deprecated)”. However, you have to set additional configuration properties to override values specified in the Spring profile:

In addition to that, you have to also start the User Changes Application which was not started when using the In-Memory replacement.

For migrating data from either MongoDB or the In-Memory replacement, make sure that for the Workflow Server, User Changes Application, and Studio Server you

Data migration is performed by the Studio Server immediately after first start. If present, additional Studio Server instances must be configured to not also start the migration by setting their property caplist.migration.on-startup=false.

The Studio Server will migrate data in the background. Editors can use Studio immediately, but migrated data may appear with a short delay in My Edited Content and Workflow Lists. According to our tests, the migration of typical data sets just takes a few seconds. It may take slightly longer if My Edited Content lists contain a very high number of content items in total. For example, with 1 million content items in total in different lists of My Edited Content, the migration took around 10 minutes in our tests. Of course, the time needed for the migration may differ for your production setup.

Studio Server will log an INFO message containing the string "Completed CapList data migration", after the data migration has finished successfully. Afterward, you may reconfigure applications to not connect to MongoDB or not use the In-Memory replacement anymore. Before doing that, please check that you do not need to migrate data of other features, or still need MongoDB for features like CoreMedia Elastic Social or Analytics Connectors.

All configuration options for CapList data migration can be found in Section 3.8.4, “Data Migration Properties” in Deployment Manual.