Fix Outlook Freezing at PersonMetadata During PST Synchronization
Question details
The user is attempting to sync a massive 28 GB PST file to Microsoft 365 via Outlook, but the application slows down significantly, freezes, or crashes when it reaches the PersonMetadata folder.

- Product
- Microsoft Outlook
- Device & OS
- not provided
- Scenario
- Importing a large PST file into the local Outlook client to synchronize old email data with a Microsoft 365 mailbox.
- Observed behavior
- The synchronization process becomes extremely slow and eventually hangs entirely at the PersonMetadata stage, leading to Outlook crashing or becoming entirely unresponsive before the import finishes.
Verify that your internet connection is highly stable and check that your Microsoft 365 mailbox storage limit has enough capacity to accommodate the 28 GB PST file before attempting any further synchronization.
Use Microsoft 365 Network Upload (AzCopy) for Large Migrations
For PST files larger than 10 GB, it is highly recommended to use the Microsoft 365 Import service rather than the local Outlook import wizard to prevent crashing and sync timeouts.
Importing exceptionally large PST files locally forces the desktop client to handle massive data transfers, which frequently causes hangs at hidden system folders like PersonMetadata.
Using the Network Upload method via AzCopy directly uploads the data to Microsoft servers, bypassing local client limitations and ensuring a smooth migration.
Log into the Microsoft Purview compliance portal using an administrator account. Navigate to Data lifecycle management > Microsoft 365 > Import.
Click on 'New import job', provide a name for the job, and select 'Upload your data'. Click Next to generate a secure SAS URL.
Download and run the AzCopy command-line tool. Use the provided SAS URL to securely upload your 28 GB PST file directly to Microsoft's Azure storage.
Create a CSV mapping file that specifies which Microsoft 365 mailbox the uploaded PST belongs to. Submit the mapping file in the Purview portal to finalize the server-side import.

Force Folder Update and Repair Data Files
If you must continue with a local import, forcing a manual synchronization and repairing the local Outlook data file can resolve hanging issues.
Experience a Lightweight Office Suite with WPS Office
Dealing with heavy data syncs and crashing applications can severely disrupt your workflow. While Outlook is handling your email migrations, consider using WPS Office for your document management. It is a powerful, lightweight alternative to Microsoft Office that handles text documents, spreadsheets, and presentations efficiently without draining your system's resources.

Frequently Asked Questions
Why does Outlook get stuck specifically on the PersonMetadata folder?
The PersonMetadata folder is a hidden folder created by the Outlook Customer Manager to store linked contacts and communication histories. When importing massive amounts of data, the system attempts to index and cross-reference thousands of entries, which can overwhelm the local client's memory and connection to Microsoft 365.
What is the maximum PST file size I can safely import into Outlook?
Although the technical maximum limit for a PST file in recent versions of Outlook is 50 GB, performance degradation, freezing, and sync failures typically begin when handling files larger than 10 GB to 20 GB locally. For files larger than 10 GB, server-side tools like AzCopy are recommended.
Will I get duplicate emails if I use AzCopy after a failed local PST import?
In most cases, you will not. The Microsoft 365 Import service is designed to recognize Message IDs. If an email has already been synced to the server during your failed local import attempt, the server-side AzCopy process will identify it as a duplicate and skip it.




