How to Import PST Files into Office 365 Without Losing Folders
A step-by-step PST import method for Microsoft 365: inventory archives, choose Graph-based tooling, throttle batches, and verify item counts after each mailbox.
- Inventory PST size, password protection, and folder depth before you schedule the cutover.
- Manual Outlook drag-and-drop does not scale and rarely produces clean logs.
- Batch, throttle, and verify — Microsoft Graph imports fail quietly when you skip sampling.
- Keep the source PST until item counts and folder trees match in Exchange Online.
Why PST import is still a real project
PST files show up after laptop refreshes, departing employees, and “we exported everything to be safe” campaigns. They are convenient archives and awkward migration sources: large, sometimes corrupt, sometimes password-protected, and often full of nested folders users still expect to see in Outlook on the web.
Step 1 — Inventory before you move anything
See Office 365 Email Backup
Reliable mailbox backup and recovery for Microsoft 365 environments.
Learn more- Mailbox owner and target UPN in Microsoft 365
- File size and path (local disk vs USB vs file share)
- Password status and encryption
- Known corruption (Outlook already warns on open)
- Whether the PST is a complete mailbox or a topic archive
Skip this step and you will discover the 28 GB archive at 4 p.m. on cutover Friday.
Step 2 — Pick an import method that matches volume
| Method | Fits | Risk |
|---|---|---|
| Outlook import | One user, small PST | No enterprise log; easy to interrupt |
| Microsoft network upload / import service | Very large, well-planned batches | Lead time, shipping or WAN constraints |
| Graph-aware desktop import tool | IT-run batches with audit logs | Must respect throttling |
Step 3 — Prepare identity and permissions
The target mailbox must exist. Use modern authentication. Grant the migration account only the rights it needs. Confirm Conditional Access will not block the unattended job overnight.
Step 4 — Run a pilot
Pick two PSTs: one tiny, one awkwardly nested. Import to a test mailbox or a real user who can validate. Check:
- Folder hierarchy (including empty folders users still want)
- Item counts versus a PST viewer
- Calendar and contacts if they were stored in the PST
- Special folders (Sent, Deleted) mapping
Step 5 — Batch production with throttling in mind
Microsoft 365 will slow aggressive imports. Smaller batches, retries, and detailed logs beat a single “upload everything” job. Do not delete source PSTs until verification is signed off.
Step 6 — Protect what you just moved
A successful import is not a backup strategy. Once mail lives in Exchange Online, pair the project with Office 365 Email Backup so a later purge does not undo the work. For the import itself, see Import PST to Office 365.
Recommended next step
Import PST to Office 365
Migrate PST archives into Microsoft 365 with audit-ready controls.
