Turning a file-share maze into a SharePoint environment people could navigate

A multi-office engineering consultancy had more than a decade of project and business content spread across network drives, Teams, and loosely managed SharePoint sites. Leadership wanted easier access for hybrid staff and a useful company intranet. IT did not want to recreate the same sprawl in the cloud—or force latency-sensitive design files into a platform that did not fit them.

• ~1.8 TBFile content assessed
• 11Governed destination sites
• ~240Users across four offices
• 9 weeksDesign through handoff

The situation

The shared drive had familiar letters and years of accumulated exceptions. Some folders inherited access cleanly; others depended on one-off user permissions. Duplicate templates lived in several departments, inactive project folders stayed writable, and external sharing happened through whichever tool a project manager knew best.

A direct lift-and-shift would have produced a technically successful migration and a poor employee experience. The engagement started with decisions about what belonged in SharePoint, what should be archived, and what needed to remain on engineering storage.

The constraints that shaped the design

• Active CAD and model files needed their existing high-performance storage workflow
• Project support documents still needed secure access from the office, home, and job sites
• Department leaders wanted autonomy without uncontrolled site creation
• Client collaboration required external sharing with clear expiration and ownership
• IT had limited capacity for a governance model that depended on constant manual policing

How we worked

Inventory before architecture

We analyzed content volume, age, ownership, file types, path depth, and permission patterns. Department workshops separated active collaboration content from records, duplicates, personal working files, and engineering data that should not move.

A small number of sites with clear jobs

The target used a communication hub for company news, policies, and navigation, with governed team sites for departments and shared business functions. Libraries were designed around how employees searched and secured content—not around every folder that existed before.

Permissions rebuilt around roles

We translated useful access patterns into Microsoft 365 groups and SharePoint groups, then retired most direct user permissions. Sensitive finance and people content remained separated. External collaboration was limited to approved sites with named owners and guest review dates.

Pilot, delta, and validation

Two departments piloted navigation, search, sync behavior, and permission mappings. Migration waves followed with pre-scan remediation, initial copy, delta sync, and business-owner validation before the old locations became read-only.

Governance the internal team could operate

The handoff included site request criteria, naming standards, owner responsibilities, sharing rules, lifecycle reviews, and a lightweight decision log. Department owners learned how to manage membership and content without becoming SharePoint administrators.

Delivery sequence

Results

• Approximately 1.2 TB of active business and project-support content moved into governed SharePoint sites
• Active engineering design files stayed on purpose-built storage instead of being forced into SharePoint
• Eleven destination sites replaced a web of departmental shares and ad-hoc collaboration spaces
• Direct user permissions were replaced with role-based group membership wherever practical
• Employees gained one intranet entry point for policies, news, department resources, and shared services
• IT received named owners, lifecycle rules, and a repeatable process for future site requests

What this engagement was not

It was not a promise that every file belonged in Microsoft 365. The better outcome came from keeping specialized engineering workloads where they performed best while moving collaboration content into a structure designed for search, sharing, and ownership.