Free estimator

How much will your storage migration cost, and how long will it take?

Enter the estate and the change windows the business will give you. The estimator returns the five lines of a fully loaded migration and the elapsed months, using our own planning assumptions, which you can see and change. No vendor pricing. Nothing leaves your browser unless you send it to us.

Updated 17 November 2026

Who we are

C4C is an official Dell Technologies, NetApp, HPE and VAST Data partner, tied to none. Nick Watson and Paul Smith each spent over a decade at EMC selling and scoping enterprise array migrations, so the assumptions here are the ones we used to build the quotes.

Your migration

Your own numbers only. The target platform price is optional and comes from your quote.

Each one needs its own cutover and test.
How often the business lets you cut over.
Our planning assumptions (change them if yours differ)
A UK senior storage migration engineer or architect, blended.
Discovery, remediation, cutover and test, averaged. Varies by method.
Data movement and validation effort that scales with volume.
Assessment, dependency mapping, runbooks, rehearsal.
Licences for migration software where the method needs it. Zero for array replication.
Added to the elapsed time for the support extension line.

Email me this estimate

Get a formatted PDF of these results by email, to keep or share with your team. We send it once and do not add you to any list.

Want the real figure, not the estimate?

Tell us the estate, the applications on it, your change windows and the platforms you are moving between. We will come back with a written plan: method, waves, specialist days, elapsed time, and whether the business case holds against a renegotiated stay. Free, written, and no obligation.

Prefer email? Write to us at hello@c4cgroup.co.uk.

How the estimator works

It follows the five lines of a fully loaded migration from our storage migration cost guide. Professional services is the planning days plus days per application plus days per 100TB, each scaled by the method, at the day rate, with the share you do yourselves taken off. Tooling is a per 100TB licence where the method needs one. Dual running is the incumbent support cost for the elapsed months, if you enter it. Support extension is the same monthly figure for the slip allowance, because timetables slip and the old array has to be supported until the last application moves. Target platform is your quote, added if you enter it. Elapsed time is the applications divided by what the windows can take, plus the planning period, and it is the number most quotes get wrong, because copy speed is never the constraint. The business is.

What it does not include

Frequently asked questions

How much does it cost to migrate 500TB of enterprise storage?

The capacity alone does not set the price. Two 500TB estates can differ by a large multiple depending on how many applications sit on the data, how tightly disaster recovery is coupled, how much can be moved in each change window, and how long the old platform runs alongside the new one. As a planning figure, a 500TB block estate with around 40 dependent applications, moved host by host at one window a week, typically needs 60 to 90 days of specialist time and four to six months of elapsed time, before the price of the new array. The estimator works it through on your own numbers.

How long does a storage migration take?

Elapsed time is set by change tolerance, not by copy speed. Data can be copied in days; applications can only be cut over in the windows the business allows. A migration with 40 applications and one maintenance window a week takes at least 40 weeks if each window moves one application, and far less if windows can take several or if the data moves underneath the host with a short final synchronisation. The estimator uses your window frequency and applications per window to work out the elapsed months.

What does the estimator include?

The five lines of a fully loaded migration from our cost guide: professional services and data movement, migration tooling, running old and new side by side, the incumbent support extension if the timetable slips, and the target platform if you enter a quote. It uses our own planning assumptions, which you can change in the advanced panel, and no vendor pricing.

Why does the estimator not price the new array?

Because storage pricing is quote specific: it depends on the platform, capacity, data services, term and the discount agreed, and the list price is a starting point rather than the number anyone pays. Enter the quote you have and the estimator adds it to the total. If you do not have one, the other four lines are the ones most organisations underestimate anyway.

Which migration method is cheapest?

Array based replication between compatible platforms is usually the least effort per terabyte but ties you to the vendor pair. Host based migration, using the operating system or hypervisor to move volumes underneath running applications, is the most common and the most flexible. Backup and restore is simplest for cold data and archives. File estates move share by share with a final synchronisation. The method changes the specialist days and the elapsed time, which is why it is an input here.

Is this a quote?

No. It is a planning estimate from your figures and our assumptions, built to show which lines dominate and whether the business case holds. For a real figure we assess the dependencies, the windows and the method on your estate and give you a written plan. That is free and without obligation.

Does C4C deliver migrations or only advise?

Both. We are partners of Dell Technologies, NetApp, HPE and VAST Data and tied to none of them. We assess, we plan, and where you want it delivered rather than advised we run the migration with the vendor’s professional services where that fits. We tell you up front when staying on the incumbent is the cheaper answer.