SharePoint intranet: what a small company actually needs
What changes when a small company moves from a shared drive and email attachments to a small, well-structured SharePoint, and why copying the file server as it is causes most of the trouble.
On this page
- What changes when you move from a shared drive to SharePoint?
- Which SharePoint sites does a small company need?
- Who should be able to see each site?
- Why use columns instead of folders?
- How much SharePoint storage does a small company get?
- What goes wrong if you copy the file server as it is?
- What can wait until people use the basics?
Say you need the current version of a client contract. One copy is attached to an email from March, a newer one sits on the S: drive, and a colleague edited a third on their desktop. A small company's SharePoint fixes that with four things: a home site for news, policies and links; one site per team, which you usually get by creating a team in Microsoft Teams; permissions set by group rather than by person; and document libraries with a few columns instead of deep folder trees. Start there, and add the rest once people use it.
This is for companies of roughly 10 to 200 people on Microsoft 365 who work from a shared drive and email attachments today. If you already run a large intranet with a content team, you need more than this.
What changes when you move from a shared drive to SharePoint?
The files stay the same. What changes is where each one lives, who can see it, and how people find it.
| Today, on a shared drive and email | After, on SharePoint |
|---|---|
| One S: drive with a folder per department, set up years ago | One site per team, joined to a home site through a hub |
| Policies and forms emailed round, or saved somewhere "everyone knows" | A home communication site with policies, forms, news and links |
| Access given folder by folder, person by person | Access given per site, through the team's Microsoft 365 group |
| Contracts found by opening folders nine levels deep | A contracts library sorted and filtered by client, type and renewal date |
| Files sent as attachments, then edited in parallel | Links to one file that people edit together |
| Remote staff on a VPN, or emailing files to themselves | Files in the browser, in Teams, or synced to the laptop |
Which SharePoint sites does a small company need?
Most small companies need a home site, one site per team, and a private site for management. Client or project sites are worth adding if that's how you already work.
The home site is a communication site that a few editors look after: news, policies, forms, links and a people directory. Each team (Sales, Finance, Operations) gets a team site, usually created by making a team in Teams, and that team edits it. If you work client by client or project by project, give each its own team site, shared with guests when needed. Directors get a private team site for board papers, HR and salaries.
Microsoft's SharePoint limits page (checked 16 November 2026) recommends creating separate sites and grouping them with hub sites rather than building subsites. For a small company, I set the home site as the one hub and join every team site to it. That gives shared navigation across the top of every site and nothing more to maintain.
Who should be able to see each site?
Give access by Microsoft 365 group, one per site, and avoid giving individual people access to individual folders. Teams creates the group for you, so everyone in the Sales team gets the Sales site.
Person-by-person folder access is quick on the day and impossible to keep track of a year later. When someone changes role, a group change moves all their access at once; folder grants hang around until someone stumbles on them.
Two settings need a deliberate decision: whether staff can share files with people outside the company, and whether "anyone with the link" links are allowed. The right answer depends on your clients and contracts. The mistake is never deciding. These choices matter even more before Copilot, which can find anything a person has permission to see; see Copilot readiness and oversharing.
Why use columns instead of folders?
A library with columns can be sorted, filtered and searched in ways a folder tree can't. A contracts library with columns for client, contract type and renewal date answers "what renews next quarter?" in one click.
Keep one or two folder levels if people find them familiar, and use columns for the rest. Microsoft's limits page gives two reasons to stay shallow: the full path including the file name can't exceed 400 characters, and Microsoft recommends syncing no more than 300,000 files in a library.
How much SharePoint storage does a small company get?
The organisation gets 1 TB plus 10 GB per licence for SharePoint, per Microsoft's limits page, separate from each person's OneDrive. A 30-person company has about 1.3 TB of shared space.
Documents rarely fill that. Video archives, design files and old backups do. Before migrating, I run a size report on the old drive and sort by folder size, because the biggest folders are usually the ones nobody has opened in years.
What goes wrong if you copy the file server as it is?
Long paths break, sync struggles, and permissions don't land the way anyone expected. Copying the old drive into one site in a single pass is the most common way a SharePoint move goes wrong.
Imagine an illustrative 60-person company whose S: drive has 14 years of folders, nine levels deep in places, with permissions set folder by folder over the years. The IT contractor copies it all into one SharePoint site to save time. Within a week, people say files won't open because the paths are over the length limit, the sync client struggles, and staff can see the HR folder, because its special permissions didn't come across the way anyone expected.
A safer route takes a little longer up front:
- Map each top-level folder to a site by who uses it: Finance folders to the Finance site, HR to a private HR site.
- Agree a cut-off date. Files untouched for years go to an archive site with read-only access, not into everyday sites.
- Set permissions at site level, by group, before copying anything, and check them with a test account that has an ordinary user's access.
- Run a path-length report on the old server and shorten the worst paths before the move.
- Copy one team first, let them work in it for a week, then do the rest.
What can wait until people use the basics?
Custom branding, complex workflows, and dozens of sites for every possible group can all wait. If people find files and policies faster in the first month, then build the next piece.
The first additions I usually see earning their place are a few Power Automate flows, such as filing supplier invoices from a mailbox into a library or reminding someone before a contract renews. Power Automate examples for small businesses has the ones worth building first.
This guide sits inside our wider Microsoft 365 migration checklist, where file moves happen in weeks 2 and 3.
Closing note: Cloudgramam designs and builds SharePoint sites for clients, so we sell this work. SharePoint itself comes with your Microsoft 365 licence, paid to Microsoft or your partner. Limits quoted here were checked on Microsoft's pages on 16 November 2026. If you want it built for you, see our SharePoint development services.