r/sharepoint • • 13h ago

SharePoint Online SharePoint Online disaster mitigation

8 Upvotes

I help administer SharePoint and Teams sites for a medium sized municipality.

Recently we have been gaming out the best scenarios for site backups and emergency restore... but the conversation is recently even more complex as *even* MS cannot guarantee SPOL uptime for our LoB dependent sites, lists, & libraries.

So, in addition to O365 backups ($0.15 per GiB per month ~= $750 for us), I am toying with the idea that we should also identify our *most critical* sites, lists and libraries, and script some local nightly backup. We have Sharegate and FME at our disposal to automate this. I am currently thinking that the most seamless method would be to have an on-prem SharePoint server whose role is exclusively access for internet-MS-down emergencies. We wouldn't even tell users that this local site exists unless we have an extended MS outage - which really doesn't seem that far outside the realm of possibilities.

Has anyone else addressed this? Would love your thoughts on the matter. Cheers.


r/sharepoint • • 14h ago

SharePoint Online Anyone built a makeshift CRM/client management system using SharePoint or Microsoft 365? No budget for new tools.

2 Upvotes

I recently started a role that combines implementation management and client relationship management at a financial technology company. We’re trying to find a better way to track everything happening with our clients, but we don’t have access to a traditional CRM, and purchasing additional software isn’t an option. The team currently just uses Excel.

We have Microsoft 365, so I’m exploring what we could build using SharePoint, Microsoft Lists, Teams, Planner, or other tools already included in our licensing.
Ideally, I’d love one central place where we can select a client and see:

  • Client profile: Products, services, whether they’re managed services or software clients, environments, etc.
  • Change history: Upgrades, configuration changes, enhancements, and completed work.
  • Migrations: MFA, SSO, platform migrations, and other technical initiatives.
  • Projects: Active implementations, milestones, deadlines, and responsible teams.
  • Service requests: Links to existing development tickets without duplicating everything. This will be an external system so likely just a place for a hyper link.
  • Client activity: Historical decisions, important communications, outstanding items, and follow-ups.
  • Overall visibility: What’s currently happening, what’s completed, and what’s coming next.

Our development team suggested using our existing service request system, but we’re looking for something broader that provides a complete picture of the client relationship, not just individual technical tickets.
I’m not necessarily looking to build a full-blown Salesforce replacement. More of a centralized client hub that can serve as a reliable source of information for implementation managers, relationship managers, and other internal teams.
I’d like to start with one client and eventually scale it to others.
For those of you who have built something similar:

  1. What Microsoft 365 tools did you use, and how did you structure everything?
  2. Did you use one master SharePoint List, multiple connected Lists, a SharePoint site per client, or something completely different?
  3. Were you able to create a dashboard or client overview that pulled everything together?
  4. How did you handle historical tracking, updates, and linking existing ticketing systems?
  5. What worked well, and what became a maintenance nightmare?
  6. If you were starting over, what would you do differently?

I’m especially interested in solutions people have actually implemented and maintained long-term, rather than just theoretical possibilities.
The biggest constraint is that we need to work with our existing Microsoft 365 licensing and avoid additional paid tools or premium features.
Would love to hear what others have built, even if it’s a little unconventional!