Document Management & Migration for Manufacturing Company

Business challenge

The manufacturing facility operated across three unconnected network drives with no consistent file naming convention or folder structure. ISO 9001 compliance documentation lived in a separate system, requiring auditors to visit three separate locations to complete a review. Retention schedules were tracked in a spreadsheet with no automated enforcement. When a key procurement manager left the company, 800 supplier contract documents became undiscoverable by anyone else on the team. IT estimated employees spent an average of 18 minutes per day searching for documents — over 1,500 person-hours wasted per month across the 500-person workforce. The incoming quality director had a mandate to achieve ISO 9001 re-certification within 12 months, and the current document infrastructure made that target unrealistic without a significant system overhaul.

Implementation approach

The project began with a three-week content audit conducted alongside department heads and the ISO coordinator. We catalogued all 15,200 documents across three network drives, identified 4,600 duplicates (30%), and agreed on a four-level metadata schema: Division, Department, Document Type (Policy / Procedure / Template / Record), and Fiscal Year. This schema was mapped to SharePoint Managed Metadata Service term sets for consistent taxonomy enforcement across all uploads. The migration used the SharePoint Migration Tool with a pre-migration script that applied metadata labels based on source folder paths, eliminating most manual tagging effort. Retention policies were configured in Microsoft Purview using the company's existing retention schedule, with a legal hold capability added for supplier contract disputes. Five custom filtered views were built for the most common daily use cases: active procedures, documents pending annual review, supplier contracts expiring within 90 days, ISO 9001 controlled documents, and recently modified files. Department champions received four hours of end-user training, and a two-page quick reference card was embedded in the site navigation. IT ran a six-month parallel decommission of the legacy network drives alongside the SharePoint rollout, ensuring no documents were lost during the transition.

Measurable outcomes

• 60% faster document search time
• 15,000+ documents migrated with metadata
• Compliance-ready retention policies

Project timeline

4 weeks including content audit and migration

Key takeaways for similar organizations

The most important decision was spending three weeks auditing before migrating. Organizations are tempted to move everything first and clean up later — but this transfers the chaos of legacy systems directly into SharePoint and immediately undermines user confidence. Removing 4,600 duplicates and agreeing on taxonomy before a single file moved meant the launch experience was clean from day one. For manufacturing companies facing ISO or regulatory audits, a filtered view of all controlled documents updated in the last 90 days delivers significant time savings during audit week. We recommend using Microsoft Purview retention labels rather than classic SharePoint policies wherever possible: the label-based approach supports both retention and deletion scheduling and integrates with eDiscovery for legal hold scenarios. Assign a Document Manager role from within the business — not IT — to own the term set and approve new metadata values. This governance decision is what keeps SharePoint document libraries useful three years after the project closes.

Six months after go-live, the quality director reported that the most recent ISO 9001 audit was completed in half the time of the previous cycle because auditors could access every controlled document from a single filtered view. The 18-minute daily document search time dropped to under three minutes per employee. If your organization is preparing for a compliance audit or planning a migration from legacy network drives, we recommend starting with a two-week content audit sprint before any SharePoint configuration begins — the time invested in governance upfront consistently delivers faster audits and lower IT overhead for years after the project closes.

Technical stack