Migrating scanned documents between cloud platforms is safest when treated as a controlled records project, not a simple file copy. This checklist covers how to inventory documents, preserve searchable OCR, map permissions, verify transfers, and maintain a rollback path before retiring the old system.
Overview
A cloud document migration can affect more than storage. Scanned PDFs may contain OCR text, custom metadata, folder structures, retention rules, sharing links, version history, approval records, and e-signature evidence. A download-and-upload process may preserve the visible page while losing the information that makes the file searchable, governed, or useful in a business workflow.
Start by defining what “successful” means for your organization. A practical migration objective might be: every in-scope file is transferred, opens correctly, remains searchable where required, has the right owner and access level, and can be found using its existing metadata or a documented replacement. If signed documents are included, decide how you will preserve the completed document, audit trail, certificate, or other associated evidence supported by the source platform.
Before selecting a transfer method, review the source and destination platforms’ current export formats, API capabilities, bulk-download limits, integration options, encryption settings, and data-residency choices. These details can change, so confirm them during planning rather than relying on an old implementation note. The cloud document migration checklist can be used alongside this workflow for a broader project record.
Build an inventory spreadsheet
Create a read-only baseline inventory before moving anything. At minimum, include:
- Source path, folder, file name, and file type
- File size, page count, version number, and last-modified date
- Document owner, department, and business process
- OCR or searchable-text status
- Tags, document dates, customer or project identifiers, and other important metadata
- Permission group, individual access, external sharing status, and sensitivity classification
- Retention category, legal hold status, or deletion restriction where applicable
- Destination folder, destination owner, migration batch, and validation result
- Source checksum or another stable identifier, if available
Separate active records, archives, duplicates, temporary scans, and documents that should be deleted under an approved retention process. Do not use migration as an excuse to make undocumented deletion decisions. For retention planning, see the scanned document retention schedule.
Checklist by scenario
Scenario 1: Moving ordinary scanned PDFs
- Confirm the source export includes the original PDF files and any metadata that the destination needs.
- Record whether each PDF is image-only, searchable, password-protected, encrypted, or damaged.
- Choose an export format that avoids unnecessary conversion. If the source provides a native bulk export, test it on a representative sample first.
- Preserve the original file name and path in a migration log, even if the destination uses a different folder structure.
- Transfer a pilot batch containing small and large files, multiple page counts, unusual characters in names, and files from different departments.
- Open and search the pilot files in the destination before transferring the remaining batches.
Scenario 2: Moving OCR PDFs and document-processing outputs
OCR is easy to overlook because the visual pages may appear unchanged after migration. For each batch, test whether text can be selected, searched, copied, and found using expected terms such as an invoice number, customer name, or date. Compare a sample of extracted text with the source version, paying particular attention to tables, rotated pages, handwriting, low-contrast scans, and characters that OCR commonly confuses.
Keep a validation sample rather than checking only a few easy documents. A useful sample includes normal files, exception files, and documents that drive downstream automation. If the destination reprocesses OCR, record the engine or workflow version used by the destination and treat the result as a transformation that requires review.
Scenario 3: Moving signed contracts or approval records
Do not assume that uploading a completed PDF preserves the complete signing record. Identify whether the source stores the signed document, audit trail, certificate, timestamps, signer details, envelope or transaction identifier, and related attachments separately. Export and map each required component before the source account is closed.
Preserve the relationship between a contract and its supporting signature evidence. If the destination cannot represent the source structure, use a documented folder or metadata convention and restrict access to the evidence files. Teams planning a wider rollout can also review the e-signature implementation checklist and guidance on electronic signatures, legal validity, and audit trails.
Scenario 4: Moving documents for remote teams
Remote access makes permission mapping especially important. Create a permissions map with columns for source group, source role, destination group, destination role, external-user treatment, owner, and approval date. Translate access by job function rather than copying every individual permission blindly. Remove stale accounts and review guest access as part of the migration, but record each intentional change.
Test the destination as different users: a standard employee, department manager, administrator, external collaborator if applicable, and a user with no access. Confirm that search results, previews, downloads, sharing, and editing behave as intended for each role.
Scenario 5: Moving files connected to scanning and e-signature workflows
List every integration that creates, reads, routes, or signs documents. This may include an online document scanner, OCR document scanner, form system, ticketing tool, accounting platform, or contract signing app. Pause or redirect automated jobs during each cutover window so new documents do not arrive in the old system after its final export.
Check whether integration credentials, webhooks, folder watches, API tokens, templates, and approval routes need to be recreated. The cloud scan and e-sign integration comparison provides useful questions for reviewing these dependencies.
What to double-check
Export-format checklist
- Original PDF or image files are included, not only previews.
- OCR text, searchable PDF layers, tags, and metadata are exported or have a documented replacement.
- Versions, comments, notes, annotations, and linked attachments are accounted for.
- Signed-document evidence is exported separately when the platform does not package it with the PDF.
- Encrypted, password-protected, oversized, corrupted, and unsupported files have an exception plan.
- File names, paths, timestamps, and character encoding survive the transfer.
Security and data-residency review
Use a transfer method approved for the sensitivity of the records. Confirm encryption in transit and at rest, administrator access, temporary export locations, local download exposure, logging, and deletion of staging copies. If the organization has data-residency or contractual requirements, verify where exports are generated, where temporary files are stored, and where the destination retains the data. A vendor review can start with the cloud document scanner security questionnaire.
Reconcile files and checksums
After each batch, compare the source inventory with the destination inventory. Reconcile at least file count, total size, path or mapped identifier, and exception count. Where the platforms expose checksums, compare a cryptographic hash of the exported file with the transferred file. If the destination transforms files or generates a new OCR layer, compare the original file hash separately from the transformed derivative and document the reason they differ.
Do not treat a matching file count as proof that the migration worked. A duplicate can inflate the count, while a missing attachment can remain hidden. Sample files by batch, owner, type, size, and sensitivity, then record the reviewer, date, and result.
Prepare a rollback plan
Keep the source system available in read-only mode until validation and business sign-off are complete. Define what triggers rollback, who can authorize it, how new documents created during the cutover will be handled, and how users will be told to return to the source. Preserve the source export, inventory, validation logs, and permissions map in a controlled location. Rollback is not simply restoring files; it also means restoring the operational path used to scan, search, approve, and sign documents.
Common mistakes
- Copying only visible files: This can omit OCR layers, versions, audit trails, attachments, or metadata.
- Starting without an inventory: Without a baseline, teams cannot distinguish a missing file from an intentional exclusion.
- Testing only successful documents: Exception files often reveal unsupported formats, OCR failures, or permission problems.
- Recreating permissions informally: Manual sharing can expose sensitive records or block legitimate users.
- Closing the old platform too soon: Keep a controlled read-only fallback until reconciliation and owner sign-off are finished.
- Leaving automations pointed at the old system: New scans, approvals, or signatures can be split across two repositories.
- Deleting staging exports immediately: Preserve them for the period required by your internal controls, then dispose of them securely.
When to revisit
Revisit this checklist before seasonal planning cycles, vendor renewals, acquisitions, storage-provider changes, platform consolidations, or a major change to scanning and e-signature workflows. Review it whenever the source or destination changes its export formats, API or bulk-download limits, encryption options, integrations, permission model, or data-residency configuration.
For an operational refresh, rerun the inventory on a defined sample, confirm that new document types are covered, test OCR search, review external access, and verify that retention and approval workflows still operate in the destination. Assign an owner and a review date to the migration record. A migration is complete when the business can find and use its documents safely—not merely when the transfer tool reports success.
Action checklist: name the migration owner, freeze the scope, export the inventory, test a pilot batch, map permissions, validate OCR and signatures, reconcile counts and checksums, obtain business sign-off, and only then schedule source-platform retirement.