Archive Mailbox Migration to Office 365: A Secure Guide for 500GB+ Data

Limits That Shape a 500GB+ Archive Move

Five figures from Microsoft’s documentation decide most of the plan, so it helps to see them side by side before you pick a route.

Items	Microsoft Figure	What it means for you
Archive size once enabled	100GB	Anything larger needs auto-expanding archiving
Auto-expanding archive	Up to 1.5 TB	Storage is provisioned on demand, not upfront
PST size for import	No larger than 20 GB	Bigger files slow the import
Data per import into an archive	100 GB maximum	Larger archives need several imports
Import rate	About 24 GB a day per mailbox	Not guaranteed, so treat it as an estimate

Run those numbers against one 500 GB archive. You’d need at least 25 PST files, at least five separate imports, and roughly three weeks of import time at the quoted rate. Because the rate applies per mailbox, spreading 500 GB across many users shortens the calendar. A single oversized archive gets no such relief.

Checks Before You Move Online Archive Mailbox to Microsoft 365

• Source location: Find out whether the archive sits on-premises, in a hybrid setup, or already in Exchange Online. That decides which route below is open to you.
• Destination archive: Enable the archive for every target user. Past 100 GB, turn on auto-expanding archiving early, because extra storage can take up to 30 days to provision.
• Holds and retention: With auto-expanding archiving on, a hold or retention policy lifts the archive quota to 110 GB. Read the policies before estimating capacity.
• Safety copy: Keep an untouched PST copy until users confirm their history is intact.

Move an Exchange Archive Mailbox to Office 365 Using a Native Hybrid Move

Where a hybrid deployment already exists, Microsoft’s mailbox move is the shortest path. Data travels server to server, so no PST files are involved.

How to Migrate Archive Mailbox to Office 365 in a Hybrid Setup

1. Confirm the hybrid configuration and a reachable migration endpoint. Running Get-MigrationEndpoint in Exchange Online PowerShell lists it.
2. In the Exchange admin center, start an onboarding batch and choose whether to move the primary mailbox with its archive, or the archive alone.
3. For per-user control, run New-MoveRequest with the -Remote, -RemoteHostName, -RemoteCredential, -TargetDeliveryDomain, and -ArchiveOnly parameters.
4. Watch the batch through completion, then sign in to a test mailbox and check the archive folders.

The catch is the plumbing. You need a working hybrid setup, and duplicate archives cause trouble. An on-premises archive and a cloud archive sharing one ArchiveGuid isn’t supported, and the move fails on purpose to protect the data. Microsoft treats an on-premises primary mailbox with a cloud archive as the only supported split.

Transfer Archive Mailbox to Office 365 Through PST Files

When there’s no hybrid link, or you need to filter the archive before import, PST becomes the carrier. Microsoft Purview’s Import service accepts the files, and its mapping file carries an IsArchive parameter. Set it to TRUE, and the data lands in the user’s main archive mailbox. For more details on exporting mailbox data to PST, see our guide on Export Office 365 Email to PST.

That detail explains the 100 GB ceiling. Imports don’t target auto-expanding storage, since that storage is provisioned on demand. So split a large archive into date-based batches that each stay under 100 GB, and allow time for the archive to expand between rounds.

Extracting the Archive with DRS Softech Export Microsoft 365 to PST Tool

Teams that transfer archive mailboxes to Office 365 by PST spend most of their effort on the export. DRS Softech Export Microsoft 365 to PST Tool covers that stage. It runs on localhost, reads Exchange Online, on-premises Exchange, and hybrid sources over EWS, and lists Primary Mailbox, Online Archive, Public Folder, and Shared Mailbox as selectable sources. An Exchange Online Archive Mailbox can therefore be picked per user through user mapping.

1. Choose authentication. Single User OAuth suits one mailbox. For many, Client ID & Secret uses a Microsoft Entra ID app registration (Client ID, Client Secret, Tenant ID, and Admin Email) plus a CSV of mailboxes. Application permissions need admin consent.
2. Select the source. Pick Online Archive, map users, and clear unneeded folders in the hierarchy view.
3. Apply filters. Date range, duplicate removal, item types, and empty-folder exclusion are all available. Use the date range to divide a large archive into smaller import batches.
4. Split and start. Turn on Split PST by size, keep each file at or under 20 GB, set the output location, and run the export.
5. Track the run. Follow the Active Tasks dashboard, then open All Reports for total, migrated, and failed item counts.
6. Rerun safely. If a run is interrupted or repeated, enable Skip Previously Migrated so items handled earlier aren’t processed twice.

The free version exports up to 500 emails per folder, which is enough for a pilot on folder hierarchy. For teams repeating this across dozens of mailboxes, having filters, splitting, and reports in one interface keeps each run consistent. That consistency is easy to lose when the same controls are stitched together from separate scripts.

Native Hybrid Move vs PST Route at a Glance

Factor	Hybrid Manual Method	PST route with DRS Softech Tool
Source needed	Hybrid deployment with a migration endpoint	Exchange Online, on-premises, or hybrid
Content control	Archive alone, or primary plus archive	Folder, date range, and item-type filters
Large archives	Server-side move, no PST sizing	Split PST by size, then import within Microsoft’s limits
Bulk handling	Migration batches	CSV mapping with Client ID & Secret
Progress record	Batch and move status	Active Tasks dashboard and All Reports

Conclusion

Archive mailbox migration to Office 365 at 500 GB and above requires careful planning and the right migration route. A native hybrid move works when the required hybrid setup is already in place. For migrations that need filtering, PST splitting, and detailed reporting, the PST route with DRS Softech Export Microsoft 365 to PST Tool provides these controls. The free version can also help test the process with one mailbox before handling larger archives.

Frequently Asked Questions