This is part 6 of 8 in our Intelligent Migration series for ECM and DAM initiatives. In our second case study, a manufacturer brings decades of paper and network file share content under records management.
A manufacturing company had two information problems that looked very different on the surface.
One was physical: several closets filled with paper records.
The other was digital: a network file share containing material dating back to the late 1990s.
Together, the two sources contained more than ten million documents. The organization needed a way to identify what it had, preserve useful information, and place the content under classification. Scanning the paper and copying the network files would have changed the format and location without resolving the underlying governance problem.
Two Sources, One Information Problem
Paper archives and file shares lose context in different ways.
Scanned paper can retain the image while losing document boundaries, indexing, ownership, and useful metadata. Network folders may contain filenames and paths that offer clues, but those clues can reflect outdated department structures, individual habits, duplicates, or years of accumulated workarounds.
The manufacturing company needed both populations to arrive at the same end state: searchable, structured information that could be governed consistently.
Paper First
A scanning vendor digitized the physical files and transferred the images for analysis. Intelligent Migration classified the scans and extracted the metadata required for the recognized document types.
The document types known at the beginning represented about 85% of the scanned population. Within that known population, classification accuracy reached 96%.
That left an important question: what should happen to documents the system had not been taught to recognize?
Human Review Expanded What the System Could Understand
Risetime content analysts reviewed the remaining material rather than treating unrecognized documents as errors to ignore.
When reviewers identified a recurring document type that was new to the model, they classified examples and used those examples to expand what the system could recognize. The newly learned type could then be applied across the larger population.
This created a learning loop. Automation handled established patterns at scale, while human expertise concentrated on exceptions and new document families. Organizations exploring that balance can also review Risetime’s perspective on content quality assurance and AI.
Then the Network Files
The network file share went through the same classification, metadata extraction, and review process. Some scanned images on the file share had never been processed with OCR, so text extraction was added where necessary before analysis.
The source was different, but the governance objective remained consistent.
What Changed After Migration
The classified content and metadata were loaded into OpenText Content Server and assigned the appropriate classifications. OpenText was the customer’s selected repository, but the structured output was portable to other document management systems with suitable APIs.
One year after the migration, the organization was able to destroy the physical source records and remove the migrated documents from the network file share.
That outcome matters because the project did not leave the original sources running indefinitely “just in case.” The organization had enough confidence in the classified and governed environment to retire the legacy sources after the required controls were in place.
More than ten million documents are now searchable, structured, and governed within one managed environment.
What This Case Shows About Large Scale Migration
Scale does not eliminate the need for context. It makes context more important.
Large document populations need a process that can recognize known patterns efficiently, expose exceptions clearly, and incorporate human expertise when new or ambiguous content appears. That combination prevents migration from becoming another bulk transfer of unresolved information.
It can also create the conditions for legacy source retirement, which is where much of the operational value of modernization becomes visible.
Organizations working through large scanned archives, network file shares, or mixed legacy repositories may also need managed services to support the environment after migration. To discuss a content population that needs to move from storage into governance, contact Risetime.