mirror of
https://github.com/mattermost/mattermost.git
synced 2026-09-21 05:54:10 +08:00
Eva SarafianouandCursor
f3849f83de
* docs: resolve cross-file anchor mismatches from RST-to-MDX migration
The Sphinx-to-Docusaurus migration converted `:ref:`/`{ref}` links using
naive text-slugification, so anchors that pointed to headings in a
different file (e.g. release-summary tables linking into their
respective changelog pages) were emitted as same-page fragments and
silently resolved to nothing.
Built a label registry from the original Sphinx `.. _label:` / `(label)=`
targets to recover the true source file for each cross-reference, then
rewrote the affected links to point at the correct file + heading
anchor. Fixes 282 broken cross-file anchors, primarily in the mobile/
desktop/server release-summary pages, plus assorted same-page anchor
mismatches caught by re-auditing after the prior admonition/anchor fix.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: manually resolve remaining anchor mismatches after cross-file audit
Hand-verified fixes for anchors that fuzzy-matching alone couldn't
safely resolve (confirmed against actual heading text/context, and in a
few cases against the original RST source, before applying):
- Typos and dropped words carried over from the original Sphinx docs
(e.g. "bot-acocunts", "auto-follow-all-new-channel-threads" ->
"follow-all-new-channel-threads").
- Sphinx auto-generated duplicate-heading IDs (#id1/#id3/#id4) resolved
to their real target headings.
- Numbered-step TOC links in enterprise-roll-out-checklist.mdx that
dropped the leading "N. " used in the actual heading slugs.
- Push-notification docs pointing at the wrong file entirely
(environment-configuration-settings instead of
push-notification-server-configuration-settings).
- SAML "saml-enterprise" label resolved to its true cross-file target
(authentication-configuration-settings#saml-2-0), recovered from the
original RST label definition that the automated registry missed
because it sat after an RST transition marker.
- sso-saml-technical references converted from broken same-page/
malformed-path anchors to correct page links.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: fix SAML 2.0 anchor slug (saml-2-0 -> saml-20)
github-slugger strips periods rather than hyphenating them, so "SAML
2.0" slugifies to saml-20, not saml-2-0 as previously fixed.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: fix broken path links found during docs/main migration cleanup
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: convert div.tab blocks to Docusaurus Tabs/TabItem components
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: restore missing Kubernetes deployment architecture diagrams
The RST-to-MDX migration never copied over the AWS/Azure/Oracle
architecture diagrams referenced by the deployment-architecture-at-scale
page, leaving broken images in each Tabs/TabItem.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: fix 7 anchor mismatches from the fragment/heading audit
Covers three root causes from the anchor mismatch breakdown:
- Fragment repeated the target page's own title instead of a real
heading, so the link is simplified to point at the bare page.
- Heading exists verbatim but lives on a sibling settings page
(experimental-configuration-settings, push-notification-server-
configuration-settings) rather than environment-configuration-settings.
- A page path was mistakenly pasted into a same-page #fragment instead
of being used as a real cross-page link.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: fix 8 anchor slugs that were close but didn't match the real heading
Repoints links whose fragment was a plausible guess (typo, reworded
heading, or wrong section) at the actual auto-generated slug of the
target heading, confirmed by inspecting each target page directly.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: merge split Tabs blocks so tabs render horizontally
The div.tab conversion script split some sibling tab groups into
separate single-item Tabs blocks whenever a stray blockquote marker
sat between them, causing them to render stacked instead of as one
horizontal tab bar. Merges the MySQL/PostgreSQL and Team/Enterprise
Edition tab groups back into single Tabs blocks.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: remove Azure tab and restore Kubernetes deploy content
The Mattermost Operator, Azure, and Oracle platform tabs on the
Kubernetes deployment guide were split across two separate Tabs
blocks (rendering stacked instead of as one tab bar) and all three
tab bodies were empty because the migration never flattened the
original RST include directives. Removes the unsupported Azure tab
and restores the Mattermost Operator and Oracle content from the
pre-migration RST sources as a single merged Tabs block.
Co-authored-by: Cursor <cursoragent@cursor.com>
* addresscoderabbitreview
* docs: unify Linux/Kubernetes/Containers deploy pages and fix FIPS/STIG placement
Kubernetes and Containers duplicated full install content across a top-level
page (Tabs) and orphaned sidebar subpages that nothing linked to. Reworked
both to follow the Linux page's pattern: shared content on the landing page,
platform-specific instructions live once in their own subpage.
Also removed configure-fips-at-install-time.mdx, which claimed FIPS is
available for native Linux installs — FIPS/STIG in Mattermost is a container
image property (Chainguard-based build), not available outside Docker/
Kubernetes. Consolidated all FIPS/STIG references onto
containers/fips-stig.mdx and pointed the Mattermost Operator subpage (not
Oracle OKE, which doesn't expose image selection) at it.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: fix review findings — image alt text, Important callout markup, typo
- Replace generic alt="image" on scaling diagrams with descriptive text
identifying cloud provider and user scale.
- Convert raw div.important markup in deploy-containers.mdx to the
repo's <Important> component, matching usage elsewhere in the file.
- Fix "Matermost" typo in manage-your-display-options.mdx.
Co-authored-by: Cursor <cursoragent@cursor.com>
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
378 lines
18 KiB
Plaintext
378 lines
18 KiB
Plaintext
---
|
||
title: "Mattermost workspace migration"
|
||
---
|
||
This document outlines the process for migrating an existing Mattermost instance [from self-hosted to Cloud](#migrate-from-self-hosted-to-cloud), and [from Cloud to self-hosted](#migrate-from-cloud-to-self-hosted).
|
||
|
||
<Note>
|
||
|
||
Migrating an existing Mattermost instance to another using the same deployment method follows the same process that's documented below, regardless as to whether the source or destination of the migration is in the Cloud or self-hosted. **These steps will work for both Cloud and self-hosted Mattermost instances**.
|
||
|
||
</Note>
|
||
|
||
## Migrate from self-hosted to Cloud
|
||
|
||
When you migrate from self-hosted to Cloud, you'll need to open a ticket with the Mattermost Support team so they can assist you with the process. The information below describes the migration process. Before you get started, visit our [Support site](https://support.mattermost.com/hc/en-us/requests/new) to open a ticket.
|
||
|
||
<Important>
|
||
|
||
- This migration process is only available to customers using paid Mattermost editions.
|
||
- We recommend reviewing the knowledge base article on [migrating from self-hosted to Cloud](https://support.mattermost.com/hc/en-us/articles/4412503667604-Migrating-from-Self-hosted-Mattermost-Instance-to-Cloud-Mattermost-Instance) before starting a migration to familiarize yourself with key considerations, required prerequisites, and our guidance on testing your export.
|
||
|
||
</Important>
|
||
|
||
Before you begin your migration, take note of the following information before you begin:
|
||
|
||
**User Authentication**
|
||
|
||
If you are using the email login method, users will need to reset their passwords after the migration has been completed. Other authentication methods, such as LDAP and GitLab SSO, required changes to your infrastructure allowing the specific authentication method to function in Mattermost cloud.
|
||
|
||
**Plugins**
|
||
|
||
If you’re using plugins that aren’t listed on the Marketplace, they won’t be included in the export and you won’t have access to them going forward. See the list of supported plugins by visiting the [integrations overview](/integrations-guide/integrations-guide-index#plugins) documentation.
|
||
|
||
**Data**
|
||
|
||
The migration only includes data from Channels. No Playbooks data is exported.
|
||
|
||
### Migration process
|
||
|
||
**Export from your self-hosted instance**
|
||
|
||
Use your administrator credentials to log into your self-hosted Mattermost server. Once you're logged in, run:
|
||
|
||
```
|
||
mmctl export create --attachments
|
||
```
|
||
|
||
This creates a full export of the server, and includes attached files. If you don’t want to export attached files, leave out `--attachments`.
|
||
|
||
This process can take some time, so `mmctl` will return immediately, and the job will run in the background until the export is fully created. If successful, the command will immediately output a job ID, like this:
|
||
|
||
```
|
||
Export process job successfully created, ID: yfrr9ku5i7fjubeshs1ksrknzc
|
||
```
|
||
|
||
While the job is running, its status can be checked using the ID that was provided when it was created, and when it's done the output will look similar to this:
|
||
|
||
```
|
||
mmctl export job show yfrr9ku5i7fjubeshs1ksrknzc
|
||
ID: yfrr9ku5i7fjubeshs1ksrknzc
|
||
Status: success
|
||
Created: 2021-11-03 10:44:13 -0500 CDT
|
||
Started: 2021-11-03 10:44:23 -0500 CDT
|
||
```
|
||
|
||
The completed file will be downloaded to your desktop as a `.zip` file.
|
||
|
||
<Note>
|
||
|
||
Do not rename the file as the file name is referenced in log files, which are used by the Support team to validate the exported file.
|
||
|
||
</Note>
|
||
|
||
The Support team will provide you with S3 credentials so you can upload the exported file. Once you’ve uploaded the file, please contact the Support team and let them know.
|
||
|
||
### Create a new workspace on the Mattermost Cloud
|
||
|
||
In the meantime, you can log into Mattermost Cloud with your Mattermost credentials and create a Cloud workspace.
|
||
|
||
<Note>
|
||
|
||
Do not create any users in your Mattermost Cloud instance as the migration process performs this task for you.
|
||
|
||
</Note>
|
||
|
||
### Importing your data into your Mattermost Cloud instance
|
||
|
||
Once the export upload to the provided S3 bucket is complete and you’ve shared your Mattermost Cloud instance name/URL, Support can begin the import step.
|
||
|
||
Depending on the size of the export this process can take some time. Support will contact you as soon as the import is complete. During this time it is highly recommended you do not use your Mattermost Cloud instance.
|
||
|
||
### Start using your Mattermost Cloud instance
|
||
|
||
When the export is complete, you can log into your Cloud instance and can invite your users to log in.
|
||
|
||
<Note>
|
||
|
||
We recommend that you keep your self-hosted Mattermost server until you’ve been using your Cloud instance for a while and all is verified as is as expected.
|
||
|
||
</Note>
|
||
|
||
## Migrate from Cloud to self-hosted
|
||
|
||
You can migrate your Cloud workspace data to a self-hosted deployment at any time.
|
||
|
||
### How does the process work?
|
||
|
||
Before you export and migrate your data, you must [install Mattermost](/deployment-guide/deployment-guide-index) on the server you’ll be using to run Mattermost. The migration is done using the mmctl CLI tool, which is a remote CLI tool for Mattermost that's installed locally and uses the Mattermost API. `mmctl` is pre-installed.
|
||
|
||
The [mmctl usage notes](/administration-guide/manage/mmctl-command-line-tool#mmctl-usage-notes) provide some additional context and information which you can reference before and during the process.
|
||
|
||
You'll be using the [mmctl export](/administration-guide/manage/mmctl-command-line-tool#mmctl-export) commands to export your Cloud data for channels, messages, users, etc. The export file is downloaded to a location specified in the export commands. Once the export is complete, you'll import the data into your self-hosted instance.
|
||
|
||
Alternatively, you can export the data to an Amazon S3 cloud storage location in cases where an export is quite large and challenging to download from the Mattermost server. See the [create the export](#create-the-export) section below for details.
|
||
|
||
<Note>
|
||
|
||
Prior to migrating your data from Cloud, please ensure you have the appropriate permissions within your organization to carry out the data export which may contain sensitive information. Mattermost is not liable for any actions taken after the data export.
|
||
|
||
Moreover, the export process doesn’t include integrations or any custom data. Other aspects of your instance, such as specific security settings and requirements, are also not included. For assistance with migrating additional data and settings, see our support options: [https://mattermost.com/support/](https://mattermost.com/support/).
|
||
|
||
</Note>
|
||
|
||
Once `mmctl` is authenticated, you can generate the export from the source instance.
|
||
|
||
## Authenticate
|
||
|
||
Authentication is done with either Mattermost login credentials or an authentication token. First, use your administrator credentials to log into the instance with mmctl, replacing <code>example-source-domain.com</code> with the network address of the source instance:
|
||
|
||
```
|
||
mmctl auth login https://yourdomain.cloud.mattermost.com
|
||
```
|
||
|
||
You'll be prompted for a username (use your admin user), password, and for a connection name. The connection name can be anything you want, and it's used to identify this set of credentials in the future, for your convenience. Then you will be able to start the export process.
|
||
|
||
## Create the export
|
||
|
||
<Important>
|
||
|
||
If your Mattermost Cloud deployment includes plugins that aren't listed on the Cloud Marketplace, those plugins won't be included in the export, and you won't have access to those plugins going forward. See the [integrations](/integrations-guide/integrations-guide-index#plugins) documentation for a list of Cloud-supported integrations.
|
||
|
||
</Important>
|
||
|
||
Once you're logged in, run the following `mmctl` command:
|
||
|
||
```
|
||
mmctl export create
|
||
```
|
||
|
||
Running this command creates a full export of the server, including attached files. Append `--no-attachments` if you do not wish to export attached files from your instance, and append `--with-archived-channels` to include archived channels in the export file. This process can take some time, so `mmctl` will return immediately, and the job will run in the background on the Mattermost instance until the export is fully created. If successful, the command will immediately output a job ID, like this:
|
||
|
||
```
|
||
Export process job successfully created, ID: yfrr9ku5i7fjubeshs1ksrknzc
|
||
```
|
||
|
||
While the job is running, its status can be checked using the ID that was provided when it was created, and when it's done the output will look similar to this:
|
||
|
||
```
|
||
mmctl export job show yfrr9ku5i7fjubeshs1ksrknzc
|
||
ID: yfrr9ku5i7fjubeshs1ksrknzc
|
||
Status: success
|
||
Created: 2021-11-03 10:44:13 -0500 CDT
|
||
Started: 2021-11-03 10:44:23 -0500 CDT
|
||
```
|
||
|
||
Once the status is `success`, download the export onto your local machine. First, discover the name of the completed export file with `mmctl export list`:
|
||
|
||
```
|
||
mmctl export list
|
||
r3kcj8yuwbramdt714doafi3oo_export.zip
|
||
```
|
||
|
||
This will show all of the exports on the server, so be sure to download the latest one and to delete it when you're done to save storage. Generate a link to download the file with a command like the following, but with the filename of the export on your server:
|
||
|
||
```
|
||
mmctl export generate-presigned-url r3kcj8yuwbramdt714doafi3oo_export.zip
|
||
```
|
||
|
||
<Tip>
|
||
|
||
- As an alternative to this last step, from your Mattermost Cloud web instance, you can retrieve the file download link to the export by using the Mattermost slash command `/exportlink [job-id|zip file|latest]`. Use the `latest` option to automatically pull the latest export available, or specify the download link by `job-id` or `zip file`.
|
||
- Mattermost v8.1.0-RC1 is required to use the `mmctl export generate-presigned-url` command on a self-hosted Mattermost instance. Access the [Mattermost Enterprise v8.1.0-RC1 binary](https://releases.mattermost.com/8.1.0-rc1/mattermost-enterprise-8.1.0-rc1-linux-amd64.tar.gz) or the [Mattermost Team Edition v8.1.0-RC1 binary](https://releases.mattermost.com/8.1.0-rc1/mattermost-team-8.1.0-rc1-linux-amd64.tar.gz).
|
||
|
||
</Tip>
|
||
|
||
## Upload the export to the new server
|
||
|
||
Finally, it's time to take our export from the source server and use it as an import into the destination server. Before proceeding, review and modify the following self-hosted Mattermost configuration settings, where applicable, to ensure a smooth and successful import.
|
||
|
||
<table style={{width: '100%'}}>
|
||
<colgroup>
|
||
<col style={{width: '39%'}} />
|
||
<col style={{width: '51%'}} />
|
||
<col style={{width: '8%'}} />
|
||
</colgroup>
|
||
<tbody>
|
||
<tr>
|
||
<td><strong>Mattermost configuration setting</strong></td>
|
||
<td><strong>Large file import recommendation</strong></td>
|
||
<td></td>
|
||
</tr>
|
||
<tr>
|
||
<td colspan="3"><a href="mm-ref:administration-guide%2Fconfigure%2Fsite-configuration-settings%3Amax%20users%20per%20team">Maximum Users Per Team | Increase this value to a number that **exceeds** the maximum number of users, per team, in the import file. |</a> |</td>
|
||
</tr>
|
||
<tr>
|
||
<td colspan="3"><a href="mm-ref:administration-guide%2Fconfigure%2Fenvironment-configuration-settings%3Amaximum%20file%20size">Maximum File Size | Temporarily increase this value to be **larger** than the size of the import file. |</a> | Following a successful import, we strongly recommend reverting this value to a reasonable limit for daily expected usage. |</td>
|
||
</tr>
|
||
<tr>
|
||
<td colspan="3"><dl>
|
||
<dt><a href="mm-ref:administration-guide%2Fconfigure%2Fenvironment-configuration-settings%3Awrite%20timeout">Write Timeout | Temporarily adjust this value based on import file speed and network path to enable the file to upload without timeouts. |</a> | Start with a value of <strong>3600</strong> and adjust if needed. |</dt>
|
||
<dd>
|
||
<div class="line-block">Following a successful import, we strongly recommend reverting this setting to its initial or previous value. |</div>
|
||
</dd>
|
||
</dl></td>
|
||
</tr>
|
||
<tr>
|
||
<td colspan="3"><dl>
|
||
<dt><a href="mm-ref:administration-guide%2Fconfigure%2Fenvironment-configuration-settings%3Aread%20timeout">Read Timeout | Temporarily adjust this value based on import file speed and network path to enable the file to upload without timeouts. |</a> | Start with a value of <strong>3600</strong> and adjust if needed. |</dt>
|
||
<dd>
|
||
<div class="line-block">Following a successful import, we strongly recommend reverting this setting to its initial or previous value. |</div>
|
||
</dd>
|
||
</dl></td>
|
||
</tr>
|
||
<tr>
|
||
<td colspan="3"><a href="mm-ref:administration-guide%2Fconfigure%2Fenvironment-configuration-settings%3Aamazon%20s3%20request%20timeout">Amazon S3 Request Timeout | If using cloud-based file storage, adjust this value to ensure your storage requests don't time out too soon. |</a> |</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
|
||
Next, log into the destination server using `mmctl` the same way you logged into the source server:
|
||
|
||
```
|
||
mmctl auth login https://localinstance.company.com
|
||
```
|
||
|
||
Use the following command to upload the export to the destination server. The speed of the upload may vary based on connection speed. When the upload is complete the command will return with the ID of the import:
|
||
|
||
```
|
||
mmctl import upload r3kcj8yuwbramdt714doafi3oo_export.zip
|
||
Upload session successfully created, ID: cfuq6q9kkjrqfgnph1pew3db4e
|
||
Import file successfully uploaded, name: xrzs9wrzufntbfcxpy39mdq9hy
|
||
```
|
||
|
||
## Complete the import into the new server
|
||
|
||
```
|
||
mmctl import list available
|
||
cfuq6q9kkjrqfgnph1pew3db4e_r3kcj8yuwbramdt714doafi3oo_export.zip
|
||
```
|
||
|
||
Run the import job to process to import the export file into the server. The speed of this process may vary based on connection speed. First, start the import process:
|
||
|
||
```
|
||
mmctl import process cfuq6q9kkjrqfgnph1pew3db4e_r3kcj8yuwbramdt714doafi3oo_export.zip
|
||
```
|
||
|
||
Once you've marked the file for processing, you can check the status of the job using `mmctl import job list`:
|
||
|
||
```
|
||
mmctl --local import job list
|
||
ID: f93jxu1hzty79enwa1xy6f1tbr
|
||
Status: pending
|
||
Created: 2021-10-28 13:32:55 +0200 CEST
|
||
```
|
||
|
||
When the job is complete, the `success` status is displayed:
|
||
|
||
```
|
||
mmctl --local import job list
|
||
ID: f93jxu1hzty79enwa1xy6f1tbr
|
||
Status: success
|
||
Created: 2021-10-28 13:32:55 +0200 CEST
|
||
Started: 2021-10-28 13:33:05 +0200 CEST
|
||
```
|
||
|
||
Then extract the export file to use it by running the following mmctl command:
|
||
|
||
```
|
||
mmctl extract run [flags].
|
||
```
|
||
|
||
Once your migration is complete and you’ve imported your data into your self-hosted instance we recommend that you take a few days to validate your data and ensure everything is working as expected before taking down your Cloud instance.
|
||
|
||
<Note>
|
||
|
||
If you are using email/password authentication, your users must reset their passwords.
|
||
|
||
</Note>
|
||
|
||
If you encounter any issues or problems, [contact our support team](https://mattermost.com/support/), or visit the [Mattermost Help Center](https://support.mattermost.com/).
|
||
|
||
## Migrate from self-hosted to Cloud
|
||
|
||
When you migrate from self-hosted to Cloud, you'll need to open a ticket with the Mattermost Support team so they can assist you with the process. The information below describes the migration process. Before you get started, visit our [Support site](https://support.mattermost.com/hc/en-us/requests/new) to open a ticket.
|
||
|
||
<Note>
|
||
|
||
This migration process is only available to customers using paid Mattermost editions.
|
||
|
||
</Note>
|
||
|
||
Before you begin your migration, take note of the following information before you begin:
|
||
|
||
**User Authentication**
|
||
|
||
If you are using the email login method, users will need to reset their passwords after the migration has been completed. Other authentication methods, such as LDAP and GitLab SSO, required changes to your infrastructure allowing the specific authentication method to function in Mattermost cloud.
|
||
|
||
**Plugins**
|
||
|
||
If you’re using plugins that aren’t listed on the Marketplace, they won’t be included in the export and you won’t have access to them going forward. You can view the list of plugins [in the Support knowledgebase](https://support.mattermost.com/hc/en-us/articles/5346624843924-Mattermost-Plugin-Marketplace-List-as-of-November-12th-2024).
|
||
|
||
**Data**
|
||
|
||
The migration only includes channel data. No collaborative playbooks data is exported.
|
||
|
||
### Migration process
|
||
|
||
**Export from your self-hosted instance**
|
||
|
||
Use your administrator credentials to log into your self-hosted Mattermost server. Once you're logged in, run:
|
||
|
||
```
|
||
mmctl export create --attachments
|
||
```
|
||
|
||
This creates a full export of the server, and includes attached files. If you don’t want to export attached files, leave out `--attachments`.
|
||
|
||
This process can take some time, so `mmctl` will return immediately, and the job will run in the background until the export is fully created. If successful, the command will immediately output a job ID, like this:
|
||
|
||
```
|
||
Export process job successfully created, ID: yfrr9ku5i7fjubeshs1ksrknzc
|
||
```
|
||
|
||
While the job is running, its status can be checked using the ID that was provided when it was created, and when it's done the output will look similar to this:
|
||
|
||
```
|
||
mmctl export job show yfrr9ku5i7fjubeshs1ksrknzc
|
||
ID: yfrr9ku5i7fjubeshs1ksrknzc
|
||
Status: success
|
||
Created: 2021-11-03 10:44:13 -0500 CDT
|
||
Started: 2021-11-03 10:44:23 -0500 CDT
|
||
```
|
||
|
||
The completed file will be downloaded to your desktop as a `.zip` file.
|
||
|
||
<Note>
|
||
|
||
Do not rename the file as the file name is referenced in log files, which are used by the Support team to validate the exported file.
|
||
|
||
</Note>
|
||
|
||
The Support team will provide you with S3 credentials so you can upload the exported file. Once you’ve uploaded the file, please [contact our support team](https://mattermost.com/support/) and let them know.
|
||
|
||
### Create a new workspace on the Mattermost Cloud
|
||
|
||
In the meantime, you can log into Mattermost Cloud with your Mattermost credentials and create a Cloud workspace.
|
||
|
||
<Note>
|
||
|
||
Do not create any users in your Mattermost Cloud instance as the migration process performs this task for you.
|
||
|
||
</Note>
|
||
|
||
### Importing your data into your Mattermost Cloud instance
|
||
|
||
Once the export upload to the provided S3 bucket is complete and you’ve shared your Mattermost Cloud instance name/URL, Support can begin the import step.
|
||
|
||
Depending on the size of the export this process can take some time. Support will contact you as soon as the import is complete. During this time it is highly recommended you do not use your Mattermost Cloud instance.
|
||
|
||
### Start using your Mattermost Cloud instance
|
||
|
||
When the export is complete, you can log into your Cloud instance and can invite your users to log in.
|
||
|
||
<Note>
|
||
|
||
We recommend that you keep your self-hosted Mattermost server until you’ve been using your Cloud instance for a while and all is verified as is as expected.
|
||
|
||
</Note>
|