- 2368 Maritime Dr Unit 250, Elk Grove, CA 95758, United States
- Mon – Fri: 7:00AM – 7:00PM
- contactus@bpsemail.com
- (916) 525 8324
A multi-provider primary care group needed to retire a failing on-premise file server and modernize document collaboration — without disrupting clinic operations or creating compliance gaps. Business PC Support delivered a structured Microsoft 365 migration that covered both platforms, tailored to how each team actually worked.
Background
When a Sacramento primary care group came to Business PC Support, their first question was simple: "Should we move everything to OneDrive or SharePoint?" It was the right question — and the answer shaped the entire engagement.
OneDrive for Business and SharePoint Online are both part of Microsoft 365, and both store files in Microsoft's cloud infrastructure. The difference is purpose. OneDrive is designed for personal work storage: a physician's draft notes, a biller's individual reports, files that belong to one person. SharePoint is designed for team and organization-level document libraries: shared clinical protocols, HR policy folders, departmental billing templates — files that belong to a team and need governed access.
This practice had been running both kinds of content off a single aging Windows Server file share, with no meaningful separation between personal and shared documents. When that server began showing signs of hardware failure, the practice administrator contacted Business PC Support to plan a migration before data loss became a real outcome.
After an initial discovery session, the team identified 2.1 terabytes of content spanning six departments. A side-by-side architecture was recommended: personal and role-specific content would route to OneDrive, while department-owned documents and shared clinical reference materials would move into structured SharePoint document libraries. Both platforms would operate under the same Microsoft 365 Business Associate Agreement already in place with the practice's Microsoft tenant.
The Situation
The practice's infrastructure challenges went beyond simple aging hardware. Years of unplanned file accumulation, no naming conventions, and no access governance had created a storage environment that was difficult to manage, difficult to secure, and difficult to migrate without careful planning.
Administrative staff kept billing templates, insurance forms, and HR documents in folders shared across the entire staff network drive — meaning clinical staff with no need for billing data had access to it by default. There were no documented retention policies for any file category, and deleted files were gone permanently with no recovery path beyond a monthly backup tape that had not been tested in over a year.
The practice's IT environment was further complicated by three remote providers who accessed files via VPN, with inconsistent performance and occasional connection failures that disrupted patient documentation workflows mid-appointment. A modern cloud solution that worked reliably on any device was as much an operational requirement as a security one.
The primary file server was operating past its recommended service life with early signs of disk degradation — creating real risk of sudden data loss across 2.1TB of clinical and administrative files.
Three off-site physicians relied on a VPN connection to access shared files during patient visits. Intermittent failures caused workflow interruptions and delayed documentation.
All staff shared a flat folder structure with broadly permissive access. Clinical, billing, and HR data sat in the same network share with no role-based separation.
Tape backups had not been verified in more than twelve months. There was no documented recovery procedure, and no recovery time objective defined for any data category.
Our Approach
Every phase was sequenced to keep the practice fully operational. Migrations ran outside patient hours, staff training happened in small group sessions between appointments, and the old server remained available as a read-only fallback until cutover was confirmed complete.
Business PC Support conducted a full inventory of the existing file server: folder structures, file types, ownership patterns, and access group memberships. Each folder category was classified as either personal-use content destined for OneDrive or shared-access content destined for SharePoint. A migration map was produced and reviewed with the practice administrator before any data movement began. Microsoft 365 licensing was confirmed to include the required plans for both platforms, and the existing HIPAA Business Associate Agreement with Microsoft was reviewed and updated to cover the expanded storage scope.
Six department-level SharePoint sites were created and organized under a single practice intranet hub. Each site received a structured document library with clearly named folders, version history enabled, and role-based permission groups tied to existing Azure Active Directory security groups. Clinical staff received access only to clinical content libraries. Billing staff accessed billing documents. HR materials were restricted to authorized administrators only. The SharePoint configuration was tested by a representative from each department before any files were transferred.
Migration ran overnight and over weekends using Microsoft's SharePoint Migration Tool, preserving original file metadata, timestamps, and folder hierarchy. Shared departmental content moved into the newly configured SharePoint libraries. Personal and role-specific files were routed to each staff member's provisioned OneDrive for Business account. Progress was tracked in real time, and any files that encountered transfer errors were logged and manually reviewed. By the end of Week 3, all 2.1TB of content had been successfully migrated and verified against the source inventory. The legacy server was placed into read-only mode as a fallback.
All 34 staff members — including the three remote providers — attended a 45-minute onboarding session delivered in small groups around the clinical schedule. OneDrive sync client was configured on each workstation and on the providers' laptops. SharePoint libraries were mapped as familiar folder locations in Windows Explorer to minimize the learning curve for staff accustomed to drive-letter navigation. Remote providers gained reliable, fast access to shared documents without the VPN. After a three-day parallel period with no reported issues, the legacy file server was formally decommissioned and documented for the practice's compliance records.
Results
Four weeks after the engagement started, the practice was operating entirely from Microsoft 365 cloud storage — with better access controls, faster file access for remote providers, and a compliance posture stronger than anything the old server could support.
All data movement occurred outside clinic hours. Not a single patient appointment was affected, and staff arrived on the final cutover morning to find their familiar folder structure already waiting in the new environment.
Six structured SharePoint sites replaced a single flat network share. Each department accesses only the content relevant to their role — a compliance and security improvement that also reduced accidental file modifications.
The Microsoft 365 BAA covers both OneDrive and SharePoint under a single agreement. Audit logging, DLP policies, and retention labels are active across all content — providing the documentation trail required under the HIPAA Security Rule.
Remote providers connect directly to SharePoint and OneDrive through Microsoft 365 with conditional access enforced. File access during patient visits is now fast and reliable — no VPN, no dropped connections, no delays mid-appointment.
Every file stored in OneDrive and SharePoint now retains 500 versions by default, with a recycle bin recovery window and administrator-controlled retention policies. The practice's untested tape backup process is fully retired.
Training sessions were completed in groups of six, working around the clinical schedule. All staff — from front desk to remote physicians — were productive in the new environment before the legacy server was decommissioned.
Platform Guidance
One of the most valuable outcomes of this engagement was a clear, documented policy on which content belongs in OneDrive and which belongs in SharePoint — a decision framework the practice now uses when onboarding new staff or creating new content categories.
"We had been running on the same file server for eleven years and were honestly nervous about moving everything to the cloud. Business PC Support walked us through every decision, structured the migration so nothing was disrupted during clinic hours, and made sure our remote doctors could actually use the new system before they decommissioned the old one. The transition was far smoother than we expected. Our staff adapted quickly, and the remote providers told us file access is noticeably faster than before." — Practice Administrator, Multi-Provider Primary Care Group · Sacramento, CA
Services Delivered
This migration was delivered as part of Business PC Support's managed cloud services practice, with ongoing monitoring and support continuing after the initial engagement closed.
Business PC Support · Sacramento, CA
Our team handles every stage of cloud migration — from content audit and architecture design to staff training and ongoing compliance monitoring — so your clinical team stays focused on patients, not IT logistics.