We move SMB infrastructure off VMware onto Proxmox — and then we stay and run it.
Fixed price, fixed scope. Read-only assessments. Night cutovers, one workload at a time, so Monday looks like Friday did. Twenty years of systems engineering behind every migration.
Book a 30-minute call No sales deck. We will ask what you run and tell you what it would take to move it.Three situations we see most often
-
Two to five VMware hosts and a renewal you did not budget for
The Broadcom quote arrived, the hosts are out of warranty, and you want to know what moving actually takes — before you sign anything.
-
A small MSP without a Proxmox bench
Your clients are asking about VMware alternatives and you are not ready to hire for it. We assess and migrate under your name — white-label; the relationship stays yours.
-
A cloud bill for a workload that never changes
Traffic is flat, the invoice is not. We read the billing and usage data and say which workloads belong on dedicated hardware — and which should stay where they are.
Assess, migrate, run
Infrastructure Exit Assessment
$2,900 / €2,300
- Licences and real renewal cost
- Workload needs, measured
- Refreshed hardware priced from the refurbished market
- Migration plan with service windows
Entry: Exit Check — $750, 2 days, read-only, credited in full.
Cloud estates: Cloud Spend Audit — $1,800 / €1,450, 5 days.
Migration at a fixed price
Fixed from the scope
- New cluster built alongside the old
- Night cutovers, one workload at a time
- Backup (local + S3) and monitoring rebuilt
Assessment fee credited if you proceed within 60 days.
Care plan
From €990 / $1,090 a month
- Monitoring with alerts
- Monthly patching, backup checks
- Up to 8 hours of engineering work
- One-page monthly report
Month to month. The hardware stays yours.
Guarantee: no 3× the fee in annualised savings found — fee refunded.
Founding clients: 20% off assessment and migration setup for the first three, in return for a case study with real numbers. Care plan at full price.
You are never locked in
Every environment we run ships with an Exit Kit: everything your team needs to bring the whole infrastructure back up without us.
-
Copies you control
Encrypted copies of your systems and data, kept where you control them. Tiered backups you can see in your panel: what is copied where, and when it last succeeded.
-
A sealed credentials vault
Every password and key we use, held by you. Opening it is never silent — we are alerted the moment it happens.
-
A plain-language runbook
What to restore and in what order, written for whoever on your team picks it up — not for us.
-
A restore test you run yourself
At handover, then whenever you ask. You see it work; we are notified that it ran.
If Stacoris disappeared tomorrow, you would open the kit, follow the runbook and run on your own. We think that is the only honest way to run someone else's infrastructure.
VMware exit and hardware refresh — 15 VMs, no working-day downtime
The estate had run production for ten years: three Dell R610s and a fibre-channel array, CPUs from 2010, the ERP database on spinning disks that the finance team felt every day, datastores at 88% and 99.9% full, and everything hanging off one shared chassis. Staying on VMware through a hardware refresh meant re-committing to a platform whose commercial terms were being rewritten around us.
We bought refurbished Dell R640s — five vendors quoted, and the spread on an identical build was a factor of two. Storage went local, on ZFS per node: no shared array, no single point of failure, more IOPS, the same usable capacity. We skipped high availability (at three nodes it is largely theatre) and spent the money on storage and backup instead.
The new cluster was built alongside the old one and production moved across one workload at a time — each cutover at night, verified before the next. Backups were rebuilt, local plus off-site S3; monitoring too, as a dashboard a non-technical owner can read. Two weeks. Nobody was asked to stop working.
The whole new cluster cost less than replacing the storage array it made redundant.
Disclosure: this is a manufacturing company in which our founder is a shareholder and has run the infrastructure for years. We ran the migration on our own production, with our own money, and we live with the result every day.
Twenty years, mostly on the unglamorous end
SAP, Unix, storage, and the migrations nobody wants to do twice. Client names withheld; descriptions are not.
- SAP on HP-UX — a Polish insurer, later part of a Korean automotive group. Built and ran the SAP 4.x landscape, then migrated it to new HP-UX hardware with an upgrade to 4.6 ahead of the group restructuring.
- Infrastructure sizing for SAP — a national television broadcaster. Servers, storage and backup sized against projected load; the broadcaster built its environment from that documentation.
- SAP 4.6 rollout — a nationwide consumer-electronics retail chain. Sized, then delivered on IBM hardware: three landscapes, fully redundant production, run under a written operating process.
- A VMware datacentre built from scratch — a manufacturing company our founder is a shareholder of. ERP, Git, Jira, remote desktops, production-line and R&D systems. The generation before it ran ten years — the standard we design to.
- VMware exit and hardware refresh — the same manufacturer, 2026. 15 VMs to Proxmox VE, shared array retired for local ZFS, backup and monitoring rebuilt. Case study above.
Four things you can hold us to
-
Fixed price, fixed scope
Price and scope are agreed before we start. Findings outside the scope go into the report under “further investigation” — they do not grow the engagement.
-
Read-only for assessments
We never need write permissions to tell you what your estate needs. A read-only role or an inventory export is all we ask for.
-
Night cutovers in your time zone
One workload at a time, verified before the next, in a window your business is not using. No downtime sold as “a planned maintenance window”.
-
One recommendation, not a menu
You get the options costed — 36-month total, break-even month, what stops being possible — and one recommendation, in writing.
What you see every day: your own panel
Every environment we run comes with a read-only panel for your team. These are real screens from the environment in the case study above, names changed — including the warnings. We would rather show you an honest panel than a green one.
Thirty minutes is enough to know whether we can help.
Tell us what you run and what the renewal quote says. We will tell you what it would take to move — or that you should stay.
Book a 30-minute call Pick a slot that suits you — it lands straight in our calendar. Or use the form below; we reply within one working day, Central European time.Contact
Emailpawel@stacoris.com
Phone+48 22 266 22 60
Based inWarsaw, Poland — working with clients across the EU, the UK and the US, Central European time.