Skip to content

Commit 4dfe171

Browse files
EN proof
1 parent 8466937 commit 4dfe171

File tree

1 file changed

+11
-11
lines changed
  • pages/web_cloud/email_and_collaborative_solutions/zimbra/migrate_mxplan_to_zimbra

1 file changed

+11
-11
lines changed

pages/web_cloud/email_and_collaborative_solutions/zimbra/migrate_mxplan_to_zimbra/guide.en-gb.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'Migrating an MX Plan email address to an OVHcloud Zimbra account'
2+
title: 'How to migrate an MX Plan email address to an OVHcloud Zimbra account'
33
excerpt: 'Find out how to migrate an MX Plan email address to an OVHcloud Zimbra account'
44
updated: 2025-03-05
55
---
@@ -8,14 +8,14 @@ updated: 2025-03-05
88

99
As part of the gradual transition from MX Plan accounts to Zimbra, you can anticipate this migration and carry out the email account transfer yourself before OVHcloud implements an automated tool. This guide will show you how to migrate manually.
1010

11-
**Find out how to migrate an MX Plan email address to an OVHcloud Zimbra account.**
11+
**This guide explains how to migrate an MX Plan email address to an OVHcloud Zimbra account.**
1212

1313
## Requirements
1414

15-
- You must have an MX Plan email address (via the MX Plan solution, or included in an [OVHcloud Web Hosting](/links/web/hosting) solution).
16-
- An OVHcloud Zimbra email account.
17-
- **Do not set redirection on the MX Plan email address you want to migrate**.
18-
- You must be logged in to your [OVHcloud Control Panel](/links/manager).
15+
- You have an MX Plan email address (via the MX Plan solution, or included in an [OVHcloud web hosting](/links/web/hosting)).
16+
- You have an OVHcloud Zimbra email account.
17+
- **No redirection is applied to the MX Plan email address you want to migrate**.
18+
- You have access to the [OVHcloud Control Panel](/links/manager).
1919

2020
## Instructions
2121

@@ -41,7 +41,7 @@ In the example below, we are migrating the address `[email protected]`. To do
4141

4242
> [!primary]
4343
>
44-
> If you already have an Zimbra email address, go to [Migrate emails with OVH Mail Migrator](#step12).
44+
> If you already have a Zimbra email address, go to [Migrate emails with OVH Mail Migrator](#step12).
4545
4646
First, create an email address with a temporary name. For example, you can create the address `[email protected]`{.action} if you need to migrate the address `[email protected]`{.action}.
4747

@@ -68,7 +68,7 @@ On the <https://omm.ovh.net/> page, in the `Migration`{.action} tab, click `New
6868
|Source login|Enter the full email address (`[email protected]`).|
6969
|Destination login|Enter the full email address (`[email protected]`).|
7070
|Administrator account with delegation|This field appears only with certain server types.|
71-
|Password|Enter the password for the email address concerned.|
71+
|Password|Enter the password for the email account concerned.|
7272

7373
- **Options**: Select the elements you want to migrate. Some content may be unavailable, depending on the server type you have chosen.
7474

@@ -93,7 +93,7 @@ There are two ways to track a single migration:
9393

9494
On the page that opens, you can track the progress of your migration. You will see a message indicating whether the process will begin, is in progress, or has been completed. Depending on this status, there are several possible interactions:
9595

96-
- `Stop the process`{.action}: allows you to cancel the migration. Items that have already been migrated will remain in the destination account.
96+
- `Stop the process`{.action}: Allows you to cancel the migration. Items that have already been migrated will remain in the destination account.
9797
-`Delete migrated elements`{.action}: Enables you to delete elements that have already been migrated to the destination account. You can clear items from a specific synchronization point.
9898
- `Synchronize`{.action}: Used to retrieve new elements that were not migrated during a previous synchronization between the source account and the destination account. We consider this action as a migration of the missing elements on the destination account from the source account.
9999

@@ -109,7 +109,7 @@ To migrate by file or multiple files, please read the “Migrate by file” and
109109
>
110110
> Before deleting your MX Plan account, **back up your emails** to avoid any data loss.
111111
112-
Use the export options of your email client. In our guide on [Migrating your email address manually](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration), you can find the details for manually exporting an email address from an email client.
112+
Use the export options of your email client. In our guide on [Migrating your email address manually](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration), you can find the details for manually exporting an email account from an email client.
113113

114114
### 2.1 - Deleting the old MX Plan email address <a name="step21"></a>
115115

@@ -139,4 +139,4 @@ For specialized services (SEO, development, etc.), contact the [OVHcloud partner
139139

140140
If you would like assistance with using and configuring your OVHcloud solutions, we recommend referring to our range of [support solutions](/links/support).
141141

142-
Join our [community of users](/links/community).
142+
Join our [community of users](/links/community).

0 commit comments

Comments
 (0)