
A company folder structure: design it first, then move to SharePoint
A folder structure is the first thing people see when they look for a file, and the last thing anyone thinks about when moving to SharePoint. So the old shared drive gets copied across as it is, detours and all. This is the order in which we design a structure before a single file moves.
Organise a folder structure around the work the business does, not today’s departments: those change faster than the processes do.
In SharePoint one question decides between site, library and folder: who needs access? Permissions belong on the site, not on individual folders.
Test the design with twenty real documents and three colleagues. Wherever they disagree, the file will end up in two places.
Why the folder structure comes before the move
A move to SharePoint or Teams is the one moment you can change how the whole business files things in a single step. Afterwards the files are in place, links point to them and people have made their shortcuts; every reorganisation then costs twice.
The temptation is to lift the old drive across unchanged, “so everyone can still find everything”. That works for a week. After that you have inherited years of improvisation on a platform that works differently: permissions belong on sites rather than folders, and deep folder trees sync badly to laptops.
So design the new folder structure on paper first, have it tested by the people who will work in it, and only then move. How to move the files themselves without losing anything is covered in our article on data migration without loss; this one is about what has to be in place before that step.
Organise by the work, not the org chart
The most common layout is one folder per department, and it is the one that ages fastest. Departments are merged, renamed and split; the work they do changes far less. A quote is still a quote, whether Sales or Account Management produces it.
Three kinds of top-level folder last better:
- Processes the whole business recognises: purchasing, sales, HR, finance, quality. They survive a reorganisation.
- Case files with a start and an end: clients, projects, contracts, premises. Each gets the same fixed subfolders from a template, so every project file looks the same.
- Shared reference: brand assets, templates, procedures, policies. One place, one owner, read-only for everyone else.
One thing does not belong: personal folders. Whatever belongs to one person lives in their own OneDrive, not in a folder with a first name on the company drive. Folders called “Misc”, “Old” or “Sarah” are where files go to disappear.
How many levels, and what sits at the top
A workable rule of thumb: people should find a file within three, at most four clicks from the top. Every extra level is a choice a colleague can make differently, and then the same kind of document ends up in two places.
The top level matters most and should be the most stable. Keep it short, and only change it by decision. Below it the work can have more freedom, but inside a case file the template applies.
Two habits keep the tree flat. A year or status in the name rather than a folder per year, so an ongoing file does not move every January. And an archive area for closed files, so the current list stays short. In SharePoint a column can also replace a folder level; more on that below.
Naming conventions that still work in five years
A naming convention sounds like bureaucracy and saves search time every day. It need not be long; these five rules cover most of it:
- Date first, year first: year, month, day (2026-10-20). A folder then sorts itself by time.
- A fixed order for the rest, for example client or project, then document type, then a short description.
- No version numbers in the name when the platform has version history. SharePoint keeps earlier versions itself; “final-v3-really” means nobody knows that.
- No special characters and short folder names. SharePoint rejects a handful of characters, and an overlong path stops syncing. Short names keep the whole path short.
- Abbreviations everyone knows, with a short list of them in the reference area.
Put the convention on one page at the top of the reference area. A rule that is written down nowhere has stopped existing within three months.
From folder structure to SharePoint: site, library or folder
On a file server everything is a folder. SharePoint has three layers, and choosing between them is the most important decision in the whole design:
- A site for each group of people with the same access: a department, a team, a large project. Access is set here, at one level.
- A library within that site for each kind of content that needs its own handling: a different retention period, different columns, its own template.
- Folders within a library for whatever ordering is left, and kept shallow.
The deciding question is always the same: who needs access? If the answer differs, it belongs in another site. If it is the same, it is a library or a folder. Turn that around and grant permissions folder by folder, and you rebuild the tangle of the old drive inside SharePoint.
If you use Teams, remember that every team gets its own SharePoint site. Designing a folder structure and then letting everyone create teams freely gives you two structures that know nothing of each other. Agree who creates teams, and how they are named.
The sorting test: try it before you move
A design on paper always looks logical to the person who drew it. The test that shows the difference takes an hour:
- Take twenty recent documents from different corners of the business: a quote, an invoice, a contract, meeting minutes, something from an HR file.
- Ask three colleagues who were not involved in the design, separately, where they would save each one and where they would look for it.
- Write down every document they disagree on.
Each of those documents will end up in two places. You fix that with a clearer name, a line in the convention or one folder fewer, not with an extra folder called “Other”. Repeat the test after the change; once the answers line up, the structure is ready to fill.
Who keeps the structure in shape
A folder structure without an owner drifts back to where it started within a year. It needs two roles, held by different people:
- An owner for each top-level folder or site, from the business. They decide what belongs there, who gets access and when a file moves to the archive.
- An administrator for the whole, usually IT. They guard the top layer, create sites and teams according to the convention, and make sure access runs through groups rather than individuals.
Agree when the structure is reviewed, for example once a year: which folders have not been opened for a year, which files can be archived, and where top-level folders have appeared that nobody decided on. In a move to Microsoft 365, naming those owners is the first step, before the first file.
Where our work stops
What we do. We help design the folder structure and translate it into sites, libraries and groups in SharePoint and Teams. We set up the permissions, move the files and build the agreements on creating and archiving into ongoing support.
What we do not do. We do not decide what your business must keep or for how long. That follows from HMRC record-keeping rules, UK GDPR and the rules of your sector, and it is a question for your accountant, your solicitor or your data protection officer. Nor are we archivists: we do not set up formal records management to a statutory or sector standard. And the layout itself stays yours: we ask the questions and build it, your teams decide what goes in.
Questions we are asked about this
The five that come up most often.
What is a good folder structure for a company?
One organised around the work (processes, case files and shared reference) rather than the org chart, kept to three or four levels, with an agreed naming convention and an owner for each top-level folder. Test it with real documents: ask three colleagues to place twenty files and see where they disagree.
How many levels should a folder structure have?
As few as possible; three to four from the top is a workable limit. Every extra level is a choice colleagues make differently, and in SharePoint it also lengthens the path. A year or status in the file name, or a column, often replaces a level.
Should we copy our shared drive folder structure straight into SharePoint?
You can, but it is rarely wise. In SharePoint permissions belong on sites rather than folders, and deep trees sync badly. Design the new layout first, then move the files into that structure.
What is the difference between a site, a library and a folder in SharePoint?
A site is the place for a group of people with the same access. A library is a collection of documents within that site with its own settings, such as columns or a retention period. Folders organise what is left inside a library and should stay shallow.
Do you also tell us how long to keep documents?
No. Retention periods follow from tax rules, UK GDPR and your sector’s rules, and that judgement belongs with your accountant or solicitor. We set up what you decide: an archive area, read-only access and, where the platform supports it, a retention policy.
Further reading
What comes before and after the structure.
Shall we design your folder structure together?
Send us an overview of the top levels of your current shared drive. We will show you how it would look in SharePoint, and what needs deciding first.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.