Migrating from Dell PowerEdge R720 to R750 — Step-by-Step Guide
The R720 is a 12G platform. Released March 2012. Dell publishes no fixed end-of-support date for it; ProSupport ends per service tag. In 2026 there is no reasonable case to stay on an R720 without third-party maintenance — the hardware is solid, but every DIMM, every PSU, every drive is either end-of-life or in the thin tail of the spare-parts market. This guide covers the R720 → R750 migration (three generation jumps), which is the path most teams take when they skip the intermediate R730/R740 generations entirely.
Why this migration, why now
R720 workloads are typically: Windows Server 2012 R2 / 2016 hosts, early VMware clusters, Oracle 11g/12c databases, Active Directory infrastructure, or legacy file/print servers. All of these workloads will run on R750 with zero architectural change — the migration is fundamentally a hardware refresh, not an application overhaul.
The trigger to move now: the R720 is a 2012 platform. Third-party maintenance (ICD Care+ equivalent) extends coverage but parts availability for certain R720-era components (specific DDR3 densities, PERC H710 controllers) is genuinely thinning. Every year the risk of a 48-hour-outage-for-lack-of-a-spare-part rises.
Compatibility analysis: what’s reusable
| Component | R720 | R750 | Reusable? |
|---|---|---|---|
| CPU | Xeon E5-2600 v1/v2 (Sandy/Ivy Bridge) | Xeon Scalable Gen 3 (Ice Lake) | No — different socket |
| Memory | DDR3 ECC RDIMM | DDR4 RDIMM | No — different standard |
| Drive caddies | 12G generation | 15G generation | No — different latch |
| Bare drives (2.5″ SAS) | 6Gb/12Gb SAS | 12Gb SAS, NVMe | Yes, with new caddies |
| PSU | 495W/750W/1100W (12G) | 800W/1100W/1400W/1800W (15G) | No — connector changed |
| RAID (PERC) | H710 / H710P / H810 | H345 / H755 / HBA355i | No — different firmware generation |
| Chassis fans, rails, bezels | 12G | 15G | No — chassis-specific |
| iDRAC Enterprise license | iDRAC7 | iDRAC9 15G | No — new license required |
The honest answer: R720 → R750 is essentially a full rebuild. Bare drives migrate with new caddies; nothing else does. This is why Dell shipped the R730 and R740 as intermediate generations — each step was smaller. The three-generation jump is viable but expensive.
Data migration path
Three approaches, in order of preference:
Option 1: Virtualisation lift-and-shift
If the R720 runs VMware ESXi, Hyper-V, or KVM, use vMotion / Live Migration to move VMs to a staged R750 cluster. Zero downtime for the workload. Requires at least one R750 online first.
Option 2: Backup and restore
Full system backup on R720 (Veeam, Rubrik, Commvault, native Windows Server Backup). Restore onto R750. Downtime equal to backup + restore time, typically 2–8 hours depending on data volume. Works for physical workloads.
Option 3: Disk migration (where electrically compatible)
2.5″ SAS drives from the R720 will read on the R750 — same SAS electrical spec. Two constraints: (a) drive caddies must be swapped R720-type → R750-type, and (b) RAID controller metadata is written by the controller family, not the drive, so the RAID set will NOT import from PERC H710 to PERC H755. You would need to restore from backup after attaching drives. This path is rarely worth the complexity.
Parts list for the R750 build
A typical R750 replacement for an R720 running a moderate virtualisation workload (8-16 VMs, 200GB–800GB RAM working set):
- R750 chassis (refurb) — on quote
- 2 × Xeon Silver 4314 or Gold 6338 (Gen 3, 16–32 cores each) — on quote (CPU pair, refurb)
- 16 × 32GB DDR4-3200 RDIMM (512GB total) — on quote (refurb). PN examples:
6VDNY,74FPM,75X1V,HF6GX. - PERC H755 (8GB NV cache) — on quote (refurb)
- 8 × 1.92TB SAS SSD or 4 × 3.84TB NVMe — on quote. PN samples:
0184M,01Y7M,03VVP,08M01,0D4GH,0HVC7. - 2 × 1400W Titanium PSU — on quote (refurb pair). PN samples:
0CYHH,1CW9G,2XNWP. - iDRAC9 Enterprise license — on quote
- Rails, bezel, cable arm — on quote
Total typical cost per R750 node: quoted per configuration (refurb).
Budget reality in USD
Get a free infrastructure audit and custom proposal. Our team responds within 24 hours.
The ICD Care+ alternative
If CapEx for full refresh is not reachable this fiscal year — common for Egyptian and Nigerian businesses weathering FX volatility — ICD Care+ third-party maintenance extends the R720 hardware coverage 2–5 additional years. Cost: quoted per node per year. Covers parts and labour, with on-site SLA levels from NBD / 8H to 2H response.
The Care+ path is a bridge, not a destination. Eventually the spare-parts market for 12G hardware tightens to the point where same-day parts cannot be guaranteed. Our recommendation: Care+ for 12–18 months, then execute the R750 refresh on the next budget cycle.
Step-by-step migration plan
- Week 1 — Inventory. Document R720 spec, workload, OS versions, backup position, network dependencies.
- Week 2 — Quote R750 build. Submit RFQ to ICD with workload and target VM count.
- Week 3–4 — Parts arrival + R750 build. ICD builds and ships from Cairo; the lead time is stated on each quote.
- Week 5 — Staging. Rack R750, install hypervisor / OS, network config, storage init.
- Week 5–6 — Workload migration. vMotion or backup/restore windowed during low-traffic hours.
- Week 7 — Validation. Performance baseline, backup verify, production cutover.
- Week 8 — Retire R720. Data-destroy drives (via ICD EKODAQ), trade in chassis, reclaim rack space.
Next steps
Request a quote specifying current R720 spec + target R750 configuration. ICD presales responds within 24 working hours with a full migration plan + parts list + USD budget.
Frequently Asked Questions
Can I reuse the drives from my R720 in a new R750?
Yes, the bare 2.5 inch SAS drives will read on the R750 because the SAS electrical spec is the same, but they need new R750-type caddies. The RAID set will not import from a PERC H710 to a PERC H755, since the controller family writes the metadata, so you restore from backup after attaching the drives.
Will my R720 workloads need application changes to run on an R750?
No. Typical R720 workloads such as Windows Server 2012 R2 or 2016 hosts, early VMware clusters, Oracle 11g/12c databases, Active Directory and legacy file or print systems run on the R750 with zero architectural change. The move is fundamentally a hardware refresh, not an application overhaul.
How many weeks does a typical R720 to R750 project take?
The plan runs about eight weeks: inventory in week 1, quoting in week 2, parts arrival and build in weeks 3 to 4, staging in week 5, workload migration in weeks 5 to 6, validation in week 7 and retiring the R720 in week 8. The build lead time is stated on each quote.
What can we do if a full R750 refresh is not in this year's budget?
ICD Care+ third-party maintenance can extend R720 hardware coverage by 2 to 5 additional years, covering parts and labour with on-site SLA levels from NBD / 8H to 2H response. It is a bridge, not a destination: the recommendation is Care+ for 12 to 18 months, then the R750 refresh on the next budget cycle.
