Skip ahead to the main page
Partner Huddle
Pages

Client folder move: 5 Microsoft storage limits to check

Partner Huddle Editorial Team · Published · 15 min read

Before you move a client folder, check five Microsoft storage limits: shared item counts, unique permissions, bulk changes, OneNote notebook size, and image thumbnails. The folder carries sharing settings that someone set years ago, permissions added one person at a time, notebooks full of meeting notes, scanned pages, and a history of changes that nobody has looked at since the last audit. Most of the trouble shows up after the move, when a partner cannot open a file, a bookkeeper can see a folder they should not see, or a shared link stops working for the client.

Key takeaways

  • Count the sub-items in each client folder against the 50,000 limit for shared folders.
  • Audit unique permissions across the whole library, since the 50,000 figure applies to the library, not one folder.
  • Plan bulk permission changes in batches at or below 5,000 items.
  • Find OneNote notebooks near 2 GB and images above 100 MB before the move.

Most of these problems are easier to avoid when you check a few numbers first. Microsoft publishes limits for OneDrive and SharePoint that apply to folders, permissions, notebooks, and images. This post covers five of them, and a companion list is in SharePoint limits: 5 checks for client libraries. Each one is a figure you can compare against your own folders before anything moves, which turns a vague worry into a short list of things to count.

The figures come from Microsoft's restrictions and limitations article for OneDrive and SharePoint. That page describes the restrictions that apply to files, file names, and file types when you sync with OneDrive for home, OneDrive for work or school, or SharePoint in Microsoft 365. If your firm uses those services, it is the first place to check. Read the page itself rather than relying on a summary, this one included, because limits are the kind of detail that gets updated.

This post is written for operations leads and partners at small accounting firms. You may not run the move yourself, but you usually approve the plan, and the checks below belong in that plan. They are also the checks that are easiest to explain to a partner who wants to know why the move is taking longer than expected.

A note on scope. The figures here are specific to Microsoft's services. If your firm is moving folders into a different cloud service, look up that provider's own limits before you start. Do not assume that one provider's numbers carry over to another, even when the features look similar on the surface.

1. Up to 50,000 sub-items in a shared folder

Sharing is where most client folder moves begin. A partner may want the client to see their own folder. A bookkeeper may need edit access to the whole archive. A staff member may need view access to one year and nothing else. Each of those decisions depends on something that is easy to overlook: how many things sit inside the folder you are about to share.

Microsoft's article gives this figure: when you share a folder, you can include up to 50,000 sub-items within that folder and its subfolders. The count covers the whole tree, not just the top level. A client folder with many years of returns, bank statements, engagement letters, and scanned invoices can grow faster than it looks, because each year, each account, and each document type tends to add its own subfolder, and each subfolder adds its own items.

The wording matters here. The article describes the number as a limit on what you can include, so treat it as a ceiling to stay under. Do not find out what happens past it during a live move. Count first, then decide.

It is easy not to know the totals for each client folder. The practical way to find out is to use whatever listing or reporting your storage administration tools provide, or to walk the folder tree once and write down the count for each client. It takes time, but it is the only way to be sure which folders are close to the figure. A folder that looks modest from the top level can hide a long list of small subfolders underneath.

If a folder is near the figure, split it before you share it. Splitting by tax year or by engagement is a common approach. It also has a second benefit: a smaller folder is easier to review when a client asks for one year's records, and easier to hand off when a team member changes. Make the split part of the move plan rather than a fix you apply after the first complaint.

Keep one habit in mind for later. Once a folder is shared, new items added inside it count toward the same figure. A folder that passes the check on move day can drift past it over the following year. Recount when you update the structure, not only at the start.

2. 50,000 unique permissions in a list or library

Permissions are the next figure, and they are the one most firms underestimate. A few items with their own access are easy to manage. Many of them spread across a client archive can make the permission structure hard to read and hard to trust.

Microsoft states: the supported limit for unique permissions in a list or library is 50,000 items. Notice the scope. This figure applies to the list or library as a whole, not to a single folder. A library that holds several client archives can collect unique permissions from all of them, so the count you care about is the total for the library you are moving into.

Individual access also builds up over time for ordinary reasons. A bookkeeper leaves, and their access stays on a few folders nobody remembers. A partner shares one document with a client and the sharing is never revisited. A staff member is given access to a single year so they can finish a review, and the access is never taken back. None of these is a crisis on its own.

Start with an audit. Find every item where access has been set by hand, list who has access to it, and write down why. Some of the access will turn out to be needed. Much of it will not. The audit does not need to be perfect, but it should answer two questions: is the library close to the supported limit, and is the permission structure simple enough that the people who use it can explain it?

Then clean up. Remove access for people who no longer work on a client. Where access is needed, grant it at the highest level that makes sense, usually a folder for a client, rather than to individuals on every subfolder. Where you can, use groups that describe a role, such as the team that handles a client, so that a change to the team is one change rather than dozens. For the wider access picture, read client data access controls. After the cleanup, recount the unique permissions and keep the number in your move log.

3. More than 5,000 uniquely permitted items changed at once

Once you know the permissions, you may need to change many of them at the same time. A common example is a staff member who leaves the firm. Their access has to come off every client folder they touched, and in a busy practice that can mean a long list. Another example is a new team that needs view access to a set of archived years. Bulk changes are where a move tends to stall, because they look like one action and turn out to be a large piece of work.

The five figures in this post, side by side:

Item Figure from Microsoft's articleEffect stated in the article
Contents of a shared folderUp to 50,000 sub-items Limit within the folder and its subfolders
Unique permissions50,000 items in a list or librarySupported limit
Bulk permission changes More than 5,000 uniquely permitted itemsChanging them at one time takes longer
OneNote notebooks2 GB Limit for notebooks saved in OneDrive or SharePoint
Image thumbnails100 MBNo thumbnails generated for larger images

Microsoft's article says: changing more than 5,000 uniquely permitted items at one time takes longer. That is enough reason to plan for it. Schedule the work for a time when a delay will not block a client deadline. Tell the people who depend on the affected folders that access may change for a while. Do not assume that a large permission change will finish during a short break in the day.

The 5,000 mark is also a sensible place to split the work. The article flags it as the point where changes take longer, so breaking a large change into batches at or below that count is a reasonable approach. Do not promise a speed to the partner before measuring. Instead, run one batch on a single client folder, note how long it takes, and use that measurement to plan the rest.

Keep a record of each batch. Write down which folders were changed, when, by whom, and what the result looked like afterward. If someone later asks why a particular staff member lost access on a given date, the log answers the question without anyone needing to remember. This is also the record you will want if a change needs to be repeated or reversed.

Bulk changes and the earlier audit are linked. If the audit turns up a large number of stale exceptions, the cleanup itself may be a bulk change. Plan the cleanup first, then do the batches, then recount. Doing those steps in the wrong order means you change permissions twice, and the second change can undo the first if the people involved have not agreed on the target state.

4. OneNote notebooks limited to 2 GB

Many small firms keep client notes in OneNote. Meeting notes, engagement checklists, questions for the client, and pages of scanned material pasted in from a scanner all end up in a notebook that sits in the client's folder. Notebooks are easy to start and easy to forget, and they can grow for years unnoticed until the move.

Microsoft's article says: OneNote notebooks saved in OneDrive or SharePoint are limited to 2 GB. The limit applies to the notebook itself, not to the rest of the folder around it. A client folder can pass every other check in this post and still hold a notebook that is too large to keep where it is. That is why this figure needs its own step in the plan rather than being assumed to follow from the others.

Notebooks that hold pasted scans and images are the likeliest to grow quickly, because those files are usually much larger than typed notes. A notebook that started as a list of meeting summaries can become something quite different after a few years of client paperwork has been pasted into it. This is a general pattern rather than a fixed figure, so the only reliable check is to look at each notebook's actual size.

Find every OneNote notebook in the client folders before the move. Notebooks are not always obvious in a folder listing, so search for them rather than relying on a visual scan. Record the size of each one next to its client name. Then compare each size against the 2 GB figure in the article.

If a notebook is near the limit, split it. The most natural split for accounting work is by year or by engagement, because that is how the client work is already organized. Splitting also makes the notebooks easier to search later. A partner looking for the notes from one engagement should not have to scroll through a decade of unrelated pages to find them.

After the move, check that each notebook still opens and syncs on the devices your staff use. Do this on a real device with a real account, not only in the administrative view. A notebook that is fine on the server but fails to sync on a laptop is still a problem for the people who need it on a Monday morning.

One more point for the plan. If a notebook is kept in its current form because it is under the limit, write that down. A future staff member may add more pages without knowing the limit exists, and a note in the move log is the simplest warning they will get.

5. No thumbnails for images larger than 100 MB

Photos and scans are the last figure. Client folders often hold images: photographs of invoices, scanned forms, pictures of property or equipment, or whiteboard photos taken during a client meeting. Those images are easy to overlook because they look like ordinary files in a folder view.

Microsoft's article says: the service doesn't generate thumbnails for images larger than 100 MB. A thumbnail is the small preview that lets someone recognize an image in a folder view without opening it. For an image above that size, the service does not generate one, so the preview that helps staff move through a folder quickly will be missing.

That matters during a move because review depends on being able to see what is in a folder. A folder full of images without previews forces staff to open each file to find out what it is. Across a large archive, that adds up to real time, and it is time that does not appear on any plan unless someone put it there.

Start by finding images above 100 MB in the photo and scan folders. Use a search or a sort by size rather than scanning by eye, because large files can sit in folders that look ordinary. Record the count and the client name for each one.

Then decide what each large image needs. Some originals should stay at their full size, because the detail is the point. A photograph of a damaged asset or a high-resolution scan of a signed form may need to be kept exactly as it was received. In those cases, keep the file and accept that it will not have a thumbnail. Note the exception in the move log so the next person knows the missing preview is expected rather than a fault.

Other images may not need their full size at all. If the scanning device or the phone settings your staff use routinely produce files that large, it is worth reviewing those settings going forward. That is a decision for the firm, and it should be made with the records policy in mind, because changing the scan resolution is a change to the records themselves, not only to the file size.

The restrictions article also covers file types and file names more broadly. It says that SharePoint in Microsoft 365 doesn't have a general list of blocked file types. That is a useful thing to know, but it does not mean the move will catch every problem for you. Without a general list to check against, the responsibility falls on your own review of the folders. Look for unusual file types, long file names, and anything that does not match the rest of the archive, and deal with those before the move rather than assuming the platform will flag them.

Illustrative example: counting one folder

Suppose a client folder holds 5,000 sub-items across its subfolders, and the firm wants to share it with one bookkeeper. The 50,000 figure leaves plenty of room, so the count does not block sharing. The same folder also contains 2 OneNote notebooks and 3 images above 100 MB. Those items need their own steps: check each notebook's size against 2 GB, and record the three large images in the move log. Now suppose the library holds 5,000 uniquely permitted items that need a bulk change. Run that change in batches at or below 5,000, and time the first batch on a single folder before scheduling the rest.

Before the move: a short checklist

The five figures in this post are not a full list of what can go wrong during a folder move. They are the ones with published numbers, which makes them the easiest to check and the easiest to explain to a partner. Use them as the core of a simple process rather than as a one-time test.

Start with an inventory for each client folder. Count the items inside it, including subfolders. Note whether it is shared and with whom. List the permission exceptions and the people behind them. Find every OneNote notebook and its size. Find every image above 100 MB. Put all of this in one place, one row for each client, so the numbers can be compared across the whole archive rather than one folder at a time. For the intake side of that work, see Accounting Client Intake Checklist for a Clear Handoff.

Next, fix what is over a figure. Split a folder that is near the sub-item limit. Clean up stale permissions before the library count becomes a problem. Plan bulk changes in batches, and schedule them so a delay does not land on a deadline. Split a notebook that is near 2 GB. For anything you cannot change, such as an image that must stay at its full size, decide that on purpose and write it down.

Then pilot one folder all the way through. Move it, share it, and check access the way the people who use it will see it. A partner should be able to open the files they need. A staff member should see only what they should see. A client should be able to reach what they were given, and nothing more. Confirm that the notebooks open and sync on a real device. Confirm that the version history a firm needs for client records is still available in the destination, and write down what you found. A single pilot will surface problems that a checklist cannot, and it gives you a measured time for the bulk steps.

Keep the source until the destination has been checked. Moving a folder and deleting the original on the same day leaves no room to recover from a mistake that only shows up after a week. Set a point at which the source is retired, and make that decision together with the partner who owns the client relationship.

Finally, keep a move log. Record the date, the client folder, the figures checked, the results, the exceptions, and the people who approved each step. The log is what turns a one-time move into a process your firm can repeat. It is also the document that answers the question a partner will ask months later, which is simply whether the folder was checked before it moved.

Today, pick one client folder and count its sub-items, including subfolders. If the count is close to 50,000, split the folder before anything else moves.

Frequently asked questions

What should I check first before moving a client folder?

Start with an inventory of each client folder: count its sub-items, note who has access, and find its OneNote notebooks and any images above 100 MB.

Are these figures a ceiling or a guarantee?

Treat each one as a ceiling to stay under, and count before you move rather than finding out during a live migration.

Where should I check the current limits?

Read Microsoft's restrictions and limitations article for OneDrive and SharePoint directly, because limits are the kind of detail that gets updated.

Sources