When OracleCMS contacted us, they had two problems. Their VMware licence was up for renewal at a price that had increased fourfold. And they had a sixty-day window to make a decision.
Sixty days is a tight window for an infrastructure migration. It is much less tight when the migration tooling does the heavy lifting.
The environment. Three clusters, ninety-something VMs, a mix of Linux and Windows guests, a handful of database servers, and the contact-centre application stack that runs the business.
The plan. Move the smallest, least-critical workloads first to build operational confidence with Netframe. Then in a single weekend cutover window, move the production stack.
Week 1–3. Build out the Netframe environment. Install Core on existing hardware, deploy Manager, configure clusters and HA. Train the OracleCMS team. Migrate a small batch of dev and staging VMs using Converter to validate end-to-end.
Week 4. Migrate the long tail of non-critical production VMs, file servers, monitoring infrastructure, internal tooling, using Converter. Validate post-migration.
Cutover weekend. Migrate the contact-centre application stack and the database servers. Total migration time: 14 hours. Service impact: none, because we used Converter's live cutover mode for the application tier and a brief planned maintenance window for the databases.
The result: OracleCMS exited their VMware contract at renewal. Three-year TCO came in at roughly a third of the projected vSphere renewal cost. Their team is now self-sufficient on Netframe and has begun planning a second-site DR build using Backup.
"The Netframe team's support is exceptional, genuinely knowledgeable engineers who understand virtualisation at depth. When we had a critical HA event at 2am, they were on the call within minutes.", Metin Unal, Director, OracleCMS