Why adoption stalls
Most businesses on Microsoft 365 already pay for Teams and SharePoint. Many of them still email attachments back and forth, keep files on a server mapped drive and use a group chat on personal phones for quick questions. Someone set up Teams during the first lockdown, created twenty channels, and nobody quite knew which one to use. SharePoint was switched on but files never moved, so it sat empty.
People keep using what works for them. If the old shared drive still has all the files, staff will keep using it. If Teams has too many channels and no rules, they'll go back to email. Adoption is less about training and more about making the new way clearly easier than the old one.
Design a simple structure first
Before anyone moves a file, decide how the business will be organised in Teams and SharePoint. For most offices under fifty people, a handful of teams is plenty: one for the whole company, one per department or function such as Accounts, Operations and Sales, and perhaps one for management. Inside each team, keep channels to a minimum and name them for real activities, not every topic that might come up.
Think about permissions at the same time. Each team has owners and members, and files in that team are shared with its members. If payroll and HR documents need tighter access, give them their own team or SharePoint site rather than relying on folder-level permissions inside a broad team. Simple structures are easier to secure and easier for staff to understand.
Move the files properly
A migration from a server shared drive or Dropbox to SharePoint is the point where adoption succeeds or fails. Clean up first: archive old projects, remove duplicates and decide what goes where in the new structure. Then use a proper migration tool or service so file dates, versions and permissions carry over correctly, rather than staff dragging folders across by hand over weeks.
Watch for the practical limits that trip people up, such as very long file paths, special characters in file names, and large numbers of files synced to one laptop. Your IT provider should check for these before the move. Teach staff how to sync a library to File Explorer or Finder, so the files appear in a familiar place, and how to use the 'Add shortcut to My files' option instead of syncing everything.
Close the old routes
Once files are migrated and checked, make the old shared drive read-only, then remove it after a set period such as a month. Announce the date clearly. If you leave it running indefinitely, half the team will quietly keep saving there and you will end up with two versions of everything.
Do the same with communication. If the team has been using a personal messaging app for work chat, agree a date to move work conversations into Teams. If a manager emails an attachment to a colleague who sits nearby, encourage them to share a link to the file in Teams instead. Small, consistent nudges change habits faster than a big announcement.
Set a few ground rules
Write down four or five simple rules and share them. For example: files live in the team they belong to, not in personal OneDrive or email. Quick questions go in Teams chat, decisions and customer matters go in email or the job system. Use channels for team-wide updates and keep one-to-one chat for personal coordination. Name files clearly so others can find them. Keep the rules short enough to pin at the top of the company team. Review them after a couple of months, since real use will show which ones matter and which can be dropped.
Managers set the tone
Staff watch what managers do. If the owner keeps emailing attachments and asking for files to be printed, nobody else will bother changing. Ask managers to use Teams and SharePoint visibly from day one: posting updates in channels, sharing links instead of attachments, running meetings from the team calendar. Celebrate small wins, such as a project where everyone worked on the same file without version confusion. Collect complaints too, because they often reveal a setup problem that can be fixed, such as a missing channel or a permissions mistake. After three months, most offices that follow this approach find the new tools have become the normal way of working.
In short
- Plan a small number of clearly named teams before moving any files.
- Use a proper migration, not manual drag and drop.
- Make the old shared drive read-only, then remove it.
- Agree a handful of simple rules for chat, email and files.
- Managers need to use the tools visibly first.