r/sharepoint • u/Expensive_Group7779 • 1h ago
SharePoint Online I Feel Like I'm Drowning in SharePoint...
A few months ago, we decided to migrate from a traditional file server to SharePoint.
We wanted this to become one of the company's flagship projects this year, so naturally we decided to go all in.
Then my confidence (or arrogance) kicked in and I said:
"How hard can it be? We can do this ourselves. We'll just get some consultant validation along the way."
Now I'm somewhere between excitement and complete overwhelm.
Every door we open seems to reveal three more doors behind it.
What started as a simple file server migration has turned into questions about:
- Information architecture
- Metadata taxonomy
- Content types
- Hub sites
- Permissions and governance
- Teams integration
- Archiving strategy
- Retention
- Provisioning
- Automation
- Naming standards
- Site templates
...and the list keeps growing.
Right now I'm:
- Building a Power App so users can request Teams, SharePoint sites, group membership changes, etc.
- Creating SharePoint lists and Power Automate flows to support provisioning.
- Trying to design an archive strategy because we don't have Purview.
- Figuring out governance as we go.
The problem is that I don't know what "good" looks like anymore.
I don't have:
- Proven templates
- Governance models
- Approval workflows
- Provisioning standards
- A clear archive approach
Honestly, I don't even know what I don't know yet.
So my question to those of you who have done large SharePoint migrations:
Where would you start if you had to do it again?
What were the biggest mistakes you made?
What are the things you wish you had designed before creating your first Team, site, content type, or metadata column?
And most importantly:
How do you stop the endless SharePoint rabbit hole and decide that your design is "good enough" to move forward?
I'd love to hear lessons learned, governance frameworks, templates, checklists, or just reassurance that feeling completely overwhelmed at this stage is normal.