Named, costed exits from per-device, per-IP and per-socket licensing, monitoring, DDI and virtualisation, run in parallel with your current stack so checks, thresholds and history survive the move.
- A like-for-like comparison priced at your real device count, before you commit
- Parallel run: old and new stacks side by side until the evidence is in
- Checks, thresholds, dashboards and history preserved, not rebuilt
- A rollback plan on every cutover
How it fits together
Leave a licence without losing a single check
The new stack is built beside the old one and both run in parallel until the results match. Only then is the old one switched off.
Today
- SolarWinds / ManageEnginePer-device licensing
- InfobloxPer-IP licensing
- VMwarePer-socket licensing
Parallel run
- Old and new side by side
- Checks, thresholds and historyCarried over
- VerifyLike for like
- Rollback planOn every cutover
After
- ZabbixMonitoring
- BIND + Kea + NetBoxDDI
- Proxmox VEVirtualisation
Three named exits
Each one replaces a recurring licence with an open-source stack we deploy, harden and operate.
SolarWinds / ManageEngine → Zabbix
Monitoring without per-device or per-sensor licences, the Kuant NMS core.
Infoblox → BIND + Kea + NetBox
Enterprise DDI on the open-source components it is built from, DNS, DHCP and IPAM without a per-IP licence.
VMware → Proxmox VE
A costed exit from per-socket repricing, with the storage and backup design done properly.
How a migration runs
The renewal date is the deadline; the parallel run is the safety net.
Assess
Inventory at your real device count, a licence-cost model of staying versus moving, and the risks named up front.
Parallel build
The new stack is built beside the old one, nothing is switched off, nothing is bet on a promise.
Verify
Like-for-like evidence: the same checks firing, the same coverage, side by side, for as long as it takes to trust it.
Cutover
A planned window with a rollback path. The old system stays restorable until you sign it off.
Decommission & handover
Runbooks, training and documentation handed over; the licence lapses instead of renewing.
Scope it before the renewal, not after
Most exits are scoped 3-6 months before a renewal date, enough time for the parallel run to produce evidence instead of pressure. Bring your renewal quote; we will price the comparison against it.
Use Cases
Monitoring renewal is due
A like-for-like comparison at your real device count, then a migration that preserves checks, thresholds and history.
VMware licensing has changed
Per-socket repricing turned a stable platform into a budget problem. The Proxmox exit is staged, tested and reversible.
DDI renewal is due
Per-IP licensing on DNS/DHCP/IPAM, replaced with BIND, Kea and NetBox, run by us under SLA.
Audit needs evidence
Coverage, detection-to-resolution times and a Git-backed change trail, produced on demand, before and after the move.
Talk to an engineer about Licence-Exit Migrations
We start with your environment as it actually is: architecture, tooling, gaps, constraints and the outcomes the business is asking for.
Get in Touch