Independent Service Vendor (ISV) software transfer fees are among the most common obstacles in IBM i cloud migration. What makes it even worse is that they often surface when an organization is already deep into the evaluation process.

You have done the research, compared hosting providers, and run the numbers. The case for moving your IBM i to the cloud looks solid. Then your software vendor sends a transfer-fee quote, and everything stops.

For an experienced hosting professional, this is one of the most predictable failure points in IBM i cloud projects, and the fix is straightforward. When you know what to ask and when to ask it, you can clear this hurdle early.

The Reason ISVs Charge Transfer Fees

ISV applications rely on specialized software keys tied to specific physical hardware environments. This structure mirrors licensing frameworks used throughout the enterprise technology market. Moving your applications to a managed cloud environment requires the primary software vendor to authorize the transfer of those keys.

What most IT leaders do not expect is how wide the range can be. Some might be a nominal one-time charge. The fees can also reach figures that bear no apparent relationship to the size of your organization or the scope of your usage. ISV practices are inconsistent across the market, and the only way to know where yours falls is to ask directly.

IBM’s own licensing structure shifted materially in 2025. IBM eliminated perpetual software licensing for its IBM i stack and moved to mandatory subscription terms. That change affected the ongoing cost structure for IBM i environments. It may have prompted ISVs to revise their own transfer fee models as well.

Managing Software Licensing Fees

Bob Losey has evaluated diverse vendor fee frameworks over decades of managing specialized infrastructure migrations for enterprise clients.

“Most all ISVs are going to charge a transfer fee. The practices of ISVs are all over the board. I have seen some ISVs charge outrageous transfer fees. One of my clients was told they had to pay a million dollars to transfer their software. We ultimately got the transfer fee down and had the software provider throw in a bunch of extras, so our client got more of their money back. But you got to find that out first, because if you do all this investigation and then you find out you have to pay a transfer fee you can’t justify, you’ve wasted your time.” – Bob Losey, Founder and President, Source Data Products

This scenario of a million-dollar fee demonstrates the value of assessing potential licensing fees early in your process. Our team negotiated that fee down substantially, but it was only possible because we caught the issue early.

Three Questions to Ask Every ISV

Before any technical assessment begins, get three answers from your software vendor in writing.

1. Will the ISV allow the software to move to a hosted cloud environment? Some vendors prohibit third-party hosting and require customers to use their own proprietary cloud platform. That restriction may be buried in the licensing agreement. Finding it early gives you options.
2. What’s covered under the transfer fee? You can’t always count on the fees to cover what you expect. A distribution company we worked with in New England received a transfer fee quote. They paid it and moved forward with migration planning. The following year, the ISV informed them that the fee had covered only one year … and only for one of their five locations.
3. Is the transfer fee a one-time payment or does it recur? With IBM’s move away from perpetual licensing, ISV subscription structures have grown more common. Assumptions made even two years ago may no longer reflect current terms. Get the answer in writing, tied to specific contract language, before a single dollar moves.

Evaluating Transfer Fees Within Your Project Budget

Most ISV transfer fees fall somewhere between reasonable and high-priced. The patterns that define the worst actors are well-documented. They might have:

• Fees tied to server categories rather than actual usage.
• Multi-location structures that multiply costs in ways the initial quote obscures
• Time-limited authorizations that create recurring leverage points at every renewal cycle.

When transfer fees are fair, the migration math still usually favors the cloud. Hardware costs, IBM software subscriptions, and ongoing maintenance for on-premises IBM i environments have all shifted in recent years.

A small business that purchased a Power server between 2010 and 2018 likely paid somewhere between $12,000 and $18,000. Today’s entry-level Power11 carries a price tag of around $36,000. You also have the IBM software subscriptions, adding $10,000 to $18,000 annually on top of that.

Against that baseline, a Cloud400 hosting fee of $800 to $1,500 per month offers a clear financial advantage, even with a meaningful ISV transfer fee factored in. You can learn more in a recent post comparing hosting math to buying new hardware.

Licensing fees represent a manageable project variable rather than an automatic barrier to transitioning to the cloud. Understanding the fees early lets you calculate project returns with confidence.

Not sure how your ISV fee fits into the broader migration picture? Reach out to the Source Data team before the clock starts and get the ISV piece scoped before any technical assessment begins.

Sequencing the IBM i Cloud Migration Conversation

The most consistent guidance from thousands of IBM i client environments points to the same answer. If your organization runs ISV-developed software on IBM i, the first call in any cloud migration evaluation should be to your software providers.

Confirm whether third-party hosting is permitted under your current license terms. Get the scope of the transfer fee in writing and ask whether the authorization is perpetual or time limited. If anything in the response feels incomplete or conditional, ask follow-up questions before any answer is locked into a contract.

Securing these details allows you to compare hosting infrastructure and build an accurate, numbers-driven migration roadmap. The NIST cloud computing framework provides a reference point for understanding vendor lock-in and portability considerations relevant to ISV licensing restrictions in hosted environments.

Technical complexity is rarely the issue that derails IBM i cloud projects. More often, these projects run into problems stemming from licensing discussions that begin too late in the process. The migration itself is almost always more straightforward than organizations expect.

FAQs about ISV Licensing Fees

What is an ISV software transfer fee for IBM i?

An ISV transfer fee is a charge required to move licensed software from one hardware environment to another. Because ISVs tie their software keys to hardware serial numbers, cloud migrations require generating new keys. The cost and associated terms vary by vendor policy across the enterprise software market.

Can an ISV refuse to let you move IBM i software to the cloud?

Yes, certain application developers restrict deployment options to their own proprietary platforms or prohibit third-party managed hosting. Reviewing your license agreements and contacting your vendor directly ensures you prevent unexpected compliance challenges during your evaluation.

How much do ISV transfer fees typically cost for IBM i migrations?

Transfer fees range from reasonable one-time charges to amounts in the hundreds of thousands of dollars. There is no standard across the market. The fee may be tied to server categories, user count, number of locations, or annual subscription terms. Getting a written quote with full scope detail before migration planning begins is essential. We touched on related issues in a post about how subscription fees impact SMBs.

Are IBM i ISV transfer fees negotiable?

Yes, software vendors have strong commercial incentives to maintain long-term client relationships across multiple software generations. Working alongside an experienced hosting partner who understands software footprints gives you a distinct advantage during negotiations. The key is addressing these licensing costs before presenting your final project timelines to leadership.

Does a high ISV transfer fee mean cloud migration is not worth it for IBM i?

The fee is one variable in a broader cost comparison. New Power11 hardware starts around $36,000, with IBM software subscriptions adding $10,000 to $18,000 annually. Cloud400 hosting typically ranges from $800 to $1,500 per month, depending on your specific your hosting resources and infrastructure environment. Hosting can still pay you back even with substantial transfer fees. Run the full numbers before treating the fee as a deal-breaker.

When in the IBM i cloud evaluation process should you contact your ISV?

Initiate contact with your software vendor before engaging hosting providers or starting deep technical reviews. Establishing your licensing parameters first ensures you invest your time in an authorized, fully viable migration pathway. Organizations that prioritize this conversation save considerable resources by eliminating structural surprises late in the project.

Start the ISV Conversation Before You Start the Clock

ISV transfer fees are the most predictable issue in IBM i cloud migration. When you put that conversation early, you set yourself up for success.

Source Data Products helps IBM i teams surface licensing risks before planning begins. We clarify transfer terms, validate assumptions, and support vendor negotiations. Contact our team to resolve the ISV question early and move forward with confidence.

Bob Losey is the founder and president of Source Data Products. He has served as a Premier IBM Business Partner continuously since 1992 and previously served as President of the Association of Service and Computer Dealers International (ASCDI).