See your migration
before any bytes move.
Run as many as you want. Tweak filters, change destinations, re-test after a source update — none of it counts against anything.
Mover walks your source, counts files, sums bytes, exercises both credentials, and prices the exact pack you'd need. The report tells you everything that would happen during the real migration — and what could trip it up — for free, every time.
What the dry run does
Five things scanned, every time.
The dry run is a real walk of the source and destination. It validates the same primitives the live migration uses — credentials, filters, file metadata, destination acceptance — so the answer it gives is the answer you get when the migration runs.
Every file on the source.
The dry run walks the entire source path you connect — every folder, every file. It applies your include and exclude patterns and reports the file count + byte total that would actually move.
The exact pack size you need.
The byte total maps directly to a usage pack. The result tells you whether a 100 GB pack, a 1 TB pack, or a 10 TB pack fits — without guessing or rounding up to a tier you don't need.
Filter and pattern correctness.
Include and exclude patterns get validated against the real source. If a pattern excludes more than you expected (or includes a directory you meant to skip), the dry run surfaces it before any data moves.
Unsupported filenames and path issues.
Filenames the destination can't accept — illegal characters, paths past the destination's length ceiling, case-collision conflicts — get flagged here so you can fix them once instead of failing partway through a multi-TB transfer.
Permission and credential checks.
The connection to both source and destination is exercised the same way the real migration would exercise it. Bad credentials, scope mismatches, and API rate-limit anomalies surface during the dry run, not at hour 6 of a 10 TB job.
What the dry run doesn't do
No writes. No charges. No egress.
Three guarantees worth stating plainly. The dry run is a read-only walk; the destination never sees a byte until you commit.
No bytes move.
The dry run reads metadata from the source — it never writes to the destination and never copies file contents. Zero impact on your usage pack and zero risk to the destination.
No charges.
Dry runs are free, always. You can run as many as you want — to test pattern changes, sanity-check after a source update, compare two destination options — without any of them counting against your pack.
No provider egress.
Source providers that charge for data egress (like S3) don't charge for the metadata reads the dry run does. The provider-side cost line in the dry run estimate is what the real migration will incur — not anything the dry run itself triggered.
See the size, the cost, and the gotchas first.
No procurement conversation about pack size starts with guessing. Run the dry run, get the byte total, buy the matching pack. The result is the number on your invoice — not the number rounded up to the next tier.
Iterate on filters without burning anything.
Include and exclude patterns are easy to write and easy to get wrong. Run the dry run, see what each pattern actually catches, adjust, re-run. Every iteration is free, so the patterns can be exactly right by the time the real migration starts.
Re-validate before the next incremental run.
If the source has changed materially since the last migration — new directories, new permission model, structural reshape — the dry run is the cheap way to find out what the next incremental run would do before it does it.
Run a dry run for free.
Connect both sides, pick what to migrate, and Mover walks the source while you make coffee. The report waits for you — the only thing it costs is the time to read it.