For the rollout, the existing memories need to be migrated from OpenTM2 via TMX to t5Memory.

For this we need to implement an automated process based on our api:

• implement that all as CLI tool which needs as argument the URL to the new t5memory instance
  • Since the script should be able to be called multiple times, the config must be checked if the given URL does already exist
• loop over each instance → another level of implementation - done on  the server
• create a new t5memory URL in the config of URLs, pointing to the new prod server
• in once instance: loop over all existing OpenTM2 language resources
• export each TM as TMX from, save it into a folder in /data/
• re-import each TMX into t5memory, using the HttpApi directly with a mocked language resource instance since the underlying service resource will point to a wrong URL (the OpenTM2 one)
• Update the filename in specificData if it has changed in t5memory
• update the resourceId to the entry of the new t5memory → this should be done in the end, not in between in the case of an error
• after looping over all resources, remove the OpenTM2 URL and update the resourceIds due the changed URL array

change GUI appearances of the name "OpenTM2" in translate5 to t5memory.