Blueprint Developer Manual / Version 2506.0
Table Of ContentsBefore starting the migration, make sure that no Projects or To-dos are written anymore to the Elastic Core persistence. Also consider other possibly running instances of Studio Server.
When the migration is enabled, you can use the actuator at actuator/projectmigration to get a
report of the migration and to trigger the execution of the migration.
Migration can be executed repeatedly. For example when a Project has been migrated with issues, you can adjust the project in the Elastic source and execute the migration again which will overwrite all previously migrated properties of the project.
Only Projects and To-dos that have not been migrated successfully will be considered for repeated executions. The state of the migration is persisted in the SQL database, so you can also restart the application in between the migration executions (or to trigger another execution of the migration alternatively to the actuator).
The actuator provides the following endpoints:
GET actuator/projectmigration: Get a report of the migration state.GET actuator/projectmigration/SOURCE_ID: Get a report of the migration state for the given SOURCE_ID with more details, where SOURCE_ID is an id of a Project or To-do in the Elastic source.POST actuator/projectmigration: (Re-)Execute the migration.DELETE actuator/projectmigration: Clear migration state in the database (Be careful: Without this data the connection between the old and already migrated data is lost and a re-execution of the migration would create another copy of the data.)
