Help Wanted: Document migration process from an Omnibus install to a normal one

[matterdoc]

Context

The Mattermost Product Documentation doesn't currently include details on how to migrate from an Omnibus Mattermost deployment to a regular Mattermost deployment.

Documentation request

Document how to migrate from an Omnibus Mattermost deployment to a regular Mattermost deployment based on the details included below.

Migrating from an Omnibus Mattermost deployment to a regular deployment involves several steps, as you would need to set up a standalone Mattermost server and migrate your data. Below is a high-level outline of the steps:

1. Prepare Your New Environment

• Provision a new server that meets the hardware and software requirements for a standalone Mattermost server.
• Install the prerequisites such as PostgreSQL database, storage, and other dependencies.

2. Back up Your Current Deployment

• Backup your data: Ensure you have a complete backup of your current Omnibus deployment. The documentation for the process is here This includes:
  • Database
  • Files and other assets

Important note: Omnibus uses the configuration in the database feature, so your server configuration won't be in the config.json file, and your data directory would be the same that you have specified in the /etc/mattermost/mmomni.yml file, under the key data_directory

3. Set Up the Standalone Mattermost Server

• Install Mattermost: Follow the Mattermost deployment instructions for your operating system. See the deployment documentation for details.

4. Configure and Restore Data

• Database: Import your database backup into the new database server.
• Configuration: Configure the config.json file initially to point to your new database.
  Since your configuration is stored in the database, after you import the database, Mattermost should pull its configuration from there.
• Files: Restore the files from the data directory mentioned in your /etc/mattermost/mmomni.yml file to the new data directory.

5. Testing

• Test your new setup: Verify that the new Mattermost server is functioning correctly. Ensure that all data and configurations are correct and users are able to log in and access their information.
  
6. Go Live
• Switch DNS/Load Balancer: If applicable, update any DNS records or load balancers to point to your new Mattermost server.
• Inform Users: Notify your users of the migration and any potential downtime.