Quick Answer
hMailServer to PST takes two methods because the mail sits in .eml files while the account and folder names sit in a database. Use Outlook over IMAP while the server is up. If the server is down or you have many accounts, use a Windows converter on a copy of the Data folder together with its database.
Without the database copy the .eml files still export but the folder tree may come out flat.
If you open the Data folder on your hMailServer machine, you will find a pile of .eml files and no mailbox. Each file is one message. Nothing in the folder tree tells you which account owns it, which is why hMailServer to PST needs a plan before you start. Microsoft's export article shows what Outlook can save once the mail has loaded.
You have two real ways to do this. Outlook can sign in to each account over IMAP and export it once its mail has loaded. A Windows converter can read a copy of your Data folder together with a database backup and save one PST for each account. When the server is working and you have three accounts, the first method is fine. When the server has crashed or you have thirty accounts, the second method saves you days of repeated sign-ins and long first syncs.
- If the server still works and you have a few accounts, export through Outlook over IMAP with each account password, because that method needs nothing beyond Outlook.
- If the server has crashed or you have many accounts, take a copy of both the Data folder and its database, move them to a Windows PC and convert them so that each account gets its own PST.
- If you need only one message, you don't need any export at all, because you can open its .eml file in Outlook and read it there.
Why Is hMailServer to PST Hard With Only the .eml Files?
hMailServer stores each message as its own .eml file inside a folder for its domain. An .eml file is plain text in the RFC 5322 message format, so a mail program like Thunderbird or Outlook can read one file. The trouble starts with the count. A busy server leaves you a long list of files that are named for the message and not for the person who owns it.
The names that tie a file to an account and a folder sit in the hMailServer database. Exporting from the files alone usually gives you mail without its folder tree, which is a safe result for a single message and a poor one for a whole account. The database can be the built-in engine, MySQL, MS SQL or PostgreSQL, so you should find out which one your server uses before you start.
Who Needs hMailServer Mail as PST Files?
Four situations usually lead to a PST request.
- A Windows admin moving to Microsoft 365 Your users will work in Outlook and each account needs a PST to import.
- An admin after a crash The hMailServer service no longer starts and the Data folder is all you have left.
- A small office owner Your old mail server is being switched off and you want one file for each employee.
- A support engineer You have to give a user who is leaving a copy of their mail that opens in Outlook.
Which Method Fits Your hMailServer to PST Export?
Three methods get hMailServer mail into Outlook. Each one asks something different of you, so the table shows what you give and where the method stops.
| Method | What you give | Where it stops |
|---|---|---|
| Outlook over IMAP | The server stays running and every account signs in to Outlook with its own password | One profile for each account and a long first sync for large mailboxes |
| Single .eml files | You open a message file from the Data folder in a mail program | Fine for one message and unrealistic for a whole account |
| Windows converter | You copy the Data folder and the database and select the accounts and the PST format | You need both copies. A licence gives you the full export |
I'd use Outlook over IMAP when your server still works and you have a few accounts. If your server is down, that method will not work, because IMAP needs the hMailServer service running and a password for every account that you want to export. The same limits apply when you export IMAP to PST from any other server.
Export hMailServer to PST From Outlook in Five Steps
Outlook sees hMailServer as an ordinary IMAP server, so you enter the server name and the account password before Outlook downloads the folders, which is easy to set up but slow to finish for a large mailbox.
- Check the service. Confirm that the hMailServer service is running and that IMAP is enabled under Settings, Protocols and IMAP in hMailServer Administrator. Note the IMAP port, which is usually 143 or 993 with SSL.
- Add the account in Outlook. Use File and Add Account in classic Outlook, choose manual setup and enter the mailbox address, the server name and the port.
- Wait for the sync. Let Outlook finish loading every folder. Microsoft's article says to wait until all your email appears before you export, so a large account can keep you waiting for hours.
- Start the export. Select File, Open & Export and Import/Export. The wizard offers Export to a file first. Its next page lists Outlook Data File (.pst).
- Save and compare. Select the account and keep Include subfolders checked. Set a location, then select Finish. Finally, open the new file and check that its folder counts match the account.
Note: in classic Outlook you have to repeat all five steps for every account. Each account needs its own password. If you manage many accounts, you should expect this method to take most of a week.
Can You Open the Data Folder's .eml Files Straight in Outlook?
You can open a single .eml file in Outlook and read the message, which makes the Data folder a quick and safe way to get one or two emails out. For an account with thousands of messages the idea breaks down, because Outlook has no way to learn which folder each file came from. Every message would land in one place and you would have to sort the mailbox by hand.
If you only need one message, find its file and open it. When you need a whole account with its folder tree, you need the database that stores those names.
Convert an hMailServer Data Folder Copy to PST on Windows
Univik hMailServer Converter opens a copy of your Data folder on a Windows PC and groups its .eml files into accounts. If you add a copy of the database, the exported mailboxes keep their real account and folder names. Because the converter reads copies that open read-only, your hMailServer machine can stay switched off and your originals stay unchanged.
- Copy the Data folder. If you can, stop the hMailServer service first. Then copy the whole Data folder to your Windows PC.
- Copy the database. Ask your database admin for a backup of the hMailServer database, whether it sits in the built-in engine, MySQL, MS SQL or PostgreSQL. Keep the backup next to the Data folder copy.
- Open both copies. Start the converter and add the Data folder. When you add the database too, accounts and folders appear with their real names.
- Select accounts. Check the accounts you need. Read any message in the preview before it is saved. A date range limits the export when you only need recent mail.
- Choose PST. Select PST, set an output folder and start the export. Then open one file in Outlook and check its folders.
Limitations: each folder exports 25 messages in the trial. If you skip the database copy, the files still export but the folder tree may come out flat. I haven't timed a large Data folder, so export two or three accounts and open them in Outlook before you plan a batch for all thirty.
Read your Data folder copy together with the database copy and receive a PST for every account you select.
Download Free Trial Select a Licence - From $999Export one account with the trial and open it in Outlook before you start the full batch.
What If the Exported Accounts Look Wrong?
Do this: The export probably started without the database copy. Add a backup of the hMailServer database next to the Data folder copy and export that account again.
Do this: IMAP needs the account password. If you have lost it, the Data folder method avoids the sign-in because it reads the files directly.
Do this: Check that you copied the folder for the right domain. If the Data folder copy is incomplete, copy it again while the service is stopped.
If an account still comes out wrong, send Univik support your hMailServer version and the account name.
Where Does the hMailServer Storage Detail Come From?
I checked two sources on 14 November 2026. Microsoft's export article gave me the Outlook export path and the advice to wait for the sync while the RFC 5322 text gave me the .eml format. The hMailServer storage details come from Univik's own converter page, because the vendor documentation was not available to me, so you should confirm your folder layout on your own server. I have no timing for a large Data folder.
- hMailServer stores each message as its own .eml file. The account and folder names sit in the database.
- Outlook over IMAP exports one account at a time and needs the service running and every password.
- A single .eml file opens in Outlook, but a whole account with folders needs the database as well.
- Copies of the Data folder and database convert to one PST for each account on Windows.
- Check one finished file in Outlook against the account before you switch off the old server.
FAQ: Export hMailServer to PST
How do I export hMailServer to PST?
Sign in to each account from classic Outlook over IMAP, then export it to an Outlook Data File (.pst) with Import/Export. You can also use a Windows converter that reads your Data folder together with a database backup.
Where does hMailServer keep its email?
Each message is an .eml file in the Data folder, filed under a folder for its domain. The hMailServer database keeps the names of the accounts and folders.
Can I open hMailServer EML files in Outlook?
Yes, a single .eml file opens in Outlook. A whole account is a different matter, because the folder tree is not in the file names and Outlook cannot rebuild it.
What does the database copy add to the export?
The database says which account and folder each message came from, so without it the files still export but the folder tree may come out flat.
Is a PST export possible with the hMailServer service stopped?
Only with a converter. Outlook depends on IMAP, so the hMailServer service must be up, while a converter that reads a Data folder copy works with the server off.
Do I need every account password for the export?
Outlook needs the password of each account. A converter that reads the Data folder copy does not sign in, so it does not need the passwords.
Can I test the hMailServer converter for free?
Yes. Univik hMailServer Converter exports 25 messages per folder in its trial, so you can look at the result in Outlook before you buy.
What should I check in an exported hMailServer PST?
Look at the folder list in Outlook first and compare it with the account. Then open one folder with attachments before you switch off the old server.
