Email Migration

Move an Exchange 2016 Archive Mailbox to Microsoft 365

Camila MilosovichCamila Milosovich Nov 22, 2026 868 views

Question details

Move the contents of an Exchange 2016 on-premises archive mailbox to Microsoft 365 without first moving the primary mailbox.

Move an Exchange 2016 Archive Mailbox to Microsoft 365
Product
Microsoft Exchange Server 2016 and Microsoft 365
Device & OS
not provided
Scenario
An organization wants to transfer an existing In-Place Archive while keeping the user's primary mailbox on-premises.
Observed behavior
The desired outcome is to make the existing archive contents available in Microsoft 365 without migrating the primary mailbox first.
Before you start

Confirm that the user has an accessible Microsoft 365 destination mailbox or archive, sufficient storage, and the permissions needed to export and import the data. If the primary mailbox will remain on-premises, verify that the hybrid configuration and licensing support the intended cloud archive.

Solution 1Recommended

Export the archive to a PST file and import it into Microsoft 365

Use a PST export to transfer archive contents without moving the primary mailbox first.

This transfers mailbox data rather than directly moving the existing archive mailbox. The available import destination depends on the user's Microsoft 365 and hybrid configuration.

1
Export the archive

In classic Outlook, open File > Open & Export > Import/Export. Choose Export to a file, select Outlook Data File (.pst), and select the on-premises archive with Include subfolders checked.

2
Save the PST file

Choose a secure location for the PST file, select Finish, and wait for the export to complete.

3
Import to the destination

In an Outlook profile that can access the Microsoft 365 destination, open File > Open & Export > Import/Export and choose Import from another program or file. Select Outlook Data File (.pst), browse to the exported file, and choose the intended mailbox or archive folder.

4
Check the imported data

Open the destination mailbox or archive in Outlook and compare its folders and messages with the source archive. Check for missing items and confirm that the primary mailbox remains on-premises.

Export the archive to a PST file and import it into Microsoft 365
Confirm the destination first: Importing into a cloud archive requires an accessible, appropriately configured archive. The import does not automatically preserve every mailbox-level setting or policy.
Free Microsoft Office alternative

Document your Exchange archive migration with WPS Office

WPS Office is a free, lightweight, and easy-to-use Microsoft Office alternative with a familiar interface and compatible file formats for sharing migration plans and checklists. It does not migrate Exchange mailboxes or import PST files; use Microsoft tools for those tasks.

Create an Exchange archive migration checklist in WPS WriterOpen and edit Microsoft Word DOCX and Excel XLSX filesUse a familiar interface for an easier transition from Microsoft OfficeWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Can I transfer the archive contents without moving the primary mailbox?

Yes. Export the archive to a PST and import it into an accessible Microsoft 365 destination. If the primary mailbox stays on-premises, first verify that your hybrid configuration supports the intended cloud archive.

Does a PST export directly move the archive mailbox?

No. A PST export transfers mailbox contents, not the existing archive mailbox itself. Mailbox-level settings and policies may need separate review.

How do I include archive subfolders in the export?

In classic Outlook, go to File > Open & Export > Import/Export, choose Export to a file and Outlook Data File (.pst), then select the archive and check Include subfolders.

Can an administrator import the PST instead of using Outlook?

Yes. An administrator with the required permissions can create a PST import job under Data lifecycle management > Import in the Microsoft Purview portal, upload the file, and map it to a supported destination.