Moves Every Domain on Your List
When your list names the accounts of several domains, they move in one batch. Univik has not timed a big server, so try a sample of your own accounts in the trial first.
Univik hMailServer Migrator for Windows
Univik hMailServer Migrator is an hMailServer migration tool for Windows that moves every account on your list in one batch. It reads the .eml files of a copied data folder, then either uploads the mail to the new IMAP host or builds PST, EML or MBOX files. You don't need hMailServer on the PC.
Free TrialBulk Account MovesNo Mail Server NeededWindows 10 and 11
*The free trial installs from the same setup file as Univik hMailServer Mail Recovery and moves 25 messages per folder in each mailbox. A one-time licence starts at $999. Univik's 30-day refund policy covers each purchase.
Before You Download
If you are about to replace an hMailServer, these five numbers show what the migrator reads, where it sends your mail, which limit applies to IMAP migration and what a licence costs.
.eml
Message Format
hMailServer stores each message as a raw .eml file. The migrator reads those files from your copy.
2
Routes
One upload route over IMAP and one file route with three formats.
500,000
Microsoft IMAP Limit
Microsoft caps an IMAP migration at 500,000 items in a mailbox and 35 MB on the largest single message.
25
Test Messages
The trial moves 25 messages per folder so you can test an account.
$999
Licence From
Paid once, from $999.
Key Features
With several domains on one hMailServer, you give the migrator a single data folder copy and a list of accounts. A log tells you how the batch ended.
When your list names the accounts of several domains, they move in one batch. Univik has not timed a big server, so try a sample of your own accounts in the trial first.
hMailServer stores each message as a raw .eml file in a subfolder for its domain and account. The migrator reads those files from your copy, so the service never has to start.
Account and folder names come from the hMailServer database. If you copy the database with the data folder, the migrator uses it to name each account and folder on the target.
Give the migrator the host and port of the new server and a login for every mailbox. Folders are created on the target as the mail arrives, so your users see the layout they know.
Choose PST, EML or MBOX instead of the upload when the new platform imports files. The EML route keeps each message as one file, as hMailServer stored it.
A damaged .eml file does not stop the batch. The migrator skips it and lists it in the log, so you know which messages to check in the original folder.
The Problem First
The last hMailServer release is version 5.6.8 from March 2021, so many admins plan a move to a maintained server. If you plan the same, two facts about the way hMailServer stores mail shape your options.
Problem 1: Mail and Names Live in Two Places
hMailServer saves each message as a raw .eml file in a domain and account subfolder. The account and folder names come from its database, which can be MySQL, MS SQL or PostgreSQL. A plain file copy does not tell you which account or folder a message came from.
Problem 2: IMAP Migration Has Hard Limits
Microsoft's IMAP migration page lists a cap of 500,000 items in a mailbox and 35 MB on the largest single message. That migration moves mail only and needs the source server up, because IMAP reads from it.
The Fix: Read the Copied Files Directly
Univik hMailServer Migrator opens your copy of the data folder and, if you have it, the database copy. The service can stay stopped. Your list names the accounts to move. The migrator then sends each one to the target you chose.
If you only need a few accounts from a server that still works, a mail client can copy them over IMAP. If your server is old, offline or damaged, a copy of the data folder is a firmer start. When the files themselves are damaged, begin with Univik hMailServer Mail Recovery.
Routes Out
Mail is what Univik's hMailServer email migration tool moves. It has one upload route plus three file formats.
| Route | What happens | Fits |
|---|---|---|
| IMAP server | Mail goes up folder by folder | A new mail server that accepts IMAP logins |
| PST files | Mail is saved in PST format | An import into Outlook |
| EML files | One .eml file for each message | An archive or an import into another program |
| MBOX files | One MBOX file for each folder | Thunderbird and other MBOX readers |
RFC 9051 is the IMAP standard. You can read it at the RFC Editor. A direct Office 365 or Gmail upload isn't part of what Univik claims for this migrator.
Choose IMAP server and type the address and port of the receiving server. Any server that accepts IMAP logins and mail uploads can take the accounts, including a newer hMailServer.
Select PST when the mail should end up in Outlook. You import the PST files there after the batch.
Select EML or MBOX if you only need the mail on disk. EML keeps the one-file-per-message layout and MBOX gathers each folder into one file.
What It Reads
| Copy | What it gives the migrator |
|---|---|
| Data folder copy | The .eml message files in their domain and account subfolders. This is the copy you can't skip. |
| Database copy | Account and folder names from MySQL, MS SQL or PostgreSQL. It is optional. With it, the target shows the names your users know. |
| Several domains | Every domain folder in the copy. Your mailbox list names the accounts that move. |
Three Steps
Before you start, stop the hMailServer service and copy its data folder.
Select the Data Folder Copy
Start Univik hMailServer Migrator and select the copied data folder. Add the database copy if you have one. Then load a CSV file with one line for each account to move.
Enter the Target Server
For an upload, choose IMAP server and type its address, its port and a login for every mailbox. To get files instead, choose PST, EML or MBOX.
Launch the Batch and Check the Log
Press Start and the batch works through your list. If it stops, resume it. At the end, scan the log for skipped files and open a few accounts on the target before you switch your MX record.
hMailServer migration trial, Windows edition: 25 messages from each folder.
Free Trial
Download the trial before you plan your cutover. It shows how your own accounts arrive.
| Item | Trial | Licence |
|---|---|---|
| Per-folder cap | 25 messages | None |
| Price | $0 | From $999, once |
| Installer | The setup file shared with Univik hMailServer Mail Recovery | The same file |
| Money back | Nothing to refund | Thirty days, per Univik's policy |
The trial reads your copy the same way a licence does, so it previews the full batch.
Buy a licence from $999 and the 25-message limit goes away. For a large server, the buy page lists the licence options.
Cutover
Cutover day is when senders start delivering to the new server.
Stop the Service Before You Copy
Stop the hMailServer service before you copy anything. Mail that arrives during the copy may be missing from it.
Lower the MX TTL Early
Lower the TTL on your MX record a day ahead. When you change the record, senders then follow it sooner.
Keep the Old Server Reachable
Keep the old server and your copy for a few days if you can. Users who miss a message can look there.
Confirm three points first. The new server accepts IMAP logins for each target account. Your list names each account once. A test account shows the right folders on the target.
Target Checks
When the batch ends, look at the target before DNS changes.
Compare Message Counts
Look at two or three accounts on the target. Their folder counts should match your copy.
Check Folder Names
If you used the database copy, folder names should match what your users saw in hMailServer. If you did not, check them yourself.
Update MX and SPF
Switch the MX record as the final step. Then adjust SPF so your new server is accepted as a sender for the domain.
Each row gives the cause that is most likely and the next step.
| Symptom | Next step |
|---|---|
| Some files are skipped | Open the log. The migrator lists each unreadable .eml file there, so you can check those messages in the original data folder. |
| Folders have generic names on the target | That usually means no database copy was selected. Add the database copy and start the batch again. |
| The target rejects the upload | Recheck the address, the port and the login of that mailbox. Also confirm the new server permits IMAP logins for it. |
| The batch stops | Resume it. The log lists what finished first. |
Who It Is For
Univik also offers hMailServer migration services, where a person plans the move with you.
Admins Replacing an Old Server
If your hMailServer sits on an aging Windows server, you can move the accounts before the hardware fails.
Small Companies Changing Mail Hosts
If you move to a host that accepts IMAP, list your accounts once and let the batch fill the new mailboxes.
IT Consultants With Several Clients
If you look after hMailServer for clients, keep one list for each client. You then move one client at a time.
Limits
Trial
25 Messages in the Trial
The trial stops at 25 messages in each folder. Use that sample to check one account, then buy a licence to move everything.
Setup
No New Server Setup
The migrator moves mail out of hMailServer. It does not install the new server or change your DNS records.
Mail Only
The migrator moves messages. Domain settings, aliases and rules are not part of the migration, so note them down before the old server goes.
Windows
A Windows PC Is Needed
A 64-bit PC with Windows 11 or Windows 10 and .NET Framework 4.8 is required. Bring the data folder copy to that PC.
Side by Side
Look at names, limits and output before you choose.
| Compare | Copying files by hand | Microsoft IMAP migration | Univik hMailServer MigratorTRIAL |
|---|---|---|---|
| Account and folder names | Missing without the database | Read over IMAP | Read from the database copy |
| Server must be up | No | Yes, IMAP reads from it | No, a copied folder works |
| Message limits | None | 500,000 items in a mailbox and 35 MB on the largest message | Trial: 25 messages per folder |
| Output | .eml files on disk | Mail in Microsoft 365 | Upload over IMAP or as PST, EML and MBOX files |
| Unreadable files | You find them by hand | Not covered on that page | Skipped and listed in a log |
Column two follows Microsoft's IMAP migration page, which Univik read in November 2026. Column one is Univik's own description of a plain file copy.
Checklist
Four items decide whether your first batch succeeds.
Windows 11 or Windows 10
.NET Framework 4.8 (or 4.8.1) is part of Windows 11. Windows 10 has it from version 1903.
hMailServer Not Required
The migrator reads the files itself, so your PC needs no hMailServer install.
A Copy of the Data Folder and the Database
Stop the service, copy the data folder and, if you can, copy the database too. Select the copies and never the live folder.
Target Logins
An IMAP target needs an address, a port and a login for every mailbox on the new server.
| Software | Univik hMailServer Migrator 6.11 for Windows |
| Type | Email migration tool |
| Reads | The .eml files of a copied data folder and the database copy |
| Moves to | IMAP upload or PST, EML and MBOX output |
| Mailbox list | CSV file, one line for each account |
| Also | Several accounts per batch, resume after a stop, a log of skipped files |
| Download | The same setup file as Univik hMailServer Mail Recovery |
| Trial | Stops at 25 messages in a folder |
| Licence | One payment, from $999 |
Questions
Written by the Univik Team Email and file software since 2013
The Univik team wrote this page. The facts about hMailServer's file layout come from Univik's own build. The limits for IMAP migration link to the Microsoft page they come from.
Updated on 14 November 2026
Univik Since 2013Read-Only AccessIMAP and File Output30-Day Refund Policy
hMailServer is a name owned by its respective owner. Univik isn't affiliated with it.