How do I use metadata reports to validate a file migration?

Generate a report before migration and another after. Compare file counts, sizes in bytes, and MIME types between the two outputs. Any discrepancy — missing file, size mismatch, unexpected type change — surfaces immediately in the diff.

Can this catch file corruption during transfer?

A size mismatch between source and destination is a strong signal of truncation or corruption. However, a file can be corrupted and still match in size. For full integrity assurance, pair metadata comparison with checksum verification.

What file formats are supported?

PDF, Excel (xlsx/xls), CSV, DOCX, TXT, ZIP, JSON, PNG, JPG, JPEG, and WEBP are all supported — covering the most common formats in enterprise and departmental file migrations.

What is the batch size limit?

Up to 50 files or 2GB per batch. For large migrations, process in batches and merge the JSON outputs into a single comparison dataset.

File Metadata Reports for Data Migration Validation and Pre-Cutover Audits

Data migrations fail at the edges — files that arrived truncated, in the wrong format, or not at all. The File Metadata Report tool produces a structured JSON inventory of every file in a batch, capturing size, MIME type, and timestamps, so you can compare pre- and post-migration states with a concrete, reproducible record rather than a manual spot check.

Create free account

Migration projects live and die by their validation steps. Running a metadata report against the source file set before migration and again against the destination set after transfer gives you a direct, diff-able comparison: every file accounted for, every size matched, every timestamp in the expected range. This is especially valuable for migrations involving hundreds of files across mixed formats — PDFs, spreadsheets, archives, documents — where manual verification is not realistic.

Deliteful processes up to 50 files per batch across all formats common in enterprise file migrations: PDF, Excel, CSV, DOCX, ZIP, JSON, TXT, and images. The flat JSON output structure is consistent across file types, making it straightforward to load both the source and destination reports into a comparison script or spreadsheet and identify discrepancies before cutover is declared complete.

How it works

1
Run a metadata report on the source file set
Upload the pre-migration files and generate a JSON inventory capturing name, size, type, and timestamps.
2
Complete the migration and upload the destination files
After transfer, run the same report against the files at the destination.
3
Compare the two JSON reports
Diff the source and destination outputs to confirm every file arrived intact — same name, same size, expected format — before signing off on cutover.

Frequently asked questions

How do I use metadata reports to validate a file migration?: Generate a report before migration and another after. Compare file counts, sizes in bytes, and MIME types between the two outputs. Any discrepancy — missing file, size mismatch, unexpected type change — surfaces immediately in the diff.
Can this catch file corruption during transfer?: A size mismatch between source and destination is a strong signal of truncation or corruption. However, a file can be corrupted and still match in size. For full integrity assurance, pair metadata comparison with checksum verification.
What file formats are supported?: PDF, Excel (xlsx/xls), CSV, DOCX, TXT, ZIP, JSON, PNG, JPG, JPEG, and WEBP are all supported — covering the most common formats in enterprise and departmental file migrations.
What is the batch size limit?: Up to 50 files or 2GB per batch. For large migrations, process in batches and merge the JSON outputs into a single comparison dataset.

Create your free Deliteful account with Google and start building pre- and post-migration file inventories for your next cutover validation.