Question 1

What does Mover charge per GB?

Accepted Answer

Mover pricing starts as low as $0.15 per GB with prepaid usage packs. You only pay for the data you move, with no hidden fees or long-term contracts.Estimate the cost of your migration.

Question 2

Are there any hidden fees with Mover?

Accepted Answer

Mover offers prepaid usage packs so you only pay for what you use. Unlike other tools, there are no license fees, no per-user charges, and no hidden costs.

Question 3

Do I save money if I move more data?

Accepted Answer

Yes. With Mover's prepaid usage packs, the more data you move, the lower your effective cost per gigabyte. Larger packs are priced at a discount, so bulk migrations cost less per GB than smaller ones — without any contracts or commitments.

Question 4

How do prepaid usage packs work?

Accepted Answer

Mover uses a prepaid Usage Pack model, where you purchase a data transfer package upfront in a size and duration that best fits your needs. Once purchased, the pack functions like prepaid credit and your balance decreases only as you transfer data between your connections, and remains valid until the duration expires.

Question 5

How are data transfers calculated?

Accepted Answer

Only data that is actually transferred during a migration counts toward your usage. Files that are skipped based on your settings are not considered usage. Failed transfer attempts due to connectivity issues or permission errors aren't considered usage.Starting a Dry Run for a migration does not count as usage.

Question 6

What happens to unused balance when a pack expires?

Accepted Answer

Usage packs are use-it-or-lose-it once the duration expires. If you have transfer remaining on a pack when its expiration date passes, that balance is forfeited. The durations are sized to give plenty of headroom for typical projects — 14 days for the 100 GB pack, 60 days for the 1 TB pack, 180 days for the 10 TB pack — so most migrations finish well inside the window with room to spare for re-runs and follow-on transfers.

Question 7

What if my migration exceeds the pack size partway through?

Accepted Answer

Purchase another pack. Mover lets you stack packs — you can hold multiple active packs at once and mix and match sizes to fit the migration. Most overages happen because the initial dry run undercounted or because re-running parts of the migration consumed more than expected; in either case a second pack picks up where the first left off without interrupting the transfer.

Question 8

Can I have more than one pack active at the same time?

Accepted Answer

Yes. Multiple active packs are supported and you can mix sizes — for example, a 10 TB pack plus a 100 GB top-up for end-of-migration cleanup. Mover draws from your aggregate remaining balance as data moves, so you don't need to plan migrations to fit precisely inside a single pack.

Question 9

Does Mover re-transfer files that already moved on a previous run?

Accepted Answer

No. Incremental syncswork at the file level — once a file has been migrated successfully, subsequent runs skip it as long as it hasn't changed at the source. Only files that are new or modified since the last successful run get re-sent.Incremental detection is file-level, not block-level: any change inside a file (including a one-byte edit) re-transfers the whole file. For typical migration patterns — moving static archives, cutting over an active workload, or running scheduled deltas during a phased move — file-level incrementality covers the use case without the complexity of block-level diffing.

Question 10

Are re-runs of a migration billed?

Accepted Answer

Bytes that actually move on a re-run count toward your pack, the same as on the first run. Failed transfer attempts from a prior run don't bill, and files that already landed successfully won't re-send on the next run (see the incremental-sync question above). What does count: a file you deliberately delete from the destination and re-run the migration on, or a file that changed at the source between runs.

Question 11

Who pays for provider egress fees (S3 egress, etc.)?

Accepted Answer

You do. Provider egress is a cost the source platform charges on its own invoice (typically AWS for S3, separately from anything Mover charges). For most cloud-to-cloud providers there are no egress fees at all— Dropbox, Google Drive, OneDrive, SharePoint, and Box don't charge for migration egress. For S3 and some S3-compatible providers, egress is a real line item on your provider bill at the standard per-GB rate.The dry run estimates expected egress so you can see the total cost before you commit. The estimate is based on our research into each provider's public pricing; for contractual rates or committed-use discounts on your specific account, your invoice will reflect the actual numbers.

Usage Pack	Price	Per GB	Savings	Use Within
100 GB	$39	39¢	—	14 days
200 GB	$59	30¢	24%	30 days
400 GB	$99	25¢	37%	30 days
1 TB	$199	20¢	49%	60 days
2 TB	$379	19¢	51%	60 days
5 TB	$799	16¢	59%	90 days
10 TB	$1,499	15¢	62%	180 days

Pay only for
what you move.

The full price list.

What we don't bill you for.

Free dry runs, always.

Skipped files don't count.

Failed transfers don't count.

$0.15 per gigabyte.^*

Frequently asked.

Scoping a bigger migration?

Connect, scan, hit Go.

Pay only forwhat you move.