Email Migration

Migrate Grommunio to Office 365 from a live server or a copy of your data

Leena Taylor Paul By Updated November 14, 2026 8 min read

Quick Answer

Grommunio cannot send a mailbox to Office 365 by itself. Your mail can still arrive in two ways. Microsoft can fetch mail over IMAP from your live Grommunio server, but it moves mail only and leaves contacts, calendars and tasks behind. You can also save a copy of your Gromox data as PST files and import them. IMAP works only while the server is running and every user has a login. PST files work from a copy.

Microsoft stops IMAP migration at 500,000 items in one mailbox and refuses a message above 35 MB.

If your company is leaving Grommunio for Microsoft 365, you will find that Grommunio has no button that sends a mailbox to Office 365. The gromox-export manual page names five output formats and a PST is not among them. Microsoft 365 takes mail through two doors, an IMAP copy and a PST import. The IMAP copy comes from your live Grommunio server. The PST import uses PST files that you built from a copy of your Gromox data.

I'd start by looking at your server, because your server decides which method is open to you. If your server is healthy and you know the passwords of your users, Microsoft's own IMAP migration needs no extra software. When your server is switched off or you want PST files, a copy of your Gromox data is the safer base. A program reads that copy and never contacts your live server.

Choose the method that fits your situation
  • If your Grommunio server is online and you can get a login for every user, use Microsoft's IMAP migration, which moves mail folders and nothing else.
  • If your server is off or users need their calendars and contacts, copy your Gromox data and save PST files from the copy.
  • If you need only a few items, use gromox-export on the server, which saves an item in a standard mail format without any extra software.

Why Does Grommunio Have No Button for Office 365?

Grommunio keeps each user's mail in Gromox data. Microsoft 365 has no connector that reads Gromox data. The gromox-export manual page lists vCard, TNEF, GXMT, RFC 5322 and iCalendar as output types, so Outlook can't open what it creates as a mailbox. That leaves two doors on the Microsoft side. Both are easy to find in the admin center.

The IMAP door has a limit that matters to you. Microsoft's IMAP migration page says it moves the inbox and the other mail folders, but it doesn't move contacts, calendar items or tasks. It also stops at 500,000 items in one mailbox. A message above 35 MB is refused too. Microsoft copies the newest mail of each mailbox first, so if a mailbox is larger than that limit, the oldest mail may stay behind, which is usually the reason a long-lived mailbox looks short in Microsoft 365.

The PST door has its own limits. Microsoft's PST import page asks for PST files of 20 GB or less, skips any item over 150 MB and calls about 24 GB a day the import rate. That import rate isn't guaranteed according to the same page, so a large domain may take several days to import.

Who Moves Grommunio Mail to Microsoft 365?

Which of these is your week?
  • A whole domain Your company is leaving Grommunio and every mailbox has to reach Microsoft 365 before the old server goes away.
  • A switched-off server Your Grommunio machine has been shut down and only a backup copy of the Gromox data is left.
  • A test group You want to move two or three mailboxes first and check them before the rest of your users follow.
  • One person with old mail Someone needs years of mail in Outlook and has no Grommunio login any more.

Which Method Fits Your Grommunio to Office 365 Migration?

Three methods are open to you. The table below shows what each one asks of you and where it stops.

MethodWhat you doWhat stops you
Microsoft IMAP migration Microsoft 365 connects to your live Grommunio server and copies the mail one folder at a time Needs the server online, a password or admin login for each user and mailboxes that already exist in Microsoft 365. Mail only
PST files from a Gromox copy A Windows program takes the data folder from your Gromox copy and saves PST files that you import Needs a Windows PC, a licence for the full export and a separate import step
gromox-export on the server You export single items in a standard mail format Works item by item on the server and has no PST format

I'd use IMAP when your server is up and your mailboxes are small, since Microsoft does the copying for you without any extra program on your Windows PC. However, when your users keep calendars in Grommunio, I'd rather start from a copy, because IMAP leaves those items behind and the copy can save them as separate files. Test two mailboxes first.

Before a domain leaves Grommunio, copy the data and move two test mailboxes from that copy. If both look right in Microsoft 365, the rest of your users follow the same steps.

Nick Rogers, Founder of Univik
Nick Rogers
Founder, Univik
Making Windows software since 2013

Move Grommunio Mail to Microsoft 365 Over IMAP in Five Steps

Microsoft's batch screens are covered in our migrate IMAP to Office 365 guide, so this section lists what you check on the Grommunio side first. A quick check there often saves a failed batch later.

  1. Create the users. Create each user in Microsoft 365 and assign a licence, because Microsoft says the mailboxes have to exist before an IMAP migration can fill them.
  2. Check the IMAP settings. The Gromox IMAP service listens on port 143 and on port 993 for implicit TLS. Its documentation lists imap_support_tls as false by default, so check in imap.cfg that TLS is switched on before Microsoft connects.
  3. Collect the sign-in details. Know each user's password or use administrator credentials. If you have neither, reset the passwords first, then list your mailboxes in a CSV file.
  4. Create the endpoint and the batch. In the Exchange admin center, create a migration endpoint for your Grommunio server and a migration batch from your CSV file. Microsoft also advises you to turn off MRM and archival policies first, because items they remove are flagged as missing.
  5. Check the mail and change the MX record. Start the batch and compare a few mailboxes with Grommunio. Then change the MX record, check that new mail reaches the Microsoft 365 mailboxes and delete the batch.

A missing TLS setting is a common cause of a refused connection. If a user can't sign in during the batch, the Gromox IMAP page may explain it. It lists 10 failed logins as the default limit, with a block of 1 minute, so a wrong password in your CSV file may lock a mailbox for a short time. Wait a minute and try again.

Save Grommunio Mail as PST Files When the Server Is Off

Univik Grommunio Migrator opens the Gromox data folder that you copied to your Windows computer. Each mailbox on your list becomes a PST, EML or MBOX file. The migrator can also upload it to the IMAP server of your choice. Because the copy is the only thing it reads, your old Grommunio server can stay off and your original data stays unchanged.

Reading and saving both happen on your Windows PC, away from the live server.
  1. Copy the data. Copy /var/lib/gromox, the default Gromox data folder, from your server to your Windows PC. Grommunio's operations page describes rsync backups, so a copy made with rsync or a disk snapshot works.
  2. Load your copy. Open the migrator and select the folder you copied. Then add a CSV list of the users you want to move (one line for each mailbox).
  3. Choose PST. Select PST as the output. It is an easy choice for Outlook. Contacts and calendars that a format can't take are saved as vCard and ICS files.
  4. Start the batch. Start the batch and open the log after it ends. If the batch stops, resume it, because the log shows which mailboxes finished.
  5. Compare the files. Open a few PST files in Outlook and compare the folders and dates with your Grommunio mail before you import anything.

Limitations: in the free trial the migrator moves 25 messages from each folder, which gives you room to test a few mailboxes before you plan the full domain. Also, I haven't tried the migrator's own upload against Microsoft 365, so the Office 365 side of this guide relies on PST files, which are a format that Microsoft documents on its own pages. I haven't timed a large batch either, which means a speed figure would be a guess. Time one mailbox yourself.

Turn your Gromox copy into PST files

Windows reads a copy of your Grommunio data and saves each mailbox on your list as a PST file.

Download Free Trial Select a Licence - From $999

Test two of your own mailboxes in the trial and open the PST files before you buy a licence.

Bring the PST Files Into Microsoft 365

If one person needs old mail, import the PST file into that user's mailbox from classic Outlook, using File, then Open & Export and Import/Export. For many users, use the Import service in Microsoft Purview. Its network upload is free and sends your PST files to a temporary Azure Storage location. No role group has the Mailbox Import Export role by default, so assign it first.

Keep every PST file under 20 GB and under 300 levels of nested folders, since Microsoft says it can't import a file with more levels. Our import PST to Office 365 guide covers the mapping file and the upload step by step.

What If Mail, Contacts or Calendars Are Missing in Microsoft 365?

1. Contacts and calendars are missing

Do this: An IMAP migration moves mail only, as Microsoft states. Save the contacts and calendars from your Gromox copy as vCard and ICS files. Then import the vCard and ICS files in Microsoft 365 or Outlook.

2. Old mail or large messages are missing

Do this: IMAP migration stops at 500,000 items in one mailbox and refuses a message above 35 MB. The PST import skips any item over 150 MB. Compare the mailbox with your Gromox copy and not with the live server (a reliable check, because your copy is fixed), because newer mail never reached your copy.

3. Microsoft cannot connect to Grommunio

Do this: Check that imap_support_tls is switched on, that port 993 (implicit TLS) is open and that the login is right. After 10 failed logins Gromox blocks a client by default, so wait a minute before you try again.

When a mailbox still differs from your copy, Univik support can look at it. Send your Grommunio version and the name of the user involved.

What Is This Grommunio Guide Based On?

I read the gromox-export manual page, the Gromox IMAP page and the Grommunio operations page on 14 November 2026. I also read Microsoft's IMAP migration page and the Microsoft Purview PST import overview on the same day. Univik's migration page was my fifth source, because each step should match the migrator. Forum posts stayed out, since a how-to needs a vendor page behind each number.

Key Takeaways
  • Grommunio has no export to Office 365 and gromox-export has no PST format. Mail can still arrive over IMAP or through PST files.
  • Microsoft's IMAP migration needs a live server and a login for each user. It moves mail only. A mailbox is capped at 500,000 items and a message at 35 MB.
  • A migrator reads a copy of /var/lib/gromox and saves PST files, so your old server can stay off while you import them.
  • Microsoft asks for PST files of 20 GB or less and skips any item over 150 MB.
  • Move two test mailboxes first and compare them with your copy before you change the MX record.

FAQ: Migrate Grommunio to Office 365

How do I migrate Grommunio to Office 365?

Start with Microsoft's IMAP migration if your Grommunio server is online. You can also save PST files from a copy of your Gromox data and import them into Microsoft 365. IMAP moves mail only, so plan the contacts and calendars separately.

Can Microsoft 365 migrate Grommunio mail over IMAP?

Yes. Microsoft 365 connects to a source that supports IMAP. Gromox offers IMAP on port 143 and port 993. You need a password or an admin login for each user and licensed mailboxes that already exist.

Does an IMAP migration move Grommunio calendars and contacts?

No. Microsoft says the IMAP migration moves mail folders but not contacts, calendar items or tasks. A migrator can save them from your Gromox copy as vCard and ICS files.

Can Grommunio export a PST for Office 365?

The gromox-export manual page names vCard, TNEF, GXMT, RFC 5322 and iCalendar as output types and no PST. A Windows migrator that reads your Gromox copy can save the PST files.

How large can a PST file be for the Microsoft 365 import?

Microsoft asks for PST files of 20 GB or less. The import skips any item over 150 MB and can't import a file with 300 or more levels of nested folders.

Do I need my Grommunio server online to migrate?

For Microsoft's IMAP migration, yes. For PST files, no, because the migrator reads a copy of your Gromox data on your Windows PC.

Can I test the Grommunio migrator for free?

Yes. The trial of Univik Grommunio Migrator moves 25 messages from every folder, so try a few of your own mailboxes first.

What happens to messages larger than 35 MB?

Microsoft's IMAP migration can't move a message over 35 MB. The PST import skips an item over 150 MB, so check large messages in your copy first.

Leena Taylor Paul

IMAP and PST limits follow the Microsoft Learn pages and the Gromox settings follow the Grommunio documentation, all read on November 14, 2026.

More Guides for Grommunio and Microsoft 365

Choose the guide that matches your Grommunio server or the next step on the Microsoft side.