BestPaid guides · Xamarin · .NET MAUI

Xamarin.Forms to .NET MAUI 11: a migration checklist for 2026

Xamarin support ended on May 1, 2024, and Xamarin tops out at Android API 34 and Xcode 15. Google Play now accepts updates only for apps that target API 36, and the App Store only takes Xcode 26 builds. A Xamarin.Forms app can't ship either way until it moves to .NET MAUI, and the version to move to today is MAUI 11.

Sources: Microsoft's Xamarin support policy, the .NET MAUI support policy and the Xamarin to .NET MAUI migration docs; Google Play's target API rules. This page is our own summary; follow the official documentation for every detail.

1. Inventory before you touch code

2. Move to the single-project structure

3. Renderers, effects and services

4. Make the builds store-ready

5. Roll out

  1. Ship to Play Console internal testing and TestFlight first.
  2. Keep the old app's bundle ID and package name, and sign with the same keys, so the update installs over the old version and users keep their data.
  3. Roll out in stages and watch crash reports.

Already on .NET MAUI 8, 9 or 10? MAUI 9 is out of support and MAUI 10 support ends on May 11, 2027; MAUI 11 is supported until May 9, 2028, so the upgrade to MAUI 11 is usually the shorter path.

Rather have it done? We migrate Xamarin.Forms apps to .NET MAUI 11 at a fixed price, with store-ready builds for Google Play and the App Store. It starts with a $490 audit of every dependency and a fixed quote within 3 business days.
See the MAUI migration offer