Univik hMailServer Migrator for Windows

hMailServer Migration Tool Move emails in bulk from a copied data folder to a new server

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.

  • Reads the Data Folder: The .eml files of your copy move. A database copy adds the account and folder names.
  • Whole Server in One Batch: Every domain and account on your list goes together.
  • Two Ways Out: IMAP upload to the new server or PST, EML and MBOX files.
  • Bad Files Logged: An unreadable .eml file is skipped and listed. The batch goes on.
Software box of the Univik tool that moves hMailServer emails

 Before You Download

What Univik hMailServer Migrator Needs and Gives File format, routes, limits and price

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

Six Features of the hMailServer Migrator Built for moving a whole server

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.

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.

Reads .eml Files From the Data Folder

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.

Reads Names From the Database Copy

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.

Uploads to an IMAP Server

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.

Saves PST, EML or MBOX Files

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.

Lists Unreadable Files in a Log

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

Why Admins Migrate From hMailServer With a Separate Tool Mail sits in raw files and the last release dates from 2021

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

hMailServer to IMAP Migration and Three File Formats What happens on each route

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.

hMailServer to a New Mail Server

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.

hMailServer to Outlook

Select PST when the mail should end up in Outlook. You import the PST files there after the batch.

hMailServer to an Archive

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

What the hMailServer Migrator Opens Two copies that work together

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

How to Use the hMailServer Mailbox Migration Tool Three steps from copied folder to finished move

Before you start, stop the hMailServer service and copy its data folder.

1

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.

2

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.

3

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.

Download the Free Trial

hMailServer migration trial, Windows edition: 25 messages from each folder.

 Free Trial

hMailServer Migration Tool Free Trial and Licence 25 messages to test and a licence to finish

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

Planning the Day Your hMailServer Migration Goes Live Fresh copy, DNS timing and a fallback

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

Checking the Target After Your hMailServer Migration Three checks and four likely problems

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.

Four Likely Problems

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

Who Needs hMailServer Migration Software?

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

Limits of the hMailServer Migrator Four things to know first

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

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

File Copy, Microsoft IMAP Migration or an hMailServer Migration Tool? Names, limits and output

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

Before You Install hMailServer Migrator: Requirements A Windows PC, two copies and a target account

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.

SoftwareUnivik hMailServer Migrator 6.11 for Windows
TypeEmail migration tool
ReadsThe .eml files of a copied data folder and the database copy
Moves toIMAP upload or PST, EML and MBOX output
Mailbox listCSV file, one line for each account
AlsoSeveral accounts per batch, resume after a stop, a log of skipped files
DownloadThe same setup file as Univik hMailServer Mail Recovery
TrialStops at 25 messages in a folder
LicenceOne payment, from $999

 Questions

hMailServer Migration Tool Questions Answers on files, databases, routes, Mac, trial and price

hMailServer stores mail as .eml files, so a copy of those files is the usual starting point for a move out. Univik hMailServer Migrator reads that copy and sends the mail to an IMAP server or builds files in PST, EML or MBOX format.

Stop the hMailServer service. Copy the data folder and, if you can, the database. Select the copies on a Windows PC and add your mailbox list. Choose an IMAP server and enter its host, port and accounts. Finally start the batch and open the log.

The migrator sends mail to an IMAP server or creates PST, EML or MBOX files. A direct Office 365 or Gmail upload isn't part of what Univik claims.

This migrator has no direct upload to either service. For Outlook, create PST files and import them there.

The whole list goes through in one batch. Univik hasn't timed a big server yet. Time a few of your own accounts in the trial before you fix a cutover date.

Yes. Select the copied data folder on a Windows PC. The migrator reads the .eml files itself, so no hMailServer install is needed.

hMailServer stores each message as an .eml file in a data folder, in subfolders for the domain and the account. The names of accounts and folders are stored in the database. Copy the folder and the database and select the copies.

The database copy is optional. It gives the account and folder names. Without it the migrator still reads the .eml files, but folder names on the target may be generic.

The migrator skips the unreadable file and lists it in the log. The rest of the batch goes on.

Yes. Use resume and the batch continues. The log lists what was already done.

No. Windows 11 or Windows 10 is required. On a Mac, bring a copy of your hMailServer files to a Windows PC first.

Yes. Press the Free Download button in the page header and test one account with 25 messages per folder. Buy a licence to move everything.

Licences start at $999 and you pay once. Univik's 30-day refund policy applies to each purchase.

Yes. Univik offers hMailServer migration services for admins who want a person to plan the move.

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.