PST to Office 365 Migration for IT Admins: A Comprehensive Guide (2026)

If you’re managing a handful of mailboxes and working with clean files under 5 GB, Microsoft’s own Import Service will probably get you there. But if you’re dealing with large archives, corrupted files, dozens of users, or a compliance team that wants documentation—read on.

The Stuff That Actually Breaks PST Migration

Corruption — and Why Scanpst Won’t Save You

PST files are fragile. They weren’t designed for the way people actually use them—parked on network shares, opened over VPN, left running through laptop shutdowns, and grown to sizes Outlook was never intended to support. The result is structural damage: orphaned B-tree nodes, broken attachment chains, and header mismatches that scanpst.exe won’t touch.

Microsoft’s repair tool handles light surface damage. Anything deeper, it flags as unreadable and moves on. The bigger issue is what happens downstream: Outlook’s import wizard and Microsoft’s network upload path both silently skip corrupted items. No error. No count. No warning. You find out three weeks later when someone can’t locate a client’s email from 2020, and you have no way to know if it was ever there.

File Size: Where Things Start to Unravel

Microsoft recommends keeping PST files under 20 GB for the import service. That recommendation exists because above it, Azure Blob upload timeouts become common, import jobs stall mid-run, and partial ingestion happens with no clear failure message. Outlook’s native import gets unreliable well before that—above 4 or 5 GB, memory pressure causes hangs and crashes.

The reality in most organizations is that nobody’s been housekeeping PST files. You’ll find 50 GB archives, occasionally 80 or 100 GB ones. Splitting them manually works, technically, but it adds hours of prep, and every split operation is a chance to introduce new damage. Better to use something that reads large PSTs natively.

Exchange Online Throttling

This one catches people off guard. Exchange Online enforces EWS rate limits per mailbox — EWSMaxConcurrency defaults to 27 simultaneous connections, and there are per-mailbox message injection rate caps on top of that. Push data in too fast, and you start getting HTTP 429 responses. Push harder, and you get 503s. A migration tool with no throttling logic will either crash or stop silently.

Proper handling means reading the Retry-After header in the 429 response, waiting the indicated interval, and resuming from where you left off—not from the beginning of the PST. Tools that don’t do this produce partial migrations that are nearly impossible to reconcile afterward.

Basic Auth is Dead

Microsoft killed basic authentication for Exchange Online in October 2022. If you have any migration workflow, script, or tool that authenticates with a username and password over SMTP or EWS, it’s broken. The replacement is OAuth 2.0 via an Azure AD app registration. That means API permissions, client secrets, tenant IDs, and admin consent grants — not just credentials.

A lot of older tools added a half-baked OAuth layer on top of an architecture built for Basic Auth. It shows. If OAuth 2.0 support wasn’t in the tool from the ground up, you’d hit edge cases that only surface during an actual migration.

Managing 50 PST Files With No Audit Trail

Running mailboxes one at a time through a manual process at any real scale is a project management problem as much as a technical one. Human error compounds across every iteration. And when compliance comes back six months later asking which mailboxes were migrated, on what date, with what item counts, “we used the import wizard” isn’t going to cut it.

Microsoft’s Built-in Import Service: When to Use It, When to Skip It

For organizations with clean archives under 20 GB per file and IT staff comfortable running AzCopy from the command line, Microsoft’s Import Service works fine. Network upload goes through AzCopy to Azure Blob storage, and then you submit a CSV-mapped import job through the compliance portal.

The Process

• Compliance portal: Data lifecycle management > Import > Import PST files > New import job. Copy the SAS URL.
• Upload via AzCopy: azcopy copy “C:\PSTs\*” “<SAS-URL>” –recursive
• Build the mapping CSV: Workload, FilePath, Name, Mailbox, IsArchive, TargetRootFolder columns.
• Submit the import job in the portal. Monitor until status shows Completed.

Real Limitations

The Import Service doesn’t inspect PST files for corruption before ingesting them. Damaged items get skipped with no notification. There’s no throttling feedback — when the job hits a rate limit, it either fails or stalls without surfacing why. And the 20 GB ceiling isn’t a hard stop; it’s a soft recommendation that Microsoft’s own documentation acknowledges will cause problems when exceeded.

Drive shipping is available for organizations with bandwidth constraints — $2/GB for Microsoft to load the files. Workable for a one-time project, but it adds turnaround time and doesn’t fix any of the corruption or throttling issues.

Outlook IMAP Sync: Not a Migration Method

IMAP sync gets suggested in forums as a free workaround. It routes mail through an intermediate account and relies on Outlook syncing the data across. The problems: it only moves email, not calendar or tasks. It falls apart above 2-3 GB. It has no error handling for corrupted items. And it requires someone actively monitoring it throughout.

If someone on your team has a single small PST and needs it moved quickly and doesn’t care about calendar history, IMAP sync is fine. For anything larger or multi-user, it’s not a real option.

SysinfoTools PST Converter: How It Handles the Hard Cases

The PST to Office 365 Migration Software SysInfo was built for scenarios where Microsoft’s native options fall short: large archives, corrupted files, bulk mailbox jobs, and environments where the compliance team will ask questions afterward.

What It Actually Does Differently

• No Outlook dependency: The tool reads PST files directly on the migration machine without needing Outlook installed.
• Large file support: PST files larger than 50 GB can be processed without the need for a pre-split; the tool breaks each large PST into smaller streams rather than attempting to load all of it into memory at once. 
• Pre-migration integrity check: Prior to migrating any items, the tool goes through each PST and checks it for structural corruption and will flag any corrupt items. You decide whether to attempt repair or exclude them — with full visibility before the job starts.
• OAuth 2.0 native: Client ID, tenant ID, client secret — the tool handles the full Modern Authentication flow. No Basic Auth workarounds.
• Administrator impersonation: The tool allows you to run scripts on behalf of a user that has been assigned full_access_as_app. This means that you can target any mailbox within your tenant without having to collect the individual user’s credentials.
• Throttling logic: If the tool receives a 429 or 503 response from the Exchange server, it will automatically back off based on the value provided in the Retry-After header. When the job resumes, it will be started at the checkpoint and not at the beginning.
• Batch processing: You can map 50+ PST’s to 50+ target mailboxes during one job. Useful for running overnight.
• Full item fidelity: Emails, attachments, contacts, calendar events, tasks, notes — not just mail.
• Duplicate detection: Once the job has been completed, all duplicate items that were previously located in the target mailbox will be automatically identified and skipped.
• Completion report: Per-mailbox item counts, repaired items, skipped items with reasons. Exportable as CSV.

Azure AD Setup Before You Run Anything

This takes 15-20 minutes and needs to be done before you touch the migration tool.

App Registration

• Azure portal > Azure Active Directory > App registrations > New registration. Name it something identifiable — PST-Migration-SysinfoTools works. Supported account types: this organizational directory only.
• API permissions > Add a permission > Microsoft Graph > Application permissions. Add Mail.ReadWrite, Calendars.ReadWrite, Contacts.ReadWrite, Tasks.ReadWrite. Then APIs my organization uses > Office 365 Exchange Online > Application permissions > full_access_as_app.
• Grant admin consent. Every permission needs a green checkmark — don’t proceed without this.
• Certificates and Secrets > Create New Client Secret. Minimum Expiration: 12 months. The Value the moment it appears. It won’t show again.
• From the app Overview page, note the Application (client) ID and Directory (tenant) ID. These go into SysinfoTools during authentication setup.

Why Admin Impersonation Changes Everything at Scale

full_access_as_app lets the tool write to any mailbox in your tenant using one service account. You’re not chasing down user passwords or running separate auth flows per mailbox. For a 200-user migration, that difference is weeks of coordination versus an afternoon of mapping configuration.

Running the Migration

Before You Open the Tool

Get your PST inventory into a spreadsheet first — file paths, sizes, owning users, last modified dates. Confirm every target mailbox already exists in Office 365 (the tool throws errors on missing targets, not warnings). Make sure admin consent is showing green on all permissions.

Loading and Scanning PSTs

Select Office 365 as the target from the opening screen. Load files individually, select multiples, or point the tool at a folder for bulk intake. Run the pre-migration scan before configuring anything else — this is where corrupted items surface. Before the job is started, review and make any necessary repair or exclusion decisions using the flagged item list. You can also preview the folder tree preview and select/deselect any item that should not migrate to the target mailbox (old junk folder archives, testing folders, and more).

Authentication/Mailbox Mapping. 

You will be required to enter your client ID, tenant ID, and client secret to access the mailboxes you are attempting to migrate to. When you click Validate, the tool will verify that it can generate the tokens and access the target mailbox. You will not be able to continue until you resolve any validation errors. For mailbox mapping, use the GUI table for small jobs or import a CSV with PST_Path and Target_Mailbox columns for bulk. Set duplicate handling behavior (skip is usually the right call), add date range filters if you’re doing a partial migration, and adjust folder name mapping if your Office 365 structure doesn’t match the PST naming.

During the Migration

The dashboard shows per-PST progress, item counts, skip reasons, throttle events, and estimated finish time. You’ll see 429 events on large jobs — that’s normal. The tool handles them automatically. Users stay online throughout; migrated items show up in their Office 365 mailbox in real time, no cutover needed.

After It Finishes

Export the completion report before doing anything else. Cross-reference item counts against your PST inventory. Spot-check 5-10 mailboxes by searching for specific emails you know existed. Check calendar and contacts in Outlook Web App. Once you’re satisfied, revoke the Azure AD app’s permissions from Enterprise applications and move source PSTs to cold storage. Give it a few weeks before deleting them permanently.

What Migrates and What Doesn’t

Full coverage: all mail folders including Inbox, Sent, Drafts, Deleted Items, custom and nested folders; file and inline attachments with original filenames; contacts and all their fields; calendar events including recurring series, attendees, location, reminders; tasks with due dates, priority, status, recurrence; sticky notes; read/unread status; original sent/received timestamps; folder structure as-is; email flags and color categories.

Not migrated: Journal entries (Exchange Online doesn’t support them) and RSS feed items. Both show up in the completion report as excluded with explanation.

Try It on Your Actual Files First

The free demo processes a capped number of items per folder. That’s enough to run it against your real PSTs — specifically the large one and the one that might have corruption issues — and confirm the tool handles your environment before you commit to the full job. No Outlook needed, no credit card, any Windows machine with internet access.

Download Free Demo of SysinfoTools PST Converter

Questions That Come Up

About The Author:

Simran Bhatia

Simran Bhatia is a technical content writer engaged in writing clear, concise, and SEO-optimized content. With a background in computer science and a passion for writing, I thrive to deliver complex technical content in simple layman terms.