Migrating Channels from Kolibri Studio v2023.09.27 to v2025.05.05

Support Studio
1

Dear Learning Equality Support Team,

I hope this message finds you well. I am reaching out to request your assistance in migrating all channels and associated data from an older version of Kolibri Studio (v2023.09.27) to the latest version (v2025.05.05). The older instance is installed on Ubuntu Server 22.04, while the new version is running on both Ubuntu Server 22.04 and Ubuntu Server 24.04.
Kolibri Studio in both environments is accessed via the server’s IP address (no custom domain). The current content storage on the older instance is approximately 101 GB, which includes channels, resources, metadata, and user-generated content.
We would like to ensure that this migration process:

  • Preserves all existing channels and content
  • Maintains metadata and channel structures
  • Retains any user-created resources or modifications

We kindly request your support and guidance on:

  • The appropriate steps to export and back up all data from the v2023.09.27 instance
  • The recommended process for importing and restoring it into the v2025.05.05 environment
  • Any tools, commands, or precautions we should take to ensure data integrity and version compatibility

If needed, we are happy to provide any additional information or technical details to assist your team.
Thank you for your continued support and for your commitment to equitable, offline-first education solutions.

Best Regards;
Ali Abdulkarim Ali

2

Hello @Abdulkarim_Ali_Patri,

Thank you for your interest in Kolibri Studio. We do not provide direct support for running deployments of Kolibri Studio, because we offer a hosted version, Kolibri Studio’s codebase is configured solely for development purposes, and it isn’t meant for offline deployments at this time. In contrast, our other software Kolibri, for which we provide implementation support, is an offline-first solution.

Since Kolibri Studio’s codebase is configured for development, it does not have any migration tooling suitable for this. Your best approach is a “backup and restore” type process-- copying all files to the new instance, and producing a SQL dump of the database in which you can restore on the new instance.

Regards,
Blaine