Open-source model
Open source: you pay for support when you need it, no per-VM or per-core fee. Scales well as volume grows.
OpenStack · KVM · VMware · Hyper-V · since 2008
OpenStack migration from VMware or Hyper-V.
Since 2008 we have been deploying private and hybrid clouds with OpenStack. On your hardware or ours, with your team, always starting with a 6-week proof of concept.
2008Our first OpenStack cloud
6 wksProof of concept in your environment
24×7Direct engineer · no ticket escalation
[ 01 ]What OpenStack brings to your infrastructure
Four reasons to consider OpenStack
Runs on what you already own
Deploys on x86, ARM (including AWS Graviton) and Power. No need to refresh the data centre to migrate.
Open standards
If tomorrow you want to move workloads to another OpenStack platform or to Kubernetes, you can: formats are open and well documented.
Private, hybrid or public
A single pane of glass for your data centre, your private cloud and the public provider you prefer. Coexists with hyperscalers when it makes sense.
[ 02 ]Technical comparison 2026
OpenStack, VMware and Hyper-V side by side
Technical criteria that appear in every enterprise virtualisation RFP. Each platform fits a different type of case; below we describe where each one typically fits best.
| Criterion | OpenStack | VMware vSphere | Microsoft Hyper-V |
|---|---|---|---|
| Licensing model | Open source. Paid support, no per-VM fee. | Per-core subscription (current model). | Bundled with Windows Server / subscription. |
| Portability | Open standards, portable to Kubernetes. | Proprietary formats and APIs. | Strong integration with the Microsoft ecosystem. |
| Hypervisor | KVM by default (also LXC, VMware). Linux and Windows VMs in the same cluster. | Own ESXi. | Own Hyper-V. |
| Architectures | x86, ARM (Graviton), IBM Power — mixed. | x86 (ARM in beta since 2024). | x86 and ARM64 (with caveats). |
| Native multi-tenant | Designed for IaaS from day 1. | Needs vCloud Director or others. | Extended via System Center. |
| VM migration | V2V via QEMU/virt-v2v. VMDK/VHDX → QCOW2. | vMotion / HCX within its own ecosystem. | Live Migration within its ecosystem. |
| Fits well in | Private cloud, internal IaaS, edge, HPC, telco. | Organisations with an established VMware investment and team. | Environments with strong Active Directory / Windows Server dependency. |
Common criteria drawn from enterprise virtualisation RFPs · VMware® and Hyper-V® are trademarks of their respective owners.
Our story
We built our first OpenStack cloud in 2008, when almost nobody knew what it was. We have watched frameworks, hyperscalers and trends come and go. When someone asks whether their current platform will still fit in two or five years, we give the answer engineers give — not a sales script — and lay out the options that fit their case.
[ 03 ]How we migrate
From VMware or Hyper-V to OpenStack, step by step
No big-bang. We start with a 6-week PoC, and only once OpenStack is running in your environment do we discuss the next milestone.
-
0
Proof of concept (PoC)
Try it first, then we talk. In under 6 weeks we build a full PoC in your environment or in our cloud. It ends with real data to define the MVP.
6 weeks -
1
Analysis of your current VMware/Hyper-V and MVP design
We audit your VM inventory, dependencies, storage and network. We design an OpenStack architecture tailored to you, ready to coexist with your existing VMware during the transition.
-
2
Installation of the OpenStack infrastructure
We deploy using our validated reference architectures — no experiments. Licences, security and performance optimised for your case.
-
3
Virtual machine migration
Gradual and controlled migration, no big-bang. VMDK/VHDX to QCOW2 conversion, thorough testing by batch and agreed maintenance windows. We minimise downtime; we don't promise zero when it's not true.
-
4
Training and knowledge transfer
Your team learns to operate OpenStack — administration, day-to-day, best practice. Full documentation included. We don't want you to depend on us, we want you to depend less on everyone.
-
5
L3 support and preventive maintenance
Proactive monitoring, updates, L3 support with in-house engineers. We anticipate; we don't wait for the ticket.
[ 04 ]Tailored support
What the support contract includes, no small print
01
Direct engineer 24×7 by phone for major incidents. No ticket escalation around the globe.
02
Reduced-rate technical training for your team on IBM, Lenovo, SUSE and Red Hat — at partner internal pricing.
03
Multinational: we deliver in English, Spanish and French. Europe, Africa and the Americas.
04
Alternative to SWMA for 95% of IBM, Red Hat and HCL software with 50% discount and added services.
05
Integration with SIEM tools (QRadar, Wazuh) that we also deploy and configure if needed.
06
In-house engineers, no subcontracting. The person who installs is the one who answers in production.
[ 05 ]Video explainer
Why OpenStack, in 5 minutes
[ 06 ]FAQ
Common questions about migrating to OpenStack
Can you migrate from VMware to OpenStack with no downtime?
Absolute zero downtime? Honestly, no. Yes with very short, planned downtime by batch: we convert VMDK to QCOW2 with virt-v2v, replicate the data, boot on OpenStack and validate before cutting over traffic. For critical workloads we use agreed maintenance windows with rollback prepared.
Does OpenStack fully replace VMware?
For server, network and storage virtualisation: yes. For very specific functions (some vSAN integrations, certain NSX plug-ins or vCenter dependencies inside third-party tooling) it needs case-by-case review. In the 6-week PoC we identify exactly what stays out before signing anything.
What hypervisor does OpenStack use?
KVM by default — the Linux kernel hypervisor, mature and with support for Linux and Windows VMs in the same cluster. OpenStack also supports other drivers (LXC, Ironic for bare-metal, even VMware ESXi for temporary coexistence), but KVM is the standard choice.
And from Hyper-V?
Equally viable. VHDX to QCOW2 conversion with qemu-img, virtio driver tweaks and network adaptation. In mixed Hyper-V + VMware environments we plan the most critical first and then the satellite systems.
How much does it cost to migrate from VMware to OpenStack?
Depends on VM inventory, storage and cut-over windows. The 6-week PoC is a fixed-price engagement that sizes the real project and lets you decide with no commitment. Tell us your case and we return an indicative range within 24 working hours.
Can we offer OpenStack as IaaS to our own customers (white-label)?
Yes. OpenStack is designed for multi-tenant from day 1: users, quotas, isolated networks, billing. It's the foundation of many European regional IaaS providers. We design the architecture, integrate billing and provide L3 support in the background.
Does it work for HPC and AI?
Yes, combined with Ceph for scalable storage and GPU passthrough in KVM. It's the architecture we recommend for on-premise AI inference and HPC — more detail here.
And if later we want to migrate away from OpenStack?
You can. That's the advantage of open standards: QCOW2 images and network formats move to any OpenStack-compatible platform or to Kubernetes with KubeVirt. You won't repeat the lock-in problem.
[ 07 ]We start with a PoC
Tell us about your VMware or Hyper-V estate
Reach us through whichever channel works best. PoC proposal in under 24 working hours with scope, milestone and fixed price.
Blog!
Our mission
SIXE ensures that your infrastructures based on IBM®, Red Hat®, Canonical®, and SUSE® technologies remain stable, secure, and optimized for as long as you need them.
At SIXE, we are committed to sustainability. That’s why we help you design, implement, and maintain durable and efficient technological solutions.
