646-558-2225Background
An MSP partner was running a sizable portion of its customers’ workloads on on-premises servers approaching their natural refresh cycle.
The environment included:
- VMware clusters with rapidly escalating licensing costs
- A mix of custom and proprietary software, tightly bound to specific hardware and MAC addresses
- Line-of-business apps where licence registration was tied to the original server identity, making any move off the existing hardware risky
They recognized that continuing on the same path would mean higher costs and increasing complexity, and needed a way to modernize without disrupting critical applications.
Pain Points
- Exploding VMware costs: Licensing and support had climbed to the point where staying on the same path was no longer sustainable.
- Impending hardware refresh: Reinvesting in new on-prem hardware would have required a major capital outlay without simplifying operations.
- Proprietary software constraints: Several key applications used registration tied to MAC IDs and specific server fingerprints, making a straightforward lift-and-shift impossible.
- Risk of disruption: Any misstep could trigger licence invalidation, forcing emergency vendor calls and downtime.
CaaB Approach
CaaB’s migration team worked directly with the MSP to understand the technical and licensing constraints around the proprietary software before moving any workloads.
The plan that emerged was hybrid by design:
- Preserve custom MAC IDs and server identity where required
- Migrate some servers as-is into CaaB’s environment
- Rebuild others cleanly, while coordinating licence handling and application re-registration with the MSP and software vendors
The objective was clear: modernize the infrastructure without breaking the software that ran the business.
Execution
- Discovery & Mapping
- Identified all servers with licence or registration dependencies
- Classified which workloads could be moved via V2V and which required rebuilds
- Identity-Sensitive Migration
- For the most licence-sensitive applications, CaaB worked with the MSP to preserve or emulate specific MAC addresses and server identifiers needed for licence validation.
- These workloads were migrated into CaaB with their logical identity intact, keeping software registrations valid.
- Rebuild & Modernize
- Less constrained workloads were rebuilt on fresh VMs in CaaB’s cloud, with updated OS and right-sized resources.
- Data was synchronized and cut over during agreed maintenance windows.
- Validation & Tuning
- Application access, licensing status, and performance were all validated post-migration.
- Resources were tuned based on real usage, with headroom for growth.
Impact
- Safe exit from legacy infrastructure: The MSP moved off aging hardware and unsustainable VMware pricing without breaking licence-locked applications.
- Modern, high-performance platform: Workloads now run on CaaB’s MSP-ready, high-performance cloud, improving reliability and resilience.
- Cost and complexity reduction: The MSP avoided a costly hardware refresh and reduced dependence on complex licensing models.
- Better use of technical talent: With CaaB handling the underlying infrastructure, engineers can now focus more on projects and services that drive revenue instead of lifecycle management of hosts.
Key Takeaway
Even when proprietary software and licence locks make migration look risky, an identity-aware approach—preserving MAC-bound and server-bound registrations where needed—can open a safe path forward.
By combining identity-sensitive migrations with selective rebuilds, CaaB helped the MSP move from an aging, high-cost on-prem stack to an MSP-ready, high-performance cloud platform, without sacrificing the applications their customers depend on every day.
