Skip to main content

Migration reports

Updated

Availability: Migrate isn't offered for purchase or activation at launch. It's coming later. This page explains how Migrate works so you can plan client moves ahead of time. There's no Migrate pricing yet. To hear when it's available, submit a request.

Migrate generates reports for each job that summarize what was transferred, how many records succeeded or failed, and what errors occurred. Reports are available after a job reaches a terminal state and can be exported as CSV for documentation or client handoff.

Generating a Report

  1. Go to the job you want to report on.
  2. Click Reports (or go to the top-level Reports section and filter by job or project).
  3. Click Generate to produce the report. Report generation runs as an on-demand operation.
  4. Once generated, click Export CSV to download the report as a CSV file.

What a Report Contains

A migration report includes:

Record counts

  • Files scanned
  • Files uploaded successfully
  • Files verified (if verify_integrity was enabled)
  • Files errored
  • Total bytes transferred

Job metadata

  • Job name and type
  • Source and destination connector types
  • Start and end timestamps
  • Final status (Completed, Failed, Cancelled)

Error log

  • Each file or record that failed, with the error reason
  • Which batch the failure occurred in (identified by batch_id)

Staging summary

  • How much data passed through R2 staging
  • Staging cleanup scheduled date (7 days after terminal state)

Idempotent Progress Counting

Progress batches are ingested with a unique batch_id. If the agent retried a batch during the job (due to a network blip or restart), the duplicate was detected and not re-counted. The totals in the report reflect actual work done, not retries.

Usage and Billing

Migrate isn't sold at launch, so there's no Migrate pricing or billing yet. Migrate does measure the volume each job moves (you'll see it in job progress and reports). Treat that figure as a record of what moved, not as a charge.

Sharing Reports

The CSV export is the primary way to share migration results. Common uses:

  • Client sign-off documentation after a completed migration
  • Internal review of error records that need manual remediation
  • Compliance or audit records for regulated industries

FAQ

How long are reports available? Reports are stored in your Migrate account and are not automatically deleted. Staging data is cleaned up after 7 days, but the report records remain.

Can I generate a report for a job that is still running? Yes, but the counts will only reflect progress to the point of generation. Re-generate after the job completes for the final totals.

My report shows fewer bytes than expected. Why? Check whether any batches errored out — errored files do not count toward transferred bytes. Also confirm that verify_integrity errors did not leave files in a failed state. The error log in the report will show any items that did not transfer cleanly.

Related