Join the VirtaMove ISV Program
ISV companies know that many applications remain on End-of-Life (EOL) operating systems because traditional modernization approaches are too costly, time-consuming, and resource-intensive.
As a result, Windows ISVs are losing maintenance and upgrade revenue as customers fall out of support and fail to buy and upgrade to modern versions of their applications.
VirtaMove has a unique ISV software offering. Our ISV Program can help ISVs open up and lock in tens of millions of dollars in additional recurring legacy maintenance revenue and accelerate additional revenue from customer upgrades.
The migration partner of choice for Fortune 500 companies
How Moving a Legacy Independent Software Vendor App With VirtaMove Works
Moving legacy applications forward to new, modern servers and operating systems is complex because you need to determine and inherit the current state of installed production applications. Most ISVs can’t deal with application state customer configuration issues in production servers; consequently, they recommend clean, new app installs on new servers with a migration plan.
Customers opt out of upgrades because clean, new installs break all of the production state constraints and create disruption and long migration delays.
The VirtaMove Independent Software Vendor Program Solves These Problems For ISVs
It offers two-way partnering and revenue sharing between ISVs and VirtaMove. We roll legacy ISV apps and state/configuration data forward to modern servers for customers; in the process, we open up and lock in long-term legacy maintenance contracts for the ISV. In addition, once the legacy ISV app is running on modern servers, we offer a planned and controlled way to do an in-place upgrade of the ISV app to a modern version. This generates additional upgrade revenue, maintenance, and customer lock-in.
Benefits of Being a Cloud Migration Consultant Partner with VirtaMove
Why partner with VirtaMove? Because we’re the future of application migrations.
Migration is about moving to a better system. We hope you’ll join our partnership programs.
How A Legacy Application Migration Works
Step 1In Stage 1, the legacy ISV app resides in its initial state on an outdated Windows Server and OS, such as WS2003 or WS2008.
Step 2In Stage 2, the legacy ISV app is copied into a VirtaMove container. The container resides on a modern Windows Server and secure OS, such as WS2012 or WS2016, and provides a safe sandbox for application testing.
Step 3Stage 3 involves removing or dissolving the container on the new server. This achieves a stateful re-install of the legacy ISV app on the new server and modern OS.
Step 4Stage 4 sees an in-place upgrade of the ISV app on the new server, which allows a modern version of the app to be installed on top of the legacy ISV version. The modern version inherits state and configuration information.
Step 5Stage 5 illustrates the containerization option. The ISV app is statefully installed into a Windows Container, on a host OS or under Microsoft Azure.
Let’s Talk About Working Together
Want to keep delivering better migrations to your customers? Let’s work together.