Infrastructure-bound access
Business information depended on the availability of a single on-premises server and a remote-access model that did not align with modern Microsoft identity.
Case study 01 / Clinical research
File server to SharePoint Online.
Replacing a legacy Windows file server, local user accounts and peer-to-peer VPN access with three structured SharePoint Online sites and Entra ID-based identity management.
≈3TBBusiness data migrated
3 sitesDistinct information domains
Entra IDCentral identity and access
From an inherited file share to a governed collaboration environment.
The client was an Australian clinical research organisation whose shared data remained tied to a local Windows Server. Staff authenticated with local server accounts and used a peer-to-peer VPN to reach files remotely.
Three purposeful sites
The destination was divided into three SharePoint Online sites, creating explicit boundaries for content, ownership and access rather than reproducing one large file share.
Identity through Entra ID
Local server identities were replaced with central Microsoft cloud identities, allowing access to be managed through Entra ID and the permission model of each site.
Architecture & delivery
The destination was designed before the data moved.
The migration treated information architecture, permissions and identity as part of the same technical change. That avoided carrying the limitations of the server directly into SharePoint Online.
01
Source assessment
Reviewed the existing Windows Server data estate, access model and remote connectivity dependencies to establish the migration scope.
02
Information architecture
Grouped the content into three SharePoint sites aligned to distinct business information domains and working requirements.
03
Permission boundaries
Established unique access controls for each site so users received the information required for their role without inheriting broad file-server access.
04
Identity transition
Moved authentication away from local server accounts and into Entra ID, providing a central identity layer for the Microsoft 365 environment.
05
Data migration
Migrated approximately 3TB of business data into the agreed SharePoint structure and validated access against the intended permission model.
A controlled transition across design, migration and acceptance.
The work was sequenced so that destination decisions were resolved before production content and users depended on the new environment.
Understand content and access
Establish how the server was used, who required access and where information boundaries needed to change.
Define sites and permissions
Design the three-site structure, Entra ID identities and maintainable access model.
Move and validate data
Transfer approximately 3TB into SharePoint Online and resolve exceptions against the target structure.
Move users to the cloud
Confirm access and establish SharePoint Online as the production location for shared business information.
Delivered outcome3TB →
3 sites
3 sites
Legacy shared data reorganised into a Microsoft cloud information environment.
Less dependence on local infrastructure. Clearer control of business information.
The organisation moved from a server-centric access model to SharePoint Online, with content distributed across three sites and access governed through Microsoft cloud identity.
The outcome was not simply remote access to the same folder structure. It created distinct information domains, explicit permissions and an identity model designed for the organisation’s Microsoft 365 environment.
- Windows Server source retired from file-sharing duty
- Approximately 3TB migrated
- Three SharePoint Online sites
- Entra ID identity and access model
Related case studies.
Microsoft cloud projects often combine information architecture, identity, endpoint management and tenant change.
Plan the destination first
Moving shared data into Microsoft 365?
Start with the information structure, access model and operating constraints—not the migration tool.
Discuss your migration ↗