- IMAP server
- imap.ukr.net
- Port
- 993 · SSL/TLS
- Username
- full address
- Password
- app password
@UKR.NET → Gmail
Migrating from UKR.NET to Gmail
Moving off the Ukrainian mail service is held up by UKR.NET rather than by Gmail: since February 2020 the account password is refused over IMAP, and external access stays off until you switch it on. After that it is an ordinary migration, with the receiving Google side as the bottleneck.
- IMAP server
- imap.gmail.com
- Port
- 993 · SSL/TLS
- Username
- full address
- Password
- app password
What breaks on this particular pair
- On the UKR.NET side, turn external access on and generate its own password first, under "Керування IMAP-доступом". The account password will not do.
- Gmail needs its own app password and IMAP enabled: two different passwords for two sides, and mixing them up is the most common failure here.
- Gmail receives more slowly than it sends, so the inbound side decides how long the move takes — not UKR.NET.
- Cyrillic folder names travel in modified UTF-7. We decode them, so "Вхідні" stays "Вхідні" instead of turning into gibberish.
FAQ
Common questions
Where does the UKR.NET app password come from?
Mailbox settings: "Керування IMAP-доступом" → switch it on → confirm with the account password → name the program → create the password. It is shown once.
Are folders and original dates preserved?
Yes — the folder tree, read flags and original dates all carry over. Nothing arrives dated today.
Does the mail stay in UKR.NET?
Yes. The default mode copies only and deletes nothing at the source.
How long will it take?
The size is measured before the run and shown in the form. Gmail's intake sets the pace: a few gigabytes usually take a day or two.
Related routes
Other directions
Find out how big your mailbox is. It costs nothing.
Connect two servers, look at the size and decide. Or take the client and keep everything on your side.
Code on GitHub · built on imapsync · no sign-up