How to Migrate Archive Mailbox to Office 365 (Microsoft 365): Complete Guide

What Is an Exchange Archive Mailbox?

An archive mailbox is a second mailbox linked to a user account. It stores older messages away from the primary mailbox. Exchange calls this feature In-Place Archive.Users see the archive as a separate folder tree in Outlook. Admins use it to keep primary mailboxes small. It also helps with retention and compliance rules.

In Microsoft 365, the archive works the same way. The cloud version can grow far beyond the on-premises limit. Auto-expanding archiving can take storage up to 1.5 TB.

Why Migrate Exchange Archive Mailbox to Microsoft 365?

There are clear reasons to move archives to the cloud:

• You can retire old on-premises servers and cut hardware costs.
• Users get one mailbox view across every device.
• Admins manage retention from a single compliance portal.
• Storage limits are much higher than most local setups.
• Backup and patching become Microsoft’s job.

Prerequisites and Planning

Good planning prevents most migration failures. Check each item below before you begin.

• The target user needs an Exchange Online Plan 2 license. Plan 1 users can use the Exchange Online Archiving add-on instead.
• Create the cloud archive before the move begins. Turn on auto-expanding archiving if data may pass 100 GB.
• The migration admin needs Organization Management rights. Recipient Management rights also work for many tasks.
• Very large on-premises archives need extra planning. Archives above 240 GB are best handled in smaller stages. Test with a pilot user first.
• Exchange Online must reach your on-premises servers. This needs valid certificates & open firewall ports.

Method 1: Migrate Archive Mailbox to Office 365 (Microsoft 365) Using Exchange Hybrid

The Exchange hybrid deployment is Microsoft’s recommended route to transfer Exchange (In-Place) Archive Mailbox to Office 365. It moves the primary mailbox and archive together. Users keep working with little disruption.

Microsoft explains the full process in its guide on moving mailboxes between on-premises Exchange and Exchange Online. Read it before you start.

Step 1: Configure the Hybrid Environment

Run the Hybrid Configuration Wizard on your on-premises server. It links your organization with Exchange Online. It also sets up the sharing and routing features you need. Next, you have to enable the MRSProxy service. This service lets Exchange Online pull mailbox data from your servers. Then, use this command on the Client Access server:

Step 02: Audit the Source Archives

Make sure you check every archive before you move it. Note the size, item count, & GUID. Run this command to migrate Exchange Archive to Office 365 in the Exchange Management Shell:

Save the output to a CSV file. You will compare it with the target later.

Step 3: Enable the Cloud Archive

The user’s cloud mailbox needs an archive ready. Hybrid sync usually handles this. If it does not, enable it by hand. For a user already in Microsoft 365, run this in Exchange Online PowerShell:

For a remote mailbox, run this on-premises instead:

Microsoft documents this step in its article on enabling archive mailboxes. You can also read our guide on how to Enable or Disable Archive Mailbox in Office 365.

Step 4: Create the Migration Batch

Open the Exchange admin center. Go to Migration >> select Add migration batch. Choose Migration to Exchange Online. Then pick Remote move migration.

Add the users from a CSV file. The CSV needs one column named EmailAddress. Modern migration tools include the on-premises archive automatically. The archive travels with the primary mailbox. You can also use PowerShell:

To move only the archive, use the -ArchiveOnly switch. This is useful when the primary mailbox is already in the cloud.

Step 05: Monitor, Complete, & Verify

Track progress from the batch status page. Wait until the status shows Synced. Then complete the batch to finalize the move. Check progress with this command:

After the completion of process, and then verify the data. Compare item counts with your saved audit file. Sign in as a test user. Open Outlook and confirm the archive shows all folders. Finally, assign retention policies in Microsoft 365. These rules keep archiving automatic and compliant.

Common Problems and Quick Fixes

Problem	Likely Cause	Fix
Batch fails to start	MRSProxy is off	Enable MRSProxy on EWS
Archive missing after move	Cloud archive not enabled	Run Enable-Mailbox with-Archive
Migration is very slow	Large archive or low bandwidth	Move in smaller batches
Items skipped	Corrupt items in source	Raise BadItemLimit carefully
Authentication errors	Wrong endpoint credentials	Recreate the migration endpoint

Method 2: Professional Solution to Migrate Archive Mailbox to Office 365 (Microsoft 365)

Key Features

• Backs up primary, shared, public folder, & archive mailboxes in one session.
• Supports batch backup of many mailboxes at once.
• Keeps the original folder hierarchy intact in the PST file.
• Shows a preview of mailbox items before the backup starts.
• Filters data by date range or by item type.
• Removes duplicate emails using the To, From, Subject, and Body fields.
• Splits large PST files into smaller, manageable parts.
• Skips items that earlier sessions already backed up.
• Lets you rename destination folders during export.
• Includes or excludes attachments as you choose.
• Uses multithreading to shorten the backup window.
• Creates a log report for checking the process.

Supported Environments and Versions

The tool works with Exchange Server 2019, 2016, 2013, 2010, & older versions. Mixed and legacy setups are covered. It runs on Windows and Mac systems.

Each environment has its own backup mode:

• Exchange Online: This runs through cloud APIs. No local server is needed.
• On-premises: The data stays inside your own infrastructure. No internet link is required.
• Hybrid: Covers local & cloud mailboxes in a single session.

The hybrid mode suits organizations that are mid-migration. Both groups of users stay protected during the move.

Choose the Right Login Method

The tool offers two sign-in options. Pick the one that matches your role.

Point	Single User Login	Client ID and Secret
Best for	Individual users	IT admins and organizations
Login type	Interactive OAuth	Azure AD app registration
Setup time	A few minutes	Needs admin configuration
Client ID needed	No	Yes
Archive, shared, public folder	Supported	Supported

Feature availability can vary with tenant permissions and mailbox access rights.

Note: You can save PST files to a local drive, an external drive, or SAN and NAS storage.

After the export, open the PST in Outlook to confirm the data. For a manual option, read our guide on how to export Office 365 Archive Mailbox to PST.

Demo Version Limits

The free demo shows how the tool works. It processes up to 500 emails per folder. It handles up to 100 items per folder for contacts, calendars, tasks, and notes.

When Should You Use This Tool?

• You want a safe PST copy before the migration starts.
• Your archives are too large for one migration batch.
• You lack a complete hybrid setup.
• Some users are on-premises while others are already online.
• You need a long-term offline record for compliance.

Best Practices for a Smooth Migration

• Start with a pilot group of two or three users.
• Run migrations during off-peak hours.
• Back up archives to PST before you start.
• Make sure you do not delete source data until checks pass.
• Review retention policies before & after the move.

Conclusion

You can migrate archive mailbox to Office 365 (Microsoft 365) with confidence. Along with that, plan the licenses, permissions, & sizes first. Then use the hybrid batch method for a clean move. Add a PST backup for extra safety. The Cigati Exchange Server to PST Backup Tool backs up archive, primary, shared, and public folder mailboxes. It works across online, on-premises, and hybrid setups. Test with a pilot batch, verify the results, & then scale up.

Related Post