Microsoft 365 (Outlook)

Start migration

Prepare a secret, link a domain, and prepare employee accounts if you haven't already done so. Make sure that the source and target domain names match.
Note. The secret applies to all running migrations. If you have already started migration and then upload a new secret, it will be applied to this migration. The secret permissions are also taken into account: if the new secret only has access to email (Mail.Read and Mail.ReadBasic.All API permissions) and you have started file migration, it will stop.
Go to the Migration tab in the left menu.
Select what you want to migrate: click Migrate email.
Select where you want to migrate mail from: click Microsoft 365.
Upload the secret file and click Next.
Specify the accounts for which you want to start migration:
1. Download the CSV file template.
2. Following the example, add employee data to the file.
  
  The first row in the file is the account field headers. Don't delete it. Each following line must contain data for one account, delimited by a semicolon and in quotation marks.
  
  You must provide the addresses of original mailboxes, and employee usernames on your domain where you want to migrate. The usernames in the yandex_login column may not match the account names in Microsoft 365. For example, if an employee has the username ivan.ivanov in Yandex 360 for Business, and their original mailbox is [email protected], enter ivan.ivanov in the yandex_login column.
  
  The resulting file should have the following structure:
```
"yandex_login";"external_email"
"ivan.ivanov";"[email protected]"
"marina.makarova";"[email protected]"
```
  Note. You can add up to 20,000 usernames to a file. If the company has more employees, you can run multiple migrations with different CSV files. Migrations will run in parallel.
3. Save the CSV file in UTF-8 encoding (in Microsoft Excel, click Save as → CSV-UTF8).
  Attention. If you save the file in a different encoding, it won't be recognized correctly.
4. Click Upload CSV and select your file.
Click Start migration.
The status will change to Migrating.

Note. If you plan to run multiple migrations, save the log file before each run (you can download it by clicking Details). If errors occur during migration, you'll be able to track at which run they appeared.

Migration process

Migration doesn't happen immediately. Data collection takes from a few minutes to two hours, and then emails from original mailboxes begin to appear in Yandex Mail for Business mailboxes. Folders from original mailboxes are also copied to target mailboxes.

During migration, 0 is displayed next to the corresponding stage. If you see 0 at the Migration stage, it means that the transfer of old emails is completed. If you only want to transfer old emails without collecting new ones, you can stop migration at this stage manually by clicking Stop.

Note. If the MX record points to your old server, incoming emails will be delivered to original mailboxes and then transferred to Yandex Mail for Business mailboxes. To stop receiving emails to the old server, delegate the domain or switch the MX record to the Yandex server.

If you don't stop migration at this stage manually, new emails delivered to mailboxes on the old server will be gradually transferred to new mailboxes. You can switch the MX record at any time: after that, incoming emails will be delivered to Yandex Mail for Business mailboxes.

What happens if you stop migration

All running migrations and incoming mail collection from original mailboxes to Yandex Mail for Business mailboxes will stop. To resume email transfer, start a new migration. It will transfer new emails that were received to original mailboxes after you stopped the previous migration. Old emails that have already been migrated won't be duplicated.

What happens if you start a new migration

The new migration will run in parallel with the already running migrations.

Troubleshooting

Take note of the following possible errors and ways to fix them.

The uploaded secret is invalid: Make sure that you prepared the secret correctly.
The first line in the CSV file has been deleted or changed: Download the CSV file template and copy the first line from it to your CSV file. Make sure that the previous import is completed and start a new import with the corrected CSV file.
The source and target domain names don't match: Before starting migration, make sure that the source and target domain names match. Otherwise, you won't be able to start migration.

To view the report with a detailed description of errors, click Details in the top right corner of the active migration page. For information on how to fix them, see Migration error report.

Contact support