Applications and dependencies
We assess systems, interfaces and vendor support. Backup, networking, permissions and exceptions such as encrypted VMs are part of the assessment.
PROXMOX IN ENTERPRISE ENVIRONMENTS From VMware
From VMware
to Proxmox.
A plan that works with your renewal deadline.
We plan and deliver your VMware exit. With your IT team, we establish what can be migrated before the next renewal, what it will cost and which applications and connected systems need adapting. Existing hardware is part of the target architecture.
EXPERIENCE WITH LARGE ENVIRONMENTSWell over 1,000 VMsWe have supported infrastructure projects at this scale.
COSTS AND TIMELINEWhat is achievable
What is achievable
before the contract ends?
An expensive renewal offer creates pressure. We first check deadlines, dependencies and available capacity. You learn whether a complete migration is realistic or a temporary arrangement is needed.
Target architecture and operations
We size clusters, storage and networking. Availability, recovery, monitoring and operational ownership help determine the design.
Costs and contract terms
We compare continuing operations with migration, including hardware, subscriptions, implementation and connected systems. Notice periods, remaining contract terms and parallel running shape the timeline.
THE OUTCOME
A target architecture, cost assessment and deliverable migration plan with explicit prerequisites. This allows IT and management to decide on the next step.
Initial assessment checklist
- Contract end date, notice period and renewal offer
- Host and VM counts, storage design and available capacity
- Critical applications, vendor support and connected systems
- Backup, recovery objectives and acceptable interruptions
- Availability of your IT team and participating providers
This information helps define the assessment scope. A reliable effort estimate follows the technical analysis.
USE EXISTING INVESTMENTSReplace VMware.
Replace VMware.
Not necessarily the hardware.
We also deliver migrations on suitable existing hardware. We assess technical and commercial suitability based on specifications, remaining service life, support and capacity during migration.
Reuse servers from a vSAN cluster.
After assessment, the servers may be suitable for the new platform. vSAN itself is not retained. We assess hardware and capacity and plan a new storage design, including data transfer.
Integrate existing SAN systems.
A suitable SAN can continue serving the new platform. Connectivity, storage methods and backup are checked for the specific combination. VMware datastores are not retained unchanged.
NO ASSUMPTION OF A COMPLETE SECOND ESTATE
We compare conversion of existing infrastructure with temporary capacity and a parallel new build. Total cost, possible interruptions and a realistic deadline determine the choice.
Hardware reuse and migration optionsAPPLICATIONS AND CONNECTED SYSTEMSWhat depends
What depends
on VMware today?
The hypervisor is only part of the change. We establish required vendor approvals and adaptations early, coordinating the work with your application and operational partners.
Clarify support and exceptions.
We check support requirements, virtual appliances, guest operating systems and licence dependencies. Systems without confirmed support need agreed testing or a separate transition path.
Resolve dependencies before migration.
We assess VLANs, routing, firewalls and, where relevant, vDS or NSX. EVPN, BGP and site connectivity are planned to fit the target environment.
Adapt backup and tools.
We check product versions, licences and recovery procedures. Monitoring, provisioning and scripts integrated with vCenter are adapted or replaced. New procedures are tested before handover.
INFORMATION SECURITY & COMPLIANCETranslate requirements
Translate requirements
into implementation.
Especially in regulated environments, it must be clear which requirements the new platform meets. We coordinate technical measures with your IT team, information security and relevant assurance teams.
What must be met?
Record protection needs, access rules, recovery objectives and internal requirements. Define owners and acceptance criteria.
How will it be achieved?
Design and implement permissions, network separation, logging and backup in the target environment.
How will we demonstrate it?
Run tests, document results and present open issues for decision. This creates usable operational documentation.
Sysfacts is responsible for the agreed technical implementation and documentation. Business approvals and assessment of regulatory obligations remain with the responsible parties.
IMPLEMENTATIONTurn the plan
Turn the plan
into a running platform.
Your applications determine the sequence. We prepare the target environment and agree tests, maintenance windows and approvals with the responsible teams.
- 01
Build the target environment
Configure clusters, networking and storage. Integrate backup and monitoring. Document configurations and access.
- 02
Run a pilot and tests
Transfer representative systems, check applications with their owners and test recovery.
- 03
Migrate in agreed waves
Group systems by dependency. During the cutover window, we focus on the systems being transferred.
- 04
Accept and support
Review results together, hand over documentation and monitor operations during the agreed hypercare period.
PROJECT EXPERIENCE · WISMAR UNIVERSITYOne central
One central
data centre.
Around 500 virtual machines on ten nodes across two fire compartments. We consolidated requirements, supported implementation and helped the data centre team with failure testing and acceptance.
The case shows our work on a Proxmox target architecture with separate environments for three faculties.
See the project and our contribution- Virtual machines
- ~500
- Nodes
- 10
- Fire compartments
- 2
BEFORE YOU STARTWhat clients
What clients
want to know.
A useful migration plan also identifies limitations. We clarify these questions before you commission implementation.
Do all systems have to move at once?
No. We plan migration waves based on dependencies. Temporary parallel operation may be useful. Licence costs, interfaces and eventual decommissioning belong in the plan.
What if some applications cannot move yet?
We identify those systems and assess a transition path with their vendors. A temporary remaining VMware environment may be necessary. Its licence costs, duration and later replacement are explicitly planned.
How much downtime should we expect?
That depends on the applications and transfer method. We test representative systems and use the results to define the windows. A blanket promise without assessment would not be reliable.
Can we commission only the assessment first?
Yes. Assessment and implementation can be commissioned separately. We define the scope in advance. You can use the documented results without a follow-on engagement.
PRODUCT AND VENDOR SUPPORT
Visit the Proxmox VE product page Proxmox VE and subscription tiers.
The product page explains features and vendor services. Sysfacts planning, migration and operational support are agreed separately.
YOUR PROJECTWhen does your
When does your
VMware contract end?
Tell us the contract end date, approximate scale and existing hardware. We discuss the main dependencies and establish how to approach assessment and implementation.
Arrange an initial conversation Our full range of services