Enterprise Storage Migration: How to Plan It, What It Costs and the Risks
Storage is on the move again. Whether you are weighing a Dell to Pure migration, looking at NetApp or VAST, or simply facing an array at end of life, the questions are the same: which platform genuinely fits, and how do you move the data without a painful surprise. Here is how to think about both, from a team that has lived on every side of the enterprise storage market.
A lot of enterprise storage is being reconsidered right now. Arrays bought five or six years ago are reaching end of life and end of support, maintenance and capacity costs are climbing, and a wave of newer platforms has given buyers real alternatives to their incumbent. Add the broader infrastructure rethink prompted by VMware and licensing upheaval, and many organisations find themselves asking a question they had not expected to revisit: is our storage still the right storage, and if not, how hard is it to move.
C4C is a UK technology consultancy that helps enterprises choose, buy and move to new storage. We work with several storage vendors, including Dell Technologies, NetApp, HPE and VAST Data, are tied to none, and recommend the platform that fits your workloads. We plan migrations from the workload outward: what moves, in what order and with how much downtime. We spent years on the vendor side architecting and selling these platforms. Tell us about your migration and we will give you a straight view.
An enterprise storage migration has two parts: choosing the target array on merit, and moving the data safely. A safe move follows five steps: discover what you have, design the target and the method, migrate with integrity checks, validate performance, and cut over with a rehearsed, reversible plan. Done this way most workloads move with minimal or no downtime. Phase it by workload, start with the least critical, and budget for the migration itself as well as the new array.
Why are so many organisations migrating storage now?
Several pressures have arrived at once. Arrays from the last refresh cycle are ageing out, and renewing support on an old platform is rarely the best use of budget. All flash has matured and prices have fallen, so the performance case for moving is easier to make. New entrants and challengers have changed the competitive picture, giving incumbents like Dell, NetApp and HPE genuine pressure from the likes of Pure Storage and VAST Data. And the same cost scrutiny driving the VMware and cloud conversations is being applied to storage. The result is that more organisations are willing to consider a change of platform than at any time in years, and the search traffic for paths like Dell to Pure reflects exactly that.
Which storage migration paths are most common?
The most searched paths tend to be moves away from an incumbent, Dell to Pure being a common one, but the truth is that the source and target hardly change the discipline. Whether you are moving Dell to Pure, NetApp to VAST, HPE to Pure, or consolidating several platforms into one, the migration principles are the same, and the right target depends entirely on your workloads rather than on a brand preference. We work across all the major platforms, Dell, Pure Storage, NetApp, VAST Data and HPE among them, which matters for one specific reason: an advisor tied to a single array vendor will always find a reason their array is the answer. An independent one starts from your requirements.
In practice the moves we see most often are from the established arrays to newer all flash platforms. On the source side that usually means Dell Unity, PowerStore, PowerMax or the older VNX, NetApp FAS and AFF, or HPE Alletra, Primera and 3PAR. On the target side it is most often Pure FlashArray or VAST Data, though the right destination is whatever the assessment points to. Each of these has its own quirks in how data is laid out and replicated, and knowing those quirks in advance is a large part of what keeps a migration uneventful.
How do you choose the target array?
The platform decision should be made on merit, matched to the workload rather than the budget line or the existing relationship. The factors that actually matter are performance and latency against what your applications need, capacity and realistic growth, the data services you genuinely use rather than the full feature sheet, and total cost over the life of the asset, including support, power, cooling and the commercial model. That last point is where many decisions go wrong, because a lower headline price can hide a higher cost over five years once support and expansion are counted. Comparing Dell, Pure, NetApp, VAST and HPE on a single consistent basis is the only way to see past the marketing and the discounting to what each will really cost and deliver for you.
Storage is where C4C's roots run deepest. Nick and Paul spent years at EMC and Dell at the sharp end of the high end storage market, on both the technical and the commercial side. We know these arrays from the inside, how they are architected, how they are sold, where the real costs sit and where the quotes have give. That is an unusual combination to have sitting on your side of the table rather than the vendor's.
How do you migrate storage safely, with minimal downtime?
A storage migration goes wrong in the planning, almost never in the technology. Done with discipline it is a routine, low drama exercise. The shape of a good migration is consistent whatever the platforms involved:
- Discover. Understand exactly what data and workloads exist, how they perform, and what depends on what. Surprises here are the main source of downtime later.
- Design. Lay out the target array properly, map the data, and choose the migration method that fits, whether host based mirroring, array based replication or online data movement.
- Migrate. Move the data with integrity checks throughout, so you can prove nothing was lost or corrupted in transit.
- Validate. Confirm performance on the new platform matches or beats the old one before anything depends on it, rather than discovering a regression in production.
- Cut over. Switch with a rehearsed, reversible plan, achieving minimal or zero downtime for most workloads.
None of this is exotic. It is simply disciplined, and the difference between a smooth migration and a painful one is almost entirely the rigour applied before the data starts moving.
How do you phase a large migration, and what does it cost?
Large estates move in waves, not in one weekend. Group workloads by criticality and dependency, move the least critical first to prove the method and the performance on the new platform, and save the systems the business cannot be without for later waves, when the process is rehearsed. File estates follow the same logic: a large scale out NAS, such as Dell PowerScale, formerly Isilon, is usually moved share by share, with a final short synchronisation before each cutover, rather than as one bulk copy.
Timeline and cost are driven by the same handful of things: how much data, how many hosts and applications depend on it, how much change the business can tolerate in each window, the migration method and tooling, and how much of the work your own team will do. The new array is only part of the bill. Budget for migration services and tooling, running old and new platforms side by side during the move, testing, and any support extension on the old array if the timetable slips. Our guide to storage migration cost breaks the numbers down, and we can model it for your estate.
How does C4C help with a storage migration?
We help at both ends of the problem. On selection, we assess your workloads and compare the platforms, Dell, Pure, NetApp, VAST, HPE and others, on a consistent, independent basis, so the array you choose is the one that genuinely fits rather than the one you were steered towards. On migration, we plan and support the move with the disciplines above, and where you need it delivered rather than advised, we can do that too. The whole approach reflects our IDEAL framework: understand first, decide on evidence, then execute properly. And because we are tied to no single vendor, the recommendation follows your workloads, not a preferred array.
Facing a storage refresh or migration?
A C4C storage assessment compares the platforms on a consistent basis, recommends the right fit for your workloads, and plans a safe migration with minimal downtime. Dell, Pure, NetApp, VAST, HPE and more, assessed independently. Decades of high end storage experience, now on your side.
Prefer email? Reach us directly at hello@c4cgroup.co.uk.
Frequently asked questions
How do you migrate from Dell to Pure storage?
A Dell to Pure migration follows the same disciplined process as any array move: discover the data and workloads, plan the target layout and method, move the data with integrity checks, validate performance, and cut over with minimal or no downtime using host based or array based replication. The principles are identical whatever the source and target.
Do you migrate Dell Unity, PowerStore or PowerMax to Pure FlashArray?
Yes. Moves from Dell Unity, PowerStore, PowerMax and the older VNX to Pure FlashArray are among the most common paths we see, and the disciplines are the same as any other migration. We assess the source array, plan the FlashArray target, and migrate with integrity checks and a rehearsed cutover for minimal downtime. We also migrate NetApp FAS and AFF, and HPE Alletra, Primera and 3PAR, to and from other platforms.
Can you migrate between any storage arrays?
Yes. We work across Dell, Pure Storage, NetApp, VAST Data, HPE and others. Whether you are moving Dell to Pure, NetApp to VAST, or any other combination, the migration disciplines are the same, and an independent partner is not tied to any single destination.
Is there downtime during a storage migration?
It can be minimal or zero when planned properly. Modern methods including host based mirroring, array based replication and online data movement let most workloads migrate with little or no disruption. Downtime risk comes from poor planning and untested cutover, not from migration itself.
How do I choose the right storage array?
Match the array to the workload, not the brand to the budget. Assess performance, capacity and growth, the data services you actually use, and total cost over the asset life including support and power. An independent assessment compares Dell, Pure, NetApp, VAST and HPE on a consistent basis.
What are the risks of a storage migration?
Mainly data integrity, unexpected performance changes, extended downtime and underestimated effort. All are manageable with proper discovery, a tested plan, integrity validation and a rehearsed cutover. The risk is almost always in the planning, not the technology.
How long does an enterprise storage migration take?
It depends on the volume of data, the number of applications that depend on it and how much change the business can take at once. Small moves can be done in weeks. Large estates are usually phased over several months in waves, starting with the least critical workloads, so each cutover is rehearsed and reversible.
What does a storage migration cost?
The new array is only part of it. Budget for migration services and tooling, running old and new platforms side by side during the move, testing, and possibly extended support on the old array if the timetable slips. The cost is driven by data volume, application dependencies, the migration method and how much of the work your own team does.
Can you migrate NetApp or HPE storage to another platform?
Yes. We migrate NetApp FAS and AFF, and HPE Alletra, Primera and 3PAR, to and from other platforms including Pure FlashArray, VAST Data and Dell. We are tied to no single vendor, so the recommended target is whichever genuinely fits your workloads.