Compete Migration for ISVs: The Hidden Costs and Risks of Migrating to Azure

The process of migrating software vendors' products and customer bases from competing cloud platforms to Microsoft Azure is known as compete migration for ISVs. This process combines engineering work (re-platforming on Azure) with go-to-market work (moving customers, qualifying for incentives, building Microsoft seller relationships). The economic case for compete migration is strong, with Microsoft programs offering hundreds of thousands of dollars in funding for qualifying ISVs.

However, the risk case is also real. McKinsey research found that cloud migration inefficiencies cost the average company 14 percent more in migration spend than planned each year, with 38 percent of companies seeing their migrations delayed by more than one quarter.

The costs of compete migration are not always accounted for. Three cost buckets show up on the actual P&L of a compete migration: engineering re-platforming and tooling, customer-side migration costs, and parallel-run and dual-cloud operations.

Re-platforming code from AWS-native or GCP-native services to Azure equivalents is rarely a clean swap. Customers also need to be moved off the old platform onto the new one, which includes downtime windows, change management, training, support load during the transition, and data egress fees paid to the source cloud.

Three risks decide whether the compete migration program pays back: customer churn during the migration window, Microsoft program rule changes mid-cycle, and hitting the $100K ACR threshold on the program clock.