You've decided to move a massive 80GB email archive into a new account. The logical first step seems to be a simple drag-and-drop. You start the process, and for a while, it looks like it's working. Then, everything grinds to a halt. The transfer fails, and Outlook might even become unresponsive. What happened?

The most common culprit is a built-in size limit on Outlook Data Files. These files, which end in .pst or .ost, are where Outlook stores your mail, calendar, and contacts on your local machine. By default, modern versions of Outlook (2010 and later) set a maximum file size of 50GB.

An Outlook Data File with the .pst extension is typically used for POP and IMAP accounts, or for manually backing up and exporting mail. An .ost file, on the other hand, is an "Offline Storage Table" used by Exchange, Microsoft 365, and Outlook.com accounts. It's a synchronized copy, or cache, of your mailbox that lives on the server. When you try to move an 80GB archive into an account using an .ost file, you're attempting to create a local cache that is 30GB larger than the default limit allows. Outlook simply won't let the file grow past that 50GB mark, causing the operation to fail.

Let's say you're technically savvy. You know about the 50GB limit and have even modified your system's settings to allow for a larger file. You restart the transfer, and it gets further this time, but eventually, it freezes again. Now what?

This time, you're likely running into server-side limitations. When you're connected to a Microsoft 365 or Exchange Online account, you aren't just interacting with files on your computer; you're in constant communication with a Microsoft server. To ensure the stability and availability of the service for millions of users, Microsoft implements throttling policies on its servers.

These policies limit the amount of resources any single user can consume in a given period. When you start a massive 80GB upload, you're sending thousands upon thousands of requests to the server in a very short time. The server sees this high-volume activity, flags it as potentially disruptive, and begins to slow down or even temporarily block your connection. From your perspective, the sync progress bar just stops moving. It’s not a bug; it’s the server protecting itself.

Throttling isn't just one single limit. It's a complex set of rules governing different types of activity. While the exact numbers can change, they cover areas like:

So how can you confirm what's causing the problem? For the file size limit, the answer lies in the Windows Registry. You can check the specific settings that control the .ost and .pst file sizes. Be very careful when editing the registry, as incorrect changes can cause system instability.

The relevant keys are typically found under a path similar to this, depending on your version of Office:

Within that key, you'd look for two DWORD values: MaxLargeFileSize and WarnLargeFileSize. These are set in megabytes (MB). If they aren't there, Outlook is using the default 50GB (or 51,200MB) limit.

The final piece of the puzzle is the communication protocol itself: MAPI over HTTP is the modern method Outlook uses to talk to Exchange servers. It's highly efficient for the day-to-day traffic of sending emails, updating calendar appointments, and syncing a few folders. However, it was not designed for a single, massive data-hauling operation. An 80GB transfer puts an enormous strain on the protocol, leading to timeouts, high latency, and contributing to the sync freezes you experience. It’s like using a sedan to move the entire contents of a warehouse. It can move things, but it's not the right tool for the job, and it will be incredibly slow and inefficient.

Ready to test your knowledge on these technical roadblocks?