Quick Answer
To migrate IceWarp to Office 365 you have two native methods, because IceWarp has no export of its own. Microsoft's IMAP batch copies mail folders from an online IceWarp server and skips contacts, calendar items and tasks. A PST import needs one PST file for each mailbox first. A Windows migrator can also upload mail, contacts and calendars from IceWarp data after one admin sign-in.
Check your largest mailbox first, because Microsoft's IMAP batch copies up to 500,000 items in each mailbox and messages up to 35 MB.
If you must migrate IceWarp to Office 365, you will find that nothing in IceWarp sends a mailbox to Microsoft. Its Migration page lists tools that bring data into IceWarp from Microsoft 365, Google Workspace, Exchange and Kerio. None of them moves data out. Microsoft 365 can take your mail in two ways. These are an IMAP batch and a PST import. A Windows migrator adds a third way.
Your choice depends on three facts. These are whether your IceWarp server still answers, how many mailboxes are on your list and whether contacts and calendars must come along.
- If your server is online and you have passwords for a few mailboxes, Microsoft's IMAP batch is a free way to start.
- If your list is long or your users need their contacts and calendars in Microsoft 365, read the migrator section, because it uploads from IceWarp mail data directly.
- If your server is switched off and only a copied mail folder or a backup .zip is left, IMAP cannot help. Use PST files or the migrator.
Why Does IceWarp Not Move Mail Out to Office 365?
I read IceWarp's Migration page on 15 November 2026. Every migrator on it brings data into IceWarp. I found no tool that moves data from IceWarp to Microsoft 365. The page offers a migration service request and nothing else for a move out.
The Server Migration page in IceWarp's help also points inward. It describes a proxy that fetches mail from an old server into IceWarp over POP3 or IMAP when each user signs in for the first time. That page does not mention contacts or calendars.
IceWarp keeps each user's mailbox in the Mail path folder, which its Directories page documents. A backup .zip from System Backup contains mail messages only if Backup emails was selected, so open a backup before you plan a move around it.
Who Moves IceWarp Mailboxes to Microsoft 365?
- An admin with a company domain Your company chose Microsoft 365 and every mailbox of your IceWarp domain has to follow.
- An admin after a first attempt Your mail arrived over IMAP but your users' address books and calendars stayed behind.
- An owner with a stopped server Your IceWarp machine is off and a copied mail folder is your only source of mail.
- A manager with a closing account One mailbox must reach Microsoft 365 before IceWarp removes the account.
Which Method Fits Your IceWarp to Office 365 Migration?
Three methods reach Microsoft 365. The table shows what each one moves and where it stops.
| Method | What it moves | Where it stops |
|---|---|---|
| IMAP batch from Microsoft | Microsoft 365 reads each mailbox from your online IceWarp server over IMAP, using a CSV list | Mail folders only. Up to 500,000 items in each mailbox and messages up to 35 MB. Needs a password or an admin account for each mailbox |
| PST import in Purview | You turn each mailbox into a PST file, upload the files to Azure Storage and Microsoft 365 imports them | IceWarp creates no PST. Files of 20 GB or less. Items over 150 MB are skipped. The Mailbox Import Export role is needed |
| Windows migrator | A Windows application reads IceWarp mail data on your PC and uploads it with one admin sign-in | Needs Windows 11 or 10 and a licence beyond the trial of 10 items per folder |
I start with the IMAP batch if your IceWarp server is stable and your mailbox list is short, because Microsoft does the copying at no extra cost. If your users need their contacts and calendars too, that choice changes. A PST import also asks for one PST per mailbox first. My guide to convert IceWarp to PST shows how to make them. For Microsoft's side of that import, read the import PST to Office 365 guide.
Five Steps to Move IceWarp Mailboxes by IMAP Batch
Read the migrate IMAP to Office 365 guide for Microsoft's own screens. The steps below cover the IceWarp side.
- Check IMAP access. Confirm that your IceWarp server answers IMAP over SSL/TLS. Univik's IceWarp email settings page lists the host and port values. If you limited connections on the server or firewall, raise those limits first, as Microsoft recommends.
- Create the Microsoft 365 users. Add every user in Microsoft 365 and assign a licence. An IMAP migration fills mailboxes that already exist.
- Build the CSV list. List the email address, user name and password of each mailbox in a CSV file. If you cannot get the passwords, Microsoft says to reset them. Users cannot open their old mailboxes until they learn the new ones.
- Turn off retention rules. Switch off messaging records management and archival policies before the batch. Microsoft's tool does not recognise them, so mail they remove shows as missing.
- Create the batch and cut over. Open the Exchange admin center and add your IceWarp server as the migration endpoint. Create the batch with your CSV file and start it. Once a few mailboxes match their source, change your MX record. Then delete the batch to stop the sync.
What Does the IMAP Batch Leave Behind?
Microsoft's IMAP migration page says the batch copies mail from the inbox and the other mail folders. It does not migrate contacts, calendar items or tasks. Mail goes from newest to oldest up to 500,000 items in each mailbox, so the oldest messages of a very large mailbox may not arrive. The largest message that can be migrated is 35 MB.
Do this: IceWarp Desktop Client opens an Export dialog under File. Its help page includes .xml, .vcf, .ics and .eml files in its examples. A .vcf file contains contacts. Import it into Outlook as Microsoft describes for vCard files.
Do this: In Outlook on the web, choose Calendar, then Add calendar and Upload from file. Microsoft says imported events are a snapshot, so a later change in IceWarp does not reach them.
Do this: When your list is long, importing files for every user adds hours. A migrator that sends contacts and calendars into the mailbox removes that step, as the next section shows.
I have not tested these file exports on an IceWarp account of my own, so open one imported contact and one calendar item before you tell your users that the move is done.
Move IceWarp Mailboxes Straight to Office 365 on Windows
Univik IceWarp Migrator reads IceWarp mail data on your PC and uploads it to Office 365. It accepts five sources. These are a Mail path copy, .imap message files, a System Backup .zip, a live account sign-in and IceWarp Cloud. Because the data is read on your PC, your IceWarp server can stay switched off. Mail, contacts and calendars go straight into the mailbox. One admin sign-in on Microsoft 365 replaces a list of user passwords.
- Copy your data. Copy the Mail path folder from your IceWarp server to your PC. Skip this step when you use .imap files, a backup .zip, a live account or IceWarp Cloud.
- Add your mailbox list. Start the migrator, choose your source and add the CSV mapping list. That list ties each IceWarp mailbox to its place in Microsoft 365.
- Choose Office 365. Choose Office 365 as the target. Then sign in once with an admin account of your tenant. Your users do not share passwords.
- Send a test batch. Move two or three mailboxes first. If they look right in Microsoft 365, start the full list. If the batch stops, resume it.
- Check the log. Open the log report. Then open a few migrated mailboxes in Microsoft 365 next to your IceWarp source. Change your MX record only after the two match.
Limitations: the trial limit is 10 items for each folder. The migrator supports IceWarp EPOS 3 (14.3.0.x), EPOS Update 2 (14.2.0.x), EPOS Update 1 (14.1.0.x) and Deep Castle 2 (13.x). It needs Windows 11 or Windows 10 with .NET Framework 4.8. Univik's only timed move sent 8 mailboxes with 340,000 messages (2.4 GB) to an IMAP server in 20 minutes. Univik has not timed an upload to Office 365, so I give you no speed figure for it.
Windows reads your IceWarp mail data and uploads the mailboxes on your list to Microsoft 365 after one admin sign-in.
Download Free Trial Select a Licence - From $99Send two test mailboxes through the trial and open them in Microsoft 365 before you buy a licence.
What If Mail or Contacts Are Missing After the Move?
Do this: When mail reached IceWarp after your copy, that mail is not in Microsoft 365. With the IMAP batch, keep the batch until your MX change works, since Microsoft says to delete it only after mail is delivered to the new mailboxes.
Do this: An IMAP batch stops at 500,000 items for each mailbox and starts from the newest. Check the oldest folders of your largest mailbox against IceWarp.
Do this: The IMAP batch skips them by design. Export them from IceWarp as .vcf and .ics files or use a migrator that sends them straight into the mailbox.
For a person to plan the move with you, Univik offers IceWarp migration services.
Which Pages Back Up This IceWarp Guide?
On 15 November 2026 I read these IceWarp pages: Migration, Server Migration, Directories, System Backup and Desktop Client export. I also read Microsoft's IMAP migration page, its PST import overview and its calendar import article. Where a page said nothing about a move out of IceWarp, I wrote that it says nothing and left the gap open.
Univik supplied the migrator facts and its one timed move. If your target is Microsoft 365, time two or three of your own mailboxes in the trial first, because a larger data set may take longer.
- IceWarp's Migration page lists tools that bring data into IceWarp and none that moves data out to Microsoft 365.
- Microsoft's IMAP batch copies mail folders only. The limits are 500,000 items in each mailbox and 35 MB for a message.
- IceWarp creates no PST, so a PST import needs one PST per mailbox first.
- A Windows migrator reads IceWarp mail data and uploads mail, contacts and calendars after one admin sign-in.
- Before you change your MX record, check a few migrated mailboxes against IceWarp.
FAQ: Migrate IceWarp to Office 365
How do I migrate IceWarp to Office 365?
Use Microsoft's IMAP batch while your IceWarp server is online. You can also turn mailboxes into PST files for Microsoft's PST import. A Windows migrator can also read IceWarp mail data and upload mail, contacts and calendars after one admin sign-in.
Does IceWarp have a tool to move mail to Microsoft 365?
No. IceWarp's Migration page lists tools that bring data into IceWarp. It lists none that move data out.
Does Microsoft's IMAP migration move contacts and calendars?
No. Microsoft's page says the IMAP migration copies mail folders. Contacts, calendar items and tasks are not migrated.
What are the limits of an IMAP migration to Microsoft 365?
Each mailbox is limited to 500,000 items, copied from newest to oldest. The largest message may be 35 MB.
Can I move IceWarp to Office 365 when the server is switched off?
Yes, if you kept the data. Univik IceWarp Migrator reads a copy of the Mail path, single message files or a System Backup .zip, all on your PC. Microsoft's IMAP batch needs a server that answers.
Which IceWarp releases does the Windows migrator support?
It supports IceWarp EPOS 3 (14.3.0.x), EPOS Update 2 (14.2.0.x), EPOS Update 1 (14.1.0.x) and Deep Castle 2 (13.x).
Can I test the Windows migrator before I buy a licence?
Yes. The trial limit is 10 items for each folder, so two or three of your own mailboxes can go through a test first.
When should I change the MX record after an IceWarp migration?
Change it after a few migrated mailboxes match their IceWarp source. With an IMAP batch, Microsoft says to delete the batch after mail is delivered to Microsoft 365.
