GoldenrozBook a call

Mailbox migration time calculator

Enter how many mailboxes you are moving, their average size and the transfer rate you measured in a pilot. The calculator estimates the hours and days of data transfer and how many mailboxes to schedule per day.

The starting values are examples, not benchmarks. Replace them with your own figures. Nothing you enter is stored or sent anywhere.

  • Total mailbox data
    Mailboxes times average size
  • Transfer time at measured rate
    Total data divided by throughput
  • Transfer time with allowance
    Adds the share for retries and throttling
  • Migration days
    Padded hours divided by hours per day, rounded up
  • Mailboxes per day
    Mailboxes divided by migration days

How to read the result

Throughput is the input you cannot look up. It depends on the source server, the network between source and target, the migration method and the throttling the target service applies. Migrate a pilot batch of ten to twenty real mailboxes, divide the data moved by the hours it took, and enter that figure.

Mailbox size is only part of the load. Item count matters as much: a mailbox with hundreds of thousands of small messages moves more slowly than its size suggests. A few very large mailboxes also set the minimum length of the project, because one mailbox cannot be split across streams. Start those first.

Data transfer is one phase of a migration, and usually not the one that goes wrong. Identity, DNS, shared mailboxes, permissions, devices and user communication take longer to plan than the copy takes to run. The full sequence is in the Office 365 migration checklist, and the service is described under Microsoft 365 migration.

Questions about migration time

How long does an email migration take?

The copy takes total mailbox data divided by the transfer rate you can sustain. 300 mailboxes of 8 GB is 2.4 TB. At 20 GB an hour that is 120 hours of transfer, or about 15 working days at 10 hours a day with an allowance for retries. Planning and cutover are extra.

How do I measure migration throughput?

Run a pilot batch with real mailboxes during the hours you plan to migrate. Note the total data moved and the elapsed time, and divide. Repeat with more concurrent mailboxes to see where the rate stops rising, which shows the limit of the source server or the network.

Can I migrate faster by running more mailboxes at once?

Up to a point. More concurrent mailboxes raise total throughput until the source server, the network link or service throttling becomes the limit. Past that point, adding streams only makes each one slower.

Do users lose access to email during the migration?

With a staged or hybrid method they do not. Mailboxes are copied in the background while users keep working, and only the final switch of each mailbox needs a short interruption. A cutover migration moves everyone at once, usually over a weekend.

Related calculators

  • Backup storage needed for a data size, daily change rate, retention policy and compression, with growth over time.
  • Allowed downtime per day, week, month and year for any uptime percentage, and whether a month met its target.
  • What an outage costs per hour, per incident and per year in lost productivity, lost revenue and recovery.

All free calculators

Talk to the person who will do the work

One hour, no sales team. You talk to Shai Goldenberg, the CTO, about your systems or your product, and you leave with a clear next step and a price range.

Or send the details

Book a callWhatsApp us