This article explains how Cloudiway handles email address translation during a mail migration.


Cloudiway automatically determines the best algorithm for translation of mail addresses found in SMTP headers.

For instance let’s migrate the following mail:
subject: …

Imagine that you are migrating from the domain to the domain and at the same time that the naming conventions are changing.
Once migrated, the mail should look like:

subject: …

The first two addresses are translated and the external domains remain unchanged.


The algorithm of email translation is:

  1. If the email address to translate is not in the source domain, it remains unchanged (considered external domain).
  2. In the user list, if all users have the same source and target email address, there is no need to perform any translation and email translation is automatically disabled.
  3. In the user list, if all users have the same prefix and a different domain name, emails are translated using the domain name defined in the target connector =>
  4. In all other cases, the user list is used as the mapping table: if the source email is found in the referencial, it’s translated to the targetemail address.

If you want to perform a migration without any mail address translation, in the global settings, disable email translation.
Disable email translation

Office 365 to Office 365 migration

You are migrating from Office 365 to Office 365 and want to keep the same domain (move the domain between two tenants).
The same domain cannot be attached at the same time to both tenants.
For the target email address, you need to define a user in the form
And you do not want to convert emails to something like
Therefore you should disable email translation.


SMTP email address translation can be enabled or disabled.
However X.500 email conversion is automatic between Exchange and Office 365 servers.
During the migration of a mail, if an X.500 address is found, it is automatically converted to the SMTP address.