SharePoint document management works when every document family has a named owner, a small set of permission groups, a few metadata fields people actually use, and a restore process someone has tested. Settle those four things before you migrate. If you move the folders first, you usually carry the old confusion into a new tool.
A common mistake is to treat a SharePoint move as a copy job and leave the rules about who owns what for later. Below is the order we recommend instead, starting with one document family as a pilot.
Why should ownership come before the migration?
A shared drive full of old copies has an ownership problem, not a storage problem. If nobody can say which version is approved, SharePoint will store the same doubt in a cleaner interface.
For each document family, name two people. A business owner is responsible for whether the content is correct and current. A site administrator is responsible for the library settings and access. They are rarely the same person, and the roles should stay separate.
Pick a bounded family for the pilot, such as operating procedures, project specifications or approved sales material. Avoid mixing HR files, contracts and marketing assets in the first library. Their audiences and risks are too different.
How should permissions be set up in SharePoint?
Microsoft's guidance on permission scopes explains that sites, libraries, folders and files inherit permissions from their parent by default. Breaking inheritance creates a new permission scope, and sharing a single file or folder also breaks inheritance on that item.
Microsoft says a library can hold up to 50,000 unique permission scopes and recommends staying under 5,000 for best performance. Few businesses reach that number. The real cost shows up much earlier: every one-off share is an exception that nobody remembers to review.
Write a simple access matrix before you build anything. Most pilots need three roles:
- Authors who create and edit working drafts.
- Approvers who decide when a document is ready for use.
- Readers who use the approved version.
When a group has a different audience, give it its own library or site instead of a pile of exceptions. Microsoft also recommends sharing folders rather than individual files and managing access through groups. Test with ordinary user accounts, not only an administrator account.
Which metadata fields are worth requiring?
Start small. Four fields cover most needs: document type, business owner, status and next review date. Add a client or project field only when people search by it every week.
For each field, ask two questions. Who keeps it accurate? What decision does it support? A required field that nobody uses adds friction and returns little.
Then build views around the questions people ask most: which procedures are due for review, which specifications are waiting for approval, and which files have no owner. A good view replaces a deep folder path that only one person remembers.
How do we separate working drafts from approved documents?
Editing and approval are different events. Agree on what moves a document from draft to approved, who can approve it and what record is kept. If you use an approval flow, test the unhappy paths too: a rejection, a resubmission and an approver who is out of the office.
Share links to the approved file instead of attachments. Once a copy is downloaded and emailed, no library can tell the recipient that a newer version exists.
How do we prove we can recover a file?
Microsoft's version history overview describes how users can view earlier versions, see who changed a file and when, and restore a previous version, which then becomes the current version. That is a useful safety net for everyday editing mistakes.
Prove it during the pilot. Create a harmless test document, make a clearly marked change, and ask an ordinary user to find and restore the earlier version. Write the steps down in plain words so the next person can follow them.
Do not treat version history as your backup or retention plan. Backup, retention and deletion are separate decisions with their own legal and business requirements, and they deserve their own review.
What about sharing with people outside the company?
Microsoft's external sharing overview explains that sharing is controlled at two levels: the organization and each site. When the two settings differ, the more restrictive one applies, so a site can never be more open than the organization allows.
Before inviting a partner, list the exact documents, the internal sponsor, the access level and the end date. Test what the guest actually sees. Do not copy private files into a more open site just to make sharing easier.
How do we know the pilot is working?
Track things the team can observe: time to find the approved version of a document, files with no owner, overdue reviews, open permission exceptions and whether the restore test passed. Ask users to complete real tasks during acceptance. Finding the right file and knowing who to ask matter more than a feature demo.
When the pilot family runs cleanly, repeat the same steps for the next one. If reviews and approvals still depend on reminder emails, that is usually the point where workflow automation earns its place.
Frequently asked questions
Not by default. Split sites by audience, ownership and lifecycle. Copying the org chart into sites often leaves the same files in several places.
No. Version history records changes. Approval is a business decision made by an authorized person through an agreed process.
It does not have to. Many teams use a shallow folder structure plus a few metadata fields. Test the design with real search tasks before a large migration.
One bounded document family with a named owner and clear permissions. Clean out obsolete copies before you move anything.
Sources
- Microsoft Learn: Manage permission scope in SharePoint
- Microsoft Learn: Version history overview
- Microsoft Learn: External sharing overview
Plan your SharePoint document pilot
Bring one document family and a rough outline of who needs access. We will help you map owners, permissions and the approval path before anything moves. Our document management services cover the build when you are ready.
