Migrating from Yandex.Mail for Domain

Compared with Yandex.Mail for Domain, Yandex.Connect offers more features for managing domains and user mailboxes. Migration to Yandex.Connect is automatic, so you don't need to do anything. Changes will only affect the admin tools. The migration will not affect user mailboxes in any way.

Tip. If you don't want to wait for the automatic migration, you can launch it manually.

Migrating to Yandex.Connect

Warning. Mailbox functions might be unstable during the migration.

To migrate your domain and mailboxes from Yandex.Mail for Domain to Yandex.Connect:

  1. Make sure you are logged in to Mail for Domain as the administrator.

  2. Go to the .

  3. Click the link Migrate to Yandex.Connect.

  4. Wait for the message about your data being successfully moved to Yandex.Connect. This usually takes a few minutes.

Restriction. The admin account for Yandex.Mail for Domain can't be used for working with Yandex.Connect services. To be able to use Yandex.Connect services, create an employee account for yourself. If necessary, grant administrator rights.

Differences between Yandex.Connect and Yandex.Mail for Domain

When migrating from Yandex.Mail for Domain to Yandex.Connect, the following changes occur:

  • Mail for Domain mailboxes become employee accounts for your organization.

  • Mailing lists from Mail for Domain become teams in Yandex.Connect. Users on a mailing list become members of the team.

    Teams that are created automatically don't have admins. Only the company admin can assign the admin for this type of team.

  • The Mail for Domain admin can manage the company settings in Yandex. Connect.

  • To confirm domain ownership in Yandex.Connect, go to the page. For information about domain confirmation, see the Help for Yandex.Connect.

  • You can find the DNS record configuration settings for domains delegated to Yandex on the page.

Note. If multiple domains are connected to Mail for Domains (other than domain aliases), separate organizations will be created for them.

The other differences are shown in the table:

Yandex.ConnectYandex.Mail for Domain

Unlimited mailbox size


Maximum number of mailboxes


DNS hosting


Domain aliases


Free third-level domain


Mailbox aliases


Public API


Support for organizational hierarchy




Protection from spam and viruses in email

Domain mailing lists++
Number of domain administratorsUnlimited1

Company signature for domain mailboxes


Shared employee address book


Employee profiles


Space on Yandex.Disk for each employee

10 GB10 GB

Yamb corporate messenger


Wiki for company knowledge base



I am using the Yandex.Mail for Domain API. Will I be able to use the API after the migration?

The Yandex.Connect API is different from the Yandex.Mail for Domain API. To start, we will be migrating domains that don't use the API. We will notify you later about migrating other domains.

To see how the Yandex.Connect API works, review the .

My mail domain is connected to Bitrix24. Will migrating to Yandex.Connect affect how it works?

Integration with Bitrix24 is not ready yet. We are not automatically migrating Bitrix24 users to Yandex.Connect at this time. If you use Bitrix24, do not migrate your domains manually. We will notify you when Yandex.Connect domains can be connected to Bitrix24.

I only use Mail and I don't need anything else. Can I choose to not migrate to Yandex.Connect?

Mailbox owners on your domain will not notice any changes. The email interfaces in Yandex.Mail for Domain and Yandex.Connect are almost identical. For domains that we migrate automatically, the Yandex.Connect collaboration services are disabled by default.

The main changes are in the interface for managing domains and accounts. There are more admin features available in Yandex.Connect. For example, you can set up employee accounts to reflect the organizational hierarchy of your company.

If you have not found the answer to your question, write to us: