Cloud Document Migration Checklist: Move Scanned Files Without Losing Searchability or Control

Overview

A cloud document migration should produce a better working system, not simply a new storage location. Before you move files, decide what belongs in the destination, how each document should be named and classified, who may access it, and how you will prove that the transfer was complete.

This is especially important for scanned documents. A PDF may look correct while its OCR text is missing, its pages are out of order, or its metadata has been stripped during export. A migration can also create duplicate files when the same receipt, contract, or form exists on a desktop, shared drive, email attachment, and legacy system.

Use the checklist below as a working document. Adapt the fields to your cloud document management platform, retention requirements, internal security rules, and the sensitivity of the records involved. Platform features, import limits, export formats, audit options, and storage controls can change, so verify those details before each migration rather than relying on an old runbook.

Migration inventory worksheet

• Source: Record the desktop, shared drive, email archive, scanner workstation, application, or legacy repository where files currently reside.
• Owner: Identify the department or person responsible for confirming that the documents are complete and usable.
• File types: List PDF, image, word-processing, spreadsheet, email, and archive formats separately.
• Approximate volume: Capture file count, folder count, and total storage size. Include an estimate of unusually large files.
• Sensitivity: Mark records that contain personal, financial, health, contractual, confidential, or regulated information.
• OCR status: Note whether files already contain searchable text, require OCR, or need manual review.
• Retention status: Separate active records, reference material, duplicates, obsolete files, and records subject to a hold or review.
• Migration decision: Assign one outcome: migrate, archive, request owner review, convert, or exclude with a documented reason.

For folder structures and naming conventions, see How to Organize Scanned Documents in the Cloud. Establish those rules before the transfer so people do not recreate inconsistent filing habits in the new system.

Checklist by scenario

Desktop folders and local scanner directories

• Ask each owner to identify local folders, downloads, temporary scan directories, and files stored outside the standard path.
• Freeze or document the naming convention used during the final collection period.
• Remove obvious temporary exports only after the owner confirms they are not the authoritative copy.
• Compare file counts and sizes before and after transfer.
• Confirm that the scanner output is readable, correctly rotated, and in the required PDF or image format.

Shared drives and network folders

• Export a folder and permission inventory before changing access.
• Identify inherited permissions, public or broad groups, dormant accounts, and folders with unclear ownership.
• Map the old folder path to the new location and preserve the original path in metadata when it supports traceability.
• Review duplicate copies created by years of departmental sharing.
• Run a pilot with representative folders, including a large folder, a deeply nested folder, and a folder containing unusual file types.

Email archives and attachments

• Define which messages and attachments qualify as records before collecting them.
• Preserve the sender, recipient, date, subject, and attachment relationship when that context matters.
• Prevent repeated attachments from becoming separate authoritative documents without a reason.
• Scan exported attachments for unsupported formats, corruption, and password protection.
• Assign meaningful metadata instead of relying only on an email subject line.

Legacy document management systems

• Document the legacy system’s export format, folder hierarchy, metadata fields, version behavior, and audit information.
• Export a sample with multiple versions, comments, approvals, and attachments if those features exist.
• Decide which history must be preserved in the new system and which history will remain in a controlled archive.
• Test whether the destination accepts the required characters, dates, file names, page counts, and file sizes.
• Keep a read-only copy or verified backup until the migration has been accepted and the agreed rollback period has ended.

Scanned receipts, invoices, and forms

• Group records by business process, such as vendor, project, employee, customer, or accounting period.
• Use OCR to make text searchable, but do not treat extracted text as automatically accurate.
• Validate dates, totals, invoice numbers, names, and other fields used for retrieval or automation.
• Check that multi-page records remain together and that blank pages or duplicate scans are handled consistently.
• Retain the original image or source file where your process requires it, and record any conversion performed.

For a focused process, use the OCR workflow for scanning receipts and invoices into searchable PDFs before adding those files to the migration batch.

Migration mapping table

Prepare a mapping table that can be reviewed by both the technical owner and the business owner:

What to double-check

OCR and document quality

Open a sample from every meaningful source and document type. Search for a word that is clearly visible on the page, then compare the result with the image. Check dates, numbers, names, tables, handwriting, stamps, and low-contrast pages because these often need closer review. Confirm page order, orientation, legibility, and whether searchable text is embedded in the final PDF.

Use a defined acceptance threshold for each batch. For example, a business owner might review a fixed sample from each source and require every critical field to be accurate before approving the batch. The right threshold depends on the document’s purpose and risk; do not use the same review standard for a casual reference scan and a contract or financial record.

Permissions and security

• List who can view, edit, download, share, delete, restore, and administer the migrated files.
• Replace broad legacy access with role-based groups where practical.
• Confirm how external sharing, link access, guest users, and administrator access are controlled.
• Review encryption, authentication, audit logging, retention, and export controls in the destination platform’s current documentation.
• Do not place sensitive files in a test workspace with wider access than the production destination.

Permission mapping is also part of document approval and signing design. If migrated documents will later be reviewed or signed, align ownership and access with the process described in the document approval workflow guide.

Backup, rollback, and evidence

Before the production transfer, define the backup location, responsible person, verification method, and retention period for the source copy. Record the migration date, source inventory, destination, tool or method used, batch identifiers, exceptions, and approval status. A backup that cannot be restored or inspected is not a complete recovery plan, so test a small restoration before relying on it.

Test migration workflow

1. Select representative files from every source, format, sensitivity level, and document type.
2. Copy them to a controlled test area without deleting or changing the originals.
3. Apply the proposed naming, metadata, OCR, and permission rules.
4. Check counts, file integrity, searchability, previews, page order, metadata, and access behavior.
5. Ask business owners to complete realistic searches and retrieval tasks.
6. Log defects, correct the mapping, and repeat the test until acceptance criteria are met.

Common mistakes

• Uploading everything first: Unreviewed duplicates and obsolete files make the new system harder to search. Inventory and classify before transfer.
• Assuming every PDF is searchable: A scanned image may need OCR. Test search behavior rather than judging by appearance.
• Preserving a confusing folder tree: A faithful copy of poor organization preserves the problem. Use metadata and clear categories where they improve retrieval.
• Ignoring permissions until the end: Access errors are harder to fix after files are shared. Map groups during planning and test with ordinary user accounts.
• Discarding the source too soon: Keep a verified, controlled copy until owners approve the migration and the rollback period is complete.
• Overlooking versions and context: Contracts, approvals, emails, and forms may depend on history or relationships. Decide what context must travel with each document.
• Changing the workflow during migration: Separate file transfer from process redesign when possible. If both change, record which change caused each result.

If the migration includes contracts or documents that will be signed after transfer, review the electronic signature compliance checklist and confirm that the destination preserves the records and signing evidence your workflow requires.

When to revisit

Revisit this checklist before each department migration, platform replacement, or seasonal planning cycle. It should also be reviewed when the source system changes, the destination changes its import or export behavior, a new document type is introduced, access groups are reorganized, or the business begins using OCR, automated routing, or e-signature workflows.

At the end of every migration, schedule a short post-migration review. Confirm that users can find representative records, owners have approved the results, exceptions have an assigned action, and the backup or rollback plan is still available. Compare the original inventory with the destination report and record any files intentionally excluded.

Post-migration sign-off template

• Migration name and date: ____________________
• Source systems and batches: ____________________
• Destination workspace: ____________________
• Files inventoried / migrated / excluded: ____________________
• OCR and search validation completed by: ____________________
• Permission review completed by: ____________________
• Exceptions and corrective actions: ____________________
• Backup verified and rollback date: ____________________
• Business owner approval: ____________________
• Technical owner approval: ____________________

Once the sign-off is complete, publish the new location, naming rules, search guidance, and support contact. A migration is finished only when the people responsible for the records can use the new cloud document management system confidently and the organization can explain what moved, what did not, and why.