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.
1. Inventory before you touch code
- List every NuGet package in the shared and platform projects and find its .NET MAUI equivalent. The usual swaps: Xamarin.Essentials is built into MAUI; Xamarin.CommunityToolkit becomes CommunityToolkit.Maui; SkiaSharp.Views.Forms becomes SkiaSharp.Views.Maui; vendor control suites (Syncfusion, Telerik, DevExpress) have separate MAUI packages.
- List custom renderers, effects and
DependencyService implementations: these are where most of the work is.
- List native bindings and third-party SDKs (payments, analytics, maps, push). Each needs a version that builds for current Android and iOS SDKs and ships 16 KB-aligned native libraries for Android.
- Write down the platforms and minimum OS versions you must keep supporting.
2. Move to the single-project structure
- Create a .NET MAUI project and move the shared code in; platform code goes into the
Platforms folders.
- Images, fonts and the splash screen become
MauiImage, MauiFont and MauiSplashScreen items under Resources; the build generates the per-platform sizes.
- Namespaces change from
Xamarin.Forms to Microsoft.Maui and Microsoft.Maui.Controls; Essentials APIs live in Microsoft.Maui.* namespaces.
- App start-up and service registration move to
MauiProgram.cs.
3. Renderers, effects and services
- Rewrite custom renderers as handlers or handler mappings. Compatibility shims for renderers exist and can help you get a first build, but treat them as a bridge, not the destination.
DependencyService implementations become services registered with dependency injection in MauiProgram.cs.
MessagingCenter is obsolete: move to a messenger such as WeakReferenceMessenger from CommunityToolkit.Mvvm.
- Prefer
CollectionView over ListView for lists you touch anyway.
4. Make the builds store-ready
- Android: target API 36. Since August 31, 2026, Google Play takes app updates only for apps that target API 36. Make sure every native library is 16 KB-aligned too: from February 1, 2027, updates without 16 KB support can't be released (our Android checklist).
- iOS: build with Xcode 26 and the iOS 26 SDK, which the App Store requires since April 28, 2026; update provisioning and entitlements as needed.
- Run the app on real devices for both platforms. Pay special attention to layouts: MAUI's layout engine is not Xamarin.Forms', and spacing, padding and default sizes can differ.
5. Roll out
- Ship to Play Console internal testing and TestFlight first.
- 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.
- 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