Third-Party Software Licensing in Application Modernization Projects (It’s Complicated)Mark Woodward
Most customers must address the issue of software licensing when they undertake Windows Server application modernization projects.
I own the software – licensing is a non-issue, right?
If customers are modernizing or migrating a custom-developed, in-house application along with the associated software stack, they often believe that licensing is a non-issue. They own the software and can move the application and its software components to whatever new server and operating system they choose. Not so fast – software licensing can in fact become complicated, and quickly.
First, let’s be clear: VirtaMove’s automated modernization software can’t be used by customers to avoid third-party software licensing. We do not generate vendor authorization keys for customers, although we will move an authorized license even if it is tied to a specific hardware component or OS version.
Upgrading can drive associated license and maintenance costs
By virtue of upgrading to new servers and OS versions, VirtaMove typically drives additional license and maintenance revenue for software vendors. If a license key needs to be regenerated by a vendor, the process is normally as simple as contacting the ISV and paying the fee they may charge for new server authorization. If the original server is to be retired, the application license is often transferable.
Consider the case of custom-developed applications built on a Microsoft stack. When customers modernize to a new server and operating system, they may also need to modernize and upgrade to new SQL Server and WebSphere stack versions. Depending on the nature of the licensing agreement, upgrading can drive associated license and maintenance costs. Each customer’s scenario is unique and many upgrades are covered by MLA or other vendor licensing agreements.
Frequently, ISV software licenses are silent on the issue of OS versions and customers can reasonably assume that they are authorized to move an existing licence of old ISV software to a new OS version if they stay on the same size server and continue to pay maintenance or other software charges. ISVs realize that keeping customers using their software opens the door to future application upgrades and additional maintenance.
Did you say ransom fee?
In some cases, an ISV may attempt to make customers pay an onerous ransom fee for adding little new functionality (other than a move to a new vendor-supported operating system version). In such cases, it isn’t surprising if customers look to technology that helps them containerize and isolate applications to run on a new OS as they bridge to new datacenter server or cloud environments.
Sometimes you can resolve with a re-install
An application might be composed of several pieces, including a licensing component. At times, you might be able to resolve a licensing issue by opting to re-install the application on the new server. Keep in mind that if your Microsoft titles are licensed through Software Assurance for example, you may only have a certain number of reinstalls available to you.
Given open source, ISV software licenses, and third-party tools, the issue of software licensing can quickly become complex and must be considered when software is modernized or moved to new server or cloud platforms. At VirtaMove, we help customers deal with these issues daily. We can help find the right solution for modernizing software to make the right decision for your business.