Our process
How we work.
A 6-step process built to minimise risks and maximise your autonomy after migration.
Technical audit
Understand before recommending
Complete inventory of the existing VMware environment: VMs, networks, storage, inter-service dependencies, backup tools, existing DRP. Identification of hardware, licensing and internal skills constraints. Deliverable: audit report with recommendations and risk matrix.
Target architecture
Design the Proxmox infrastructure suited to your context
Definition of the Proxmox VE architecture: HA clustering, storage strategy (NFS, Ceph, iSCSI), network segmentation, PBS backup policy. Resource sizing. HLD and LLD documentation delivered before work begins.
POC or test environment
Validate the architecture before production
Setting up a representative Proxmox environment on your hardware or on VSHIFT Cloud. Migration of a representative subset of VMs. Cutover, rollback and performance tests. Configuration adjustments before going to production.
Wave migration
Migrate progressively, keeping VMware on standby
VM migration in ordered groups by criticality: non-critical first, production systems last. At each wave: functional validation, load tests, business team sign-off. The VMware environment remains operational in parallel until final validation.
Knowledge transfer
Make your teams autonomous
Training sessions on Proxmox VE, PBS and associated tools. Writing operational runbooks: escalation procedures, alert management, node updates, backup restoration. The goal is for your teams to operate the infrastructure autonomously without dependency on VSHIFT.
Post-delivery support
Ensure stability after cutover
4 to 8 week stabilisation period post-migration: proactive monitoring, resolution of migration-related incidents, configuration optimisations. Optionally: managed Proxmox Enterprise subscription, architect access on tickets, recurring support.
What we guarantee
Everything is documented
Architecture, runbooks, technical decisions: every deliverable is written and belongs to you.
No dependency created
Our engagements target your autonomy. You should not need us to operate your infrastructure.
Rollback at every step
The VMware environment remains operational until final validation by your teams.
Ready to get started?
Discuss your project →