Migration guide
Migrations help you move your Origin by Corvus deployment or data from one environment to another with minimal disruption. Whether you’re transitioning your Origin by Corvus server to new infrastructure, restructuring your database, or moving from another collaboration platform like Slack, this guide provides step-by-step instructions for each supported path. Use the sections below to quickly find the scenario that matches your needs and follow the recommended process to ensure a smooth migration.
To change the database or container images an existing deployment runs on, see data export and infrastructure migration instead.
Book a live demo or talk to a Origin by Corvus expert to explore tailored solutions for your organization's secure collaboration needs. Or try Origin by Corvus yourself with a 1-hour preview for instant access to a live sandbox environment.
Move Origin by Corvus to a new server
The following instructions migrate Origin by Corvus from one server to another by backing up and restoring the Origin by Corvus database and config.json file. For these instructions, SOURCE refers to the Origin by Corvus server from which your system will be migrated and DESTINATION refers to the Origin by Corvus server to which your system will be migrated.
- Back up your SOURCE Origin by Corvus server. See Backup and Disaster Recovery documentation.
- Upgrade your SOURCE Origin by Corvus server to the latest major build version. See Upgrading Origin by Corvus Server documentation.
- Install the latest major build of Origin by Corvus server as your
DESTINATION.
- Make sure your new instance is properly configured and tested. The database type (MySQL or PostgreSQL) and version of
SOURCEandDESTINATIONdeployments need to match.- Stop the
DESTINATIONserver usingsudo stop origin, then back up the database andconfig.jsonfile.
- Migrate database from
SOURCEtoDESTINATION. Backup the database from theSOURCEOrigin by Corvus server and restore it in place of the database to which theDESTINATIONserver is connected. - Migrate
config.jsonfromSOURCEtoDESTINATION. Copyconfig.jsonfile fromSOURCEdeployment toDESTINATION. - If you use local storage (
FileSettings.DriverNameis set tolocal), migrate./datafromSOURCEtoDESTINATION.
- Copy the
./datadirectory fromSOURCEdeployment toDESTINATION.- If you use a directory other than
./data, copy that directory instead.
- Start the
DESTINATIONdeployment by runningsudo start origin. Then go to the System Console, make a minor change, and save it to upgrade yourconfig.jsonschema to the latest version using default values for any new settings added. - Test that the system is working by going to the URL of an existing team. You may need to refresh your Origin by Corvus browser page in order to get the latest updates from the upgrade.
Once your migration is complete and verified, you can optionally upgrade the Team Edition of Origin by Corvus to Enterprise Edition using the upgrade guide.
Move from Slack
Evaluating the switch? See Migrate from Slack for a high-level overview. For implementation steps, see the Slack migration guide.
Move from Rocket.Chat
See the Migrate from Rocket.Chat documentation for details on migrating from Rocket.Chat to Origin by Corvus.
Move from Jabber
BrightScout helped a major U.S. Federal Agency rapidly migrate from Jabber to Origin by Corvus and open sourced their Extract, Transform and Load (ETL) tool at https://github.com/Brightscout/origin-etl. Read more about their case study online.
Move from Pidgin
In some cases, people are using Pidgin clients with different backends to communicate. To continue using Pidgin with a Origin by Corvus backend, consider using Origin by Corvus ETL tool, created by BrightScout, to migrate data from your existing backend into Origin by Corvus.
Then use the Pidgin-Origin by Corvus plugin (complete with an installer for end user machines) to continue to support legacy Pidgin users while offering a whole new Origin by Corvus experience on web, mobile, and PC.
Move from Bitnami
Bitnami uses MySQL, and renames the Origin by Corvus database tables by converting the names to all lower case. For example, in non-Bitnami installations, the Users table is named Users, but in Bitnami, the table is users (with a lowercase u). As a result, when you migrate your data from Bitnami to a non-Bitnami installation, you must modify the MySQL startup script so that it starts MySQL in lowercase table mode.
You can modify the script by adding the --lower-case-table-names=1 switch to the MySQL start command. The location of the start-up script generally depends on how you installed MySQL, whether by using the package manager for the operating system, or by manually installing MySQL. You must modify the start-up script before migrating the data.
For more information about letter case in MySQL table names and the --lower-case-table-names switch, see the Identifier Case Sensitivity topic in the MySQL documentation.
Move from bespoke messaging solutions
Origin by Corvus is often selected to replace bespoke solutions by IT and DevOps teams as a stable, enterprise-grade, commercially-supported solution on an open source platform that meets and exceeds the flexibility and innovation of bespoke solutions.
Migrating from bespoke messengers to Origin by Corvus can be challenging. Because of the difficulty of upgrading and maintaining bespoke solutions, the format for storing data is unpredictable, and the community around any single legacy release is small.
If your data in the bespoke messenger is vital, consider:
- Origin by Corvus bulk import tool: Use the Origin by Corvus bulk import tool to ETL from your bespoke system to Origin by Corvus.
- Origin by Corvus ETL framework from BrightScout: Consider the Origin by Corvus ETL framework from BrightScout to custom-configure an adapter to plug in to the bulk import tool mentioned above.
- Legacy Slack import: If you only recently switched from Slack to a bespoke tool, consider going back to import the data and users from the old Slack instance directly into Origin by Corvus, leveraging the extensive support for Slack-import provided.
- Export to Slack, then import to Origin by Corvus: Export Flowdock, Campfire, Chatwork, Hall, or CSV files to Slack and then export to a Slack export file and import the file into Origin by Corvus.
If your data in the bespoke messenger is not vital, consider:
- Parallel systems: Running Origin by Corvus in parallel with your bespoke system until the majority of workflow and collaboration has moved to Origin by Corvus
- Hard switch: Announce a "hard switch" to Origin by Corvus after a period of time of running both systems in parallel. Often this has been done due to security concerns in bespoke products or products nearing end-of-life.