Liminal Works
Project-based virtualization consulting

Your VMware Escape Artist

Liminal Works helps small and mid-sized organizations move to Proxmox without turning production into a lab experiment. Your migration is planned, tested, documented, and handed back to your team.

Talk through your environment
1,000+ VMs migratedHands-on experience with enterprise-scale virtualization
Backup expertiseProxmox Backup Server, Veeam, and NAKIVO
Python automationUsed where it makes the work safer and repeatable
Services

Most engagements involve some combination of these three pieces.

Get from a VMware bill to a Proxmox environment your team can actually run.

01

Understand the environment

Get a clear inventory of the estate, its dependencies and oddball workloads, capacity requirements, and what should move, change, or stay put.Typical output: findings, target design, migration sequence, and a realistic risk list.

02

Build and migrate

Start with a properly designed Proxmox cluster and a representative pilot, then move production workloads in controlled batches with validation and rollback points.Typical output: working platform, migrated VMs, runbooks, and configuration records.

03

Protect the new environment

Carry existing Veeam protection into Proxmox, or transition VMware backup workflows to NAKIVO or Proxmox Backup Server. Liminal Works is a NAKIVO reseller with hands-on experience across all three platforms.Typical output: platform selection, licensing guidance, migrated backup jobs, restore tests, and operating notes.

Experience that transfers

Proven at a scale where shortcuts show up quickly.

Liminal Works brings experience earned migrating more than 1,000 virtual machines in enterprise-scale infrastructure. That experience shapes a practical approach: know the dependencies, automate the repetitive parts, test restores, keep a rollback path, and leave useful documentation behind.

In one enterprise-scale migration, careful capacity planning and phased hardware reuse made it possible to complete the move without purchasing additional hardware. Every environment is different, but the same approach may reduce or eliminate new infrastructure costs.

Why Liminal Works? You work directly with the person doing the technical work. There is no handoff from a sales team to a rotating cast of engineers.

What matters in a migration

  • A pilot that resembles production
  • Backups that have actually been restored
  • Scripts another engineer can read
  • Clear stop and rollback criteria
  • A platform your team can own afterward
Working together

A practical engagement.

The exact plan depends on the environment. The working rhythm is usually straightforward.

Initial reviewStart with the current setup, the reason for moving, timing, and anything that already looks risky.
Written scopeGet a defined piece of work, clear responsibilities, and a finish line.
Pilot firstProve the approach on representative systems before committing the rest of the estate.
Work in wavesMigrations are scheduled, checked, and documented. Problems get solved before the next batch.
Clean handoffYour team gets the documentation, scripts, and context needed to operate the result.
Engagement model

Remote first, with local support when needed.

Project-based by defaultEach engagement has a defined finish line. When the work is complete, your team receives the documentation, scripts, and operating context. There is no required MSP contract or recurring service fee. As-needed support remains available at standard hourly rates.

Remote engagements nationwideMost projects are delivered through secure client-provided access. Liminal Works handles assessment, platform deployment, migration, automation, testing, and documentation while your IT team provides hands-on support for the hardware.

On-site in the Chicago areaFor organizations in the Chicago suburbs and surrounding area, on-site assistance is available by arrangement, including evening and weekend work when the project calls for it.

Start with a conversation

Let’s plan your VMware exit.

A rough VM count, current storage, backup platform, and desired timeline are enough to start.