An employee knows a document is somewhere on the shared drive. They remember the customer, the project, and roughly when the work happened, but the filename is unhelpful and three folders contain a copy.
Moving from shared drives to document management software can make records easier to find and give staff clearer control over document work. The move also needs to preserve the information people currently get from folders, permissions, filenames, and their own experience.
Use this migration checklist to plan the files, decisions, tests, and handover needed for a controlled move. It applies whether your shared drive is on a Windows server or a network storage device. The import method and supported features depend on the document management product you choose.
If you are still choosing the destination, the SharePoint and dedicated document management comparison can help you establish which approach fits your work.
1. Define the first part of the move
Choose a manageable starting point, such as one department's active contracts or a clearly defined set of project records. Identify the business owner who can decide what belongs in that collection and accept the result.
Describe success through tasks staff need to complete. For example: an authorized employee can find a contract by customer number, open the correct version, and see the information needed to act on it.
2. Inventory the shared drives before setting a date
Build an inventory with source paths, file counts, total storage, file types, sizes, and relevant timestamps. Group it by department or document collection so a business owner can review something recognizable.
Include difficult items in the assessment: unusually long paths, large files, password-protected documents, unreadable files, shortcuts, and file types the destination may store but cannot preview or process. A spreadsheet and a scanned PDF can have very different import and search requirements.
Check what relies on the drive. Spreadsheet formulas, application attachments, scanner destinations, scheduled jobs, and links in other documents may point to the old paths. Uploading the files does not automatically repair those connections.
3. Decide what moves, stays, or needs review
Separate active business records, historical material, and items requiring a decision. An archive can remain useful without receiving the same setup and cleanup effort as documents employees handle every day.
Have the responsible business owner decide how retention requirements and existing holds affect the scope. A migration should not quietly become a document disposal exercise.
Review duplicates in context. Two files can contain the same bytes and still belong to different customer or project records. A technical duplicate report can identify candidates, but the business must decide whether to keep separate records, use a supported link, or consolidate them.
4. Turn folder context into useful document information
Metadata is the information attached to a document, such as its customer number, document type, project, date, or status. In a shared drive, much of that information may be implied by the folders above the file.
Map those clues to the fields and document categories your destination actually supports. Start with information staff need for retrieval, access, and routing. Every required field also creates a question about what to do when the source does not provide a reliable value.
| What the shared drive tells you | Possible destination | Decision to confirm |
|---|---|---|
| A folder named Customer 1048 | Customer number field | Does 1048 identify the same customer in the current business system? |
| A folder named Contracts | Document category | Does every file belong to that category, including attachments and working drafts? |
| A year folder named 2024 | Year or source folder field | Is this the document year, project year, or simply the year someone filed it? |
| A filename containing signed or final | A value requiring review | Who can confirm the document version and its actual approval or signing status? |
| An old network path | Source location field or migration record | How will staff trace the imported document back to its original location? |
Consider a hypothetical engineering consultancy with folders organized by customer, project, and year. A folder labelled 2024 might contain a contract signed in 2023 for work completed in 2024. Automatically treating that folder name as the signing year would change the meaning of the record.
Keep uncertain values visible for review. Preserve original source details separately when they are needed for traceability. Confirm how the importer handles original timestamps, import dates, and the account performing the load.
5. Map permissions and historical versions explicitly
Shared drive access can depend on both share permissions and file or folder permissions. A document management system may use a different combination of groups, document categories, and record restrictions. Agree on the intended access in the destination and test what users can actually do.
Include direct document access, previews, search results, and downloads. An employee who cannot open a file may still learn something confidential from a title or search result if restrictions are incomplete. The business application access-control guide explains how to define responsibilities before configuring them.
Decide separately how earlier versions and approval evidence will carry forward. Files named final, final2, and signed do not establish a trustworthy version sequence on their own. Existing backup snapshots, version stores, or history from another application may require a separate export or archive.
6. Prove the import with a representative pilot
Choose pilot files that reflect the difficult parts of the collection as well as routine work. Include a poor scan, an unusually large file, missing information, a repeated filename from another folder, a restricted record, and a document with a known earlier version.
Keep a migration record that connects each source item to its destination record or approved exception. Record the batch, result, and any error requiring attention. This makes it possible to investigate a missing item without relying on someone remembering where it went.
Test what happens when a batch is interrupted and resumed. Establish how a repeated import recognizes work already completed and avoids creating unintended copies or applying the same change twice.
7. Verify complete records, search, and everyday use
Reconcile the inventory with the import results. Every item in scope should have an explained outcome. Counts may differ when an approved rule combines copies, creates several records, or handles versions separately, so document those rules alongside the totals.
For files intended to remain unchanged, file hashes can help compare transferred bytes with the source version captured for that batch. If a process converts a file or creates a searchable derivative, keep the original and validate the transformed result separately. A matching file does not establish that its customer number, permissions, or document category are correct.
Have staff find documents using the information they remember, such as a project number or a phrase inside a scan. Check whether OCR and indexing have finished before judging search results. Confirm the product supports the file formats, recognition, and search behavior your team needs.
8. Control changes during the final move
An inventory becomes out of date when staff continue editing, renaming, moving, deleting, or adding files. Define how the migration will identify those changes and how the final load will handle each type.
For some collections, a planned pause in editing is sufficient. Others need an initial load followed by a final update. Establish a clear point when the old location stops accepting changes and the new system becomes the place to work.
Tell staff what happens to urgent documents received during that window. Assign someone to track them through the handover so they do not disappear into a temporary folder or get processed twice.
9. Rehearse recovery and train the people doing the work
Preserve a protected source copy or suitable backup before the final move, and confirm it can be recovered. Define the conditions that would pause the migration or require a return to the earlier working arrangement.
Recovery gets more complicated once staff start changing records in the destination. Agree how those new documents, edits, and decisions would be preserved and reconciled if the team had to return to the old system. Include responsibilities and expected recovery time in the plan.
Train employees on familiar tasks: finding a document, adding the right identifying information, submitting review work, correcting a mistake, and asking for help. Give them instructions for their collection's actual cutover date and working location.
10. Sign off before retiring the old share
Set a go-live decision with the business owner and the people responsible for access and operation. Review the reconciliation results, unresolved exceptions, user testing, and support arrangements together. Assign a named owner and deadline to each accepted exception.
Retire the old location through a planned sequence. It may remain as a restricted, read-only reference for an agreed period while staff confirm the new working arrangement. Verify the restriction works for ordinary users and for automated processes that previously wrote files there.
Confirm backup and recovery for the new system as well. Keeping a copy of the original shared drive protects the starting point; it does not protect documents and decisions created after the move.
What should the migration proposal include?
Ask for the source collections, inventory assumptions, metadata mapping, permissions plan, treatment of versions, pilot, validation evidence, cutover, and support responsibilities in the scope. Identify who supplies business decisions and corrects ambiguous information.
File count and storage volume help size the job, but they do not describe the effort of rebuilding document context. Our business data migration cost guide explains how cleanup, mapping, rehearsals, and cutover affect the estimate.
Separate the software purchase from the migration work. A product may support batch upload while still requiring additional preparation, mapping, or import development for your collection.
Where Apex fits in the move
Apex Document Management provides document drawers, custom indexing fields, batch capture, OCR, search, document versions, and user and group access controls. Those features can support a destination organized around the information and tasks your team needs.
The migration still needs a verified approach for your files and their context. The available import path, field mapping, access rules, version treatment, and any connections to other software must be agreed for the project. Existing shared drive permissions and historical activity should not be assumed to transfer automatically.
Honor Tech can discuss the move as part of document workflow automation, including which requirements fit Apex configuration and which need separately scoped migration or development work.
Discuss your document migration. Describe the shared drives, approximate file count and storage, main document types, access restrictions, and the work staff need to complete after the move. That gives us a practical starting point for defining a pilot and an implementation scope.