Skip to content
Finitizer

Data Transfer Time Calculator

See how many days your data takes to transfer, and the bandwidth you need to hit your deadline.

Multi-cloudCalculator60 seconds
New here? See what this tool does and how to use it.

Learn more

Data Transfer Time Calculator

What this free tool does for you

Find out whether your migration fits its deadline before you commit to a date. See how long the transfer really takes, and the bandwidth the deadline needs.

How to use it

  1. Pick a scenario under Start from a scenario, or enter your own Data to move.
  2. Set the Link speed, the Usable share of the link and the Hours a day for migration.
  3. Add the Days until the deadline, or 0 if there is none.
  4. Read the Expected transfer time and whether it fits, then the Link speed for the deadline.
  5. Use Continue your migration plan to count the real volume or compare ways to move it.

Good to know

  • Measure a pilot. Copy a few terabytes first, then set Protocol efficiency to the rate you saw.
  • Lots of small files? Enter the Average file size. Files under 1 MB can halve the rate.
  • Save or share. Use Copy link to this result, under the answer, to get a link with your numbers filled in.
Start from a scenario

Each one fills in the fields below for a typical workload of that kind. You can change any of them.

Optional

Expected transfer time86 days
Deadline
At risk, 26 days late
Link speed for the deadline
1.4 Gbps
Moves a day
5.2 TB

450 TB at an effective 644 Mbps.

Expected transfer time
86 days
About 12 weeks. 450 TB to send.
Line-rate floor
42 days
The whole link, 24 hours a day, nothing lost. No transfer gets here.
AWS formula
79 days
Your usable share and hours, as in the AWS DataSync guide.
Expected
86 days
Also takes off protocol overhead.
Link speed for the deadline
1.4 Gbps
To finish in 60 days at the same share and hours.

What this means

  • Deadline at risk

    At 1 Gbps and 18 hours a day this takes about 86 days; your deadline is 60 days away. Meeting it needs about 1.4 Gbps at the same usable share and hours.

  • Offline transfer candidate

    450 TB is large for this link. A transfer appliance or terminal usually reaches the cloud in two to five weeks whatever the link speed. Compare both in the transfer cost comparator.

  • The daily window is a lever

    Running the copy 24 hours a day instead of 18 would finish in about 65 days, 22 days sooner.

What this model assumes

Show
  • The formula is AWS’s. Days = data in bits / (link bits a second x usable share x 3,600 x hours a day). AWS calls it a theoretical minimum; 100 TB on 1 Gbps at 80% all day is 11.57 days.
  • Decimal units. 1 TB is 1012 bytes and 1 Gbps is 109 bits a second, as storage arrays and carriers count them.
  • Protocol efficiency defaults to 92%. TCP, IP and TLS framing and the transfer tool’s own protocol take the rest. Measure a pilot copy and set the figure you see.
  • Small files are a band, not a curve. Average files of 8 to 64 MB run at 90% of the rate, 1 to 8 MB at 75%, 128 KB to 1 MB at 50% and smaller at 30%. These are rules of thumb; a pilot is the real measure.
  • Not counted: source storage that cannot read as fast as the link, outages, and pauses between waves. Leave room for them in the deadline.

Planning the target architecture?

Cloud Cost Audit: We review placement, network design and egress before the first bill arrives, so the migration does not carry avoidable transfer costs into the cloud. From $1,500, fixed. Nothing paid upfront.

See the service

Questions

How do you calculate data transfer time?

Divide the data in bits by the bits a second you can actually use. AWS publishes it as: days = bytes x 8 / (link bits a second x usable share x 3,600 x hours a day). Then allow for protocol overhead, small files and storage that cannot read as fast as the link.

What bandwidth do I need to migrate by a deadline?

Enter the deadline and the page works backwards: the link speed that moves your data in that many days at the same usable share, hours and losses. If it is more than twice what you have, an offline transfer is usually worth pricing.

When should I ship data on an appliance instead?

When the online copy takes more than about a month, or the deadline needs more than double your link. An appliance or the AWS Data Transfer Terminal usually lands data in two to five weeks whatever the link speed. The transfer cost comparator prices both.

Why do small files make a transfer slower?

Every file costs a round trip to open, write metadata and confirm, on top of its bytes. Millions of files under 1 MB can halve the effective rate or worse, and in object storage each file is also a billed request.

Related tools

More tools for: Network and data transfer

The transfer ends. The network bill does not.

Once the data is in the cloud, Finitizer puts every data transfer line next to the workload causing it, across accounts and projects, so placement mistakes show up in the first month.

See how Finitizer works

Rate this tool

How would you rate the Data Transfer Time Calculator?