Email Migration

Migrate Axigen to Office 365 from a running server or a working directory copy

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

Quick Answer

Axigen has no function that sends a mailbox to Office 365. Two ways move your mail. Microsoft can sign in to your live Axigen server over IMAP and copy the mail, but it moves mail only and stops at 500,000 items for each mailbox. You can also copy the working directory and turn its .hsf containers into PST files. IMAP needs a running server and a login for each account, while a copy works with the server off.

Axigen documents its Automatic Migration as a way to bring mail in. It describes no way to send mail out.

If you look after an Axigen server and your company is moving to Microsoft 365, you will find that Axigen's Automatic Migration only brings mail into Axigen. The page describes no function that sends mail out. That leaves you two ways to reach Microsoft 365. Microsoft can copy mail over IMAP from your running server. A copy of your working directory can also become PST files that you import.

I'd decide by asking whether your Axigen server still answers. If it does and you have a login for each account, Microsoft's IMAP migration needs no extra program, which makes it an easy and quick start for a short list of accounts. When the server is down or you want files, the working directory copy is the safer start, because a program reads the copy and never needs your server.

Start with the method that fits your server
  • If your Axigen server is online and every account has a known password, let Microsoft 365 copy the mail over IMAP.
  • If your server stopped working or was switched off, copy the working directory from its disk and build PST files from that copy.
  • If you prefer not to do the move yourself, Univik also offers Axigen migration services for the whole domain.

Why Does Axigen Only Move Mail Into Axigen?

Axigen's Automatic Migration moves domains from another mail server into Axigen over IMAP. The same page describes no way to move mail out, so you can't point Axigen at Microsoft 365 and start a batch. Mail also sits in storage containers that Axigen alone opens, which makes a direct file copy useless as a mailbox, because Outlook and Microsoft 365 can't read the .hsf format on their own.

Axigen's storage page says container files have a two-digit hexadecimal name and the .hsf extension, for example 2A.hsf. Each domain uses at least three storages. A file named hsf.dat records how a storage relates to the others of its domain. If you copy only one folder, you may lose that link. Then your copy may no longer match the way Axigen expects to find its storages.

The IMAP door has Microsoft's limits. Microsoft's IMAP migration page lists 500,000 items for each mailbox and 35 MB for each message. It copies mail folders only. Contacts, calendar items and tasks are not part of it. It copies the newest mail first.

Who Moves Axigen Mail to Microsoft 365?

Does one of these match your move?
  • A hosting admin You manage Axigen for several customer domains and one customer is leaving for Microsoft 365.
  • An in-house admin Your company has chosen Microsoft 365 and your Axigen server will be switched off later.
  • A failed server Your Axigen machine no longer starts and its disk is the only copy of your mail.
  • One leaving user A manager needs one mailbox in Outlook before the account is closed.

Which Method Fits Your Axigen to Office 365 Migration?

Two methods are open to you. The table shows what each one needs.

MethodWhat you doWhat stops you
IMAP migration by Microsoft Microsoft 365 signs in to your running Axigen server and copies each mailbox folder by folder Needs a running server, a login for every account and mailboxes that already exist in Microsoft 365
Files from a working directory copy A Windows program opens your copy, reads the .hsf containers and saves PST, EML or MBOX files or uploads to an IMAP host Needs a licence for the full export on a Windows PC. A PST needs its own import step

I'd start with IMAP when your server is healthy and your list is short, since Microsoft does the copying for you. However, when the server is down, I'd use the copy, because Axigen's own documentation offers no other way to read the .hsf containers outside Axigen. Also, a copy lets you test two mailboxes (a reliable check) before you plan the whole domain.

Move two test accounts out of Axigen before you plan the whole domain. A mailbox that looks right in Microsoft 365 tells you the rest of your list will follow.

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

Move Axigen Mail to Microsoft 365 by IMAP in Five Steps

Our migrate IMAP to Office 365 guide covers the Microsoft screens, so these steps stay on the Axigen side.

  1. Check the IMAP listeners. Axigen listens on port 143 and, for implicit SSL/TLS, on port 993. Open the IMAP service settings in WebAdmin and check that the listener you need is active.
  2. Create the Microsoft 365 users. Add each person with a licence, because the mailboxes have to exist before the batch starts. If you move your domain, verify it with your registrar.
  3. Get a login for every account. Collect each password or use administrator credentials. Reset the passwords you don't know, then list your addresses in a CSV file.
  4. Review the error limit. The listener's error control sets a maximum number of invalid commands or failed sign-ins. A value of 0 switches the limit off. Check that value before a large batch.
  5. Start the batch and switch. Create the migration endpoint and the batch in the Exchange admin center. Compare a few mailboxes with Axigen, then change your MX record.

If a sign-in fails, Axigen's IMAP page may explain it, because each listener has its own list of allowed authentication types. The default ports article lists 143 for IMAP and 993 for IMAPS.

Turn an Axigen Working Directory Copy Into PST Files

Univik Axigen Mail Migrator takes the working directory that you copied and lists the domains and accounts inside it. It reads the .hsf containers with their hsf.dat files, so Axigen can stay off. It then saves PST, EML or MBOX files or uploads to an IMAP server that you name.

The migrator reads your copy on a Windows PC and never signs in to your old server.
  1. Stop and copy. Stop the Axigen service, then copy the working directory with every storage directory in it. A domain uses at least three storages, so a partial copy may miss one.
  2. Add the copy. Start the migrator and select your copied working directory. You can filter the list of domains and accounts that it shows.
  3. Choose PST. Load your CSV list of accounts and select PST. Preview one mailbox first.
  4. Start the batch. Start the batch and read the log when it ends. If the batch stops, resume it. Finally, note the time that one account took.
  5. Check the result. Open a few of the PST files in Outlook, then compare their folders with your Axigen accounts before you import anything.

Limitations: the free trial moves 25 messages per folder. The migrator needs Windows 11 or Windows 10 with .NET Framework 4.8. I haven't tested an upload from the migrator into Microsoft 365, so this guide uses PST files for the Microsoft side. I haven't timed a large directory either. If you plan a big domain, move two accounts first and note the time.

Turn your Axigen copy into PST files

Windows reads the .hsf containers of your working directory copy and saves each account on your list as PST files.

Download Free Trial Select a Licence - From $999

Move two accounts in the trial and open the files before you buy a licence.

Bring Your PST Files Into Microsoft 365

If you have one person to move, import the PST file from classic Outlook through File, Open & Export and Import/Export. If you have many accounts, use the Microsoft Purview Import service. Microsoft's overview wants each PST at 20 GB or less and says it skips any item over 150 MB. Step by step, our import PST to Office 365 guide walks through the mapping file.

What If Mail Is Missing or Microsoft Can't Sign In?

1. Microsoft cannot sign in to Axigen

Do this: When Microsoft reports a failed sign-in, check that the IMAP listener on port 993 is active and that the account password is right, since either one can refuse a login. The listener also has an error control limit, so a long series of wrong logins may block your batch.

2. Your copy shows fewer folders than expected

Do this: If your copy misses one storage directory, it often looks empty or incomplete, because a domain uses at least three storages and the migrator can only list what your copy contains. Copy the whole working directory again with the service stopped.

3. Old mail is missing in Microsoft 365

Do this: IMAP migration allows at most 500,000 items for each mailbox and 35 MB for each message. Compare the mailbox with your copy and not with the live server, because newer mail never reached your copy.

When a mailbox keeps looking wrong, Univik support can help. Send your Axigen version and the account involved.

What Is This Axigen Guide Based On?

I read four Axigen pages on 14 November 2026: the Automatic Migration page, the storage page, the IMAP service page and the default ports article. Next I read the Microsoft pages that cover IMAP migration and Purview PST import. Univik's migration page was my seventh source, since I wanted each step to match what the migrator offers. I left out forum posts, because a how-to needs a documented source behind each number.

Key Takeaways
  • Axigen's Automatic Migration moves mail into Axigen only, so mail reaches Microsoft 365 over IMAP or as PST files from a copy.
  • Axigen listens on port 143 and port 993 by default. Each listener has its own error control and authentication types.
  • Mail sits in .hsf containers. Each domain uses at least three storages, so copy the whole working directory.
  • Microsoft's IMAP migration moves mail only, up to 500,000 items and 35 MB for each message.
  • Before you change the MX record, compare two test accounts with your copy.

FAQ: Migrate Axigen to Office 365

How do I migrate Axigen to Office 365?

Let Microsoft 365 copy the mail over IMAP while your Axigen server is online. You can also build PST files from a copy of your working directory and import them. IMAP moves mail only and needs a login for each account.

Can Axigen send mail to Microsoft 365 by itself?

Axigen's Automatic Migration page describes a feature that brings domains into Axigen over IMAP. It describes no way to send mail out, so Microsoft's IMAP migration or a converted copy has to do it.

Which ports does Axigen use for IMAP?

Axigen's default ports article lists port 143 for IMAP and port 993 for IMAPS. The IMAP service page says the listeners cover all IPv4 and IPv6 addresses by default.

Where does Axigen keep the mail I need to copy?

Axigen keeps messages in container files that end in .hsf. Each domain uses at least three storages, so copy the whole working directory and not one folder.

What limits does Microsoft's IMAP migration have?

Microsoft lists 500,000 items for each mailbox and 35 MB for each message. It moves mail only and leaves contacts, calendar items and tasks behind.

Can I migrate Axigen mail with the server switched off?

Yes, from a copy. A migrator opens your copied working directory on a Windows PC, reads the .hsf containers and saves PST, EML or MBOX files.

Can I test the Axigen migrator for free?

Yes. The trial of Univik Axigen Mail Migrator moves 25 messages from each folder, so your own accounts can be tested before you buy a licence.

Can Univik move my Axigen domain for me?

Univik offers Axigen migration services to Microsoft 365 and Google Workspace. Read the services page for the scope. You can also use the migrator and the steps above yourself.

Leena Taylor Paul

Axigen facts follow four Axigen documentation pages and the Microsoft limits follow two Microsoft Learn pages, all read on November 14, 2026.

More Guides for Axigen and Microsoft 365

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