In a paper-to-cloud migration, records usually go missing because nobody put them on the inventory. If a box of 1987 property deeds is left off your list, it can drop out of the project entirely, and you may not notice the gap until an auditor asks for one of them.
This cloud migration checklist is built around a verification loop that catches that missing box. You count the files before the move, count them again after, and confirm them with checksums, digital fingerprints that change if a file changes. Generic checklists tend to skip that loop.
Build a Data Migration Plan for the Paper Archive
Before anyone scans a single page, you need to write down what’s moving, where it’s going, and how you’ll know it arrived. A workable data migration plan for a paper archive covers 6 things:
- Scope: which locations, departments, and date ranges are included
- Ownership: who runs the project, who approves each phase, and who signs off at the end
- Retention: how long each record type has to be kept, which decides what you send for scanning and what you schedule for destruction
- Destination: cloud storage, a document management system (DMS), or both
- Verification: how files will be counted and checked
- Decommissioning: when the paper can go, and who approves it
Retention periods can vary a lot, even under one agency’s rules. The IRS record-keeping guidance generally sets a 3-year period for tax records, but 7 years for a bad debt or worthless securities claim, and at least 4 years for employment tax records.
Property records follow a longer rule. The IRS generally says to keep them until the period of limitations, the window the IRS has to assess additional tax, expires for the year you dispose of the property. If the property was sold in the last few years, you may still need those 1987 deeds.
Finance teams can map these periods into their financial record-keeping system before the archive moves.
Settle legal holds, which freeze disposal for records tied to litigation, and decide who approves disposal before the first box moves. The companion guide to legacy records migration compliance walks through both.
Inventory Every Box Before Anything Moves
Give every box an ID and a line in the inventory before it leaves its shelf. For each one, capture:
- a unique box ID or barcode
- current location
- department and record series
- date range
- retention category and any legal hold
- condition notes, such as fragile pages, staples, bindings, or oversized sheets
- an estimated page count
Page estimates set both budget and timeline. Calculating how many boxes you have turns shelf space into a rough page count.
At the end of the project, you’ll check what arrived against this inventory, so lock the version you send to the provider and log every change after that.
Index Everything, Digitize Paper Archives Selectively
For a large archive, scanning everything is rarely the most economical choice. The usual answer is to index every box, scan the files people actually request, and keep the rest in retrievable storage.
Indexing means recording enough about each box or folder (names, dates, account numbers, record types) to find it later without opening it. With a solid index, inactive records can stay in a provider’s offsite records storage, where the provider can pull any file on request, and many providers can scan it on demand.
For scanned files, document indexing decides how searchable your cloud archive will be. Choose index fields once and use them for both the paper boxes and the digital files.
Scanning everything up front makes sense in narrower cases. It fits when the paper has to be out of a building by a set date, when many people need the same files every day, or when the records are fragile enough that handling them once is safer than handling them repeatedly.
Batch the Document Migration So Nothing Gets Skipped
Once you’ve decided what to digitize, get free quotes from document scanning providers and plan the work in batches. A batch is a set of boxes that the provider picks up, scans, and checks as a unit, with its own manifest listing every box and folder in it.
Providers in our network typically prep each batch by removing staples and flattening folds, then scan, index, and run quality control on it. They also log each box with a barcode and a signed manifest at every handoff, so the chain of custody (the record of who held each box, and when) stays intact across every location the boxes come from.
Ask the provider for an exceptions list of anything they couldn’t image cleanly. Oversized drawings and maps usually travel in their own batch, since they need large-format equipment, and construction archives tend to have a lot of them.
Nobody can give a reliable timeline before seeing the archive. It depends on page count, paper condition and prep time, image resolution and color requirements, indexing depth, the size of the quality-control sample, and how quickly your team approves each batch.
Your own prep can shorten it, since files you sort and pull before a scanning project need less handling from the provider. Providers in our network take on batch projects like this in cities from Reno, NV, to Chattanooga, TN.
Verify the Migration With Counts and Checksums
Run all 3 checks on every batch:
- Count before. Record the boxes, folders, and estimated pages in the batch, straight from the inventory.
- Count after. Reconcile the files and pages delivered against the batch manifest, and resolve every gap before the next batch starts.
- Confirm every file with checksums. Generate a checksum for each file at handoff, recalculate it after upload, and compare the two values.
A checksum is a short fingerprint calculated from a file’s contents, and if even one bit of the file changes, the fingerprint changes. Use SHA-256, one of the algorithms in Federal Information Processing Standard (FIPS) 180-4, the federal Secure Hash Standard. Skip SHA-1, which the National Institute of Standards and Technology (NIST) has scheduled to phase out by the end of 2030.
Checksums prove a file didn’t change in transit. They can’t prove the scan was right in the first place, so pair them with a visual check, pulling a sample from each batch and comparing the images to the paper page by page.
Pick Where the Data Migration Plan’s Files Live Long-Term
Cloud storage is the simpler option. The storage provider supplies encryption, redundant copies, and access-control tools, though deciding who should have access to what stays your job. It suits records people retrieve by name or date, as long as the provider can answer basic cloud storage security questions about encryption and access.
A document management system adds structure on top. It typically gives you searchable index fields, version history, and an audit trail of who opened or changed each file, and many platforms can apply retention rules that flag records when they’re due for disposal.
For a regulated archive, those features automate tracking that the paper system handled by hand. Many organizations use both, keeping the files encrypted and access-controlled in the cloud and managing them through a DMS.
Decommission Paper Once the Document Migration Is Verified
Keep the originals through a dual-running period. That’s the stretch after migration when the paper and the digital files exist side by side, so anything missing from the cloud can still be found on a shelf.
The period ends when every batch has passed reconciliation, the sample checks are signed off, and retention and hold reviews are complete. The National Archives and Records Administration (NARA) sets the same order for federal agencies, and while its rules don’t bind private organizations, they’re a useful model. NARA’s digitization rules let agencies destroy digitized source records only after validating that the digitization meets NARA’s standards.
Some originals should stay regardless, such as records whose legal value depends on the physical document. Ask counsel about anything carrying original signatures or recording stamps, which covers much of what real estate and title files hold, including those 1987 deeds.
When the rest of the paper goes, use a provider certified to NAID AAA, the secure destruction standard from the International Secure Information Governance & Management Association (i-SIGMA). Ask for a certificate of destruction, and make it a line in the contract.
Paper-to-Cloud Migration FAQ
It depends on page count, paper condition, prep work, image specifications, indexing depth, and how fast your team approves batches. A good quote spells out those assumptions, so be wary of a firm timeline offered before anyone has seen the boxes.
For most large archives, index everything, scan the frequently requested files, and keep the rest in retrievable storage. Scanning everything up front pays off mainly when the space has to be cleared by a deadline or the files are in daily use.
The dual-running period is the stretch after migration when the paper originals and the digital files exist side by side. It gives you time to find and fix anything missing before the originals go for destruction.
Count files before and after each batch, and reconcile any difference against the manifest. Then confirm every file with checksums, and check a sample visually against the paper.
Only after every batch has passed verification, retention periods and legal holds have been checked, and the project owner has signed off. Records whose value depends on the physical original may need to be kept even then.
Matching Your Archive With Scanning and Storage Providers
Record Nations connects you with certified, vetted providers who can handle the scanning, indexing, cloud records storage, and end-of-project disposal your checklist calls for. On the records side, look for PRISM Privacy+, i-SIGMA’s certification for records and information management. Record Nations is an i-SIGMA member.
Fill out our form or call (866) 385-3706 to get free quotes. You’ll often receive multiple competitive quotes within minutes or the hour, and generally by day’s end, depending on how integrated each provider is.
