Migration audit
Screens, NuGet packages and device SDKs reviewed before any code moves.
Mobile
Xamarin to .NET MAUI migration, by a team that shipped both
Microsoft stopped supporting Xamarin on 1 May 2024. We built three apps on Xamarin and one on .NET MAUI, and we carry Xamarin.Forms apps across.
1 May 2024Xamarin support ended
3Published builds on Xamarin
1Published build on .NET MAUI
4Platforms from one .NET MAUI project
What we build
What a Xamarin migration covers
Upgrade Assistant run
The .NET Upgrade Assistant converts the project, then engineers finish what it leaves.
Device features carried over
Bluetooth LE, GPS, photos and vendor SDKs, as on Hydrajaws and the Digital Testing Platform.
Stabilise first
Environments documented and rebuilt before the move, as on Hydrajaws.
Architecture
What a .NET MAUI app talks to
A .NET MAUI field app with Bluetooth devices
Devices
Pull testersBluetooth LE
Torque wrenchesBluetooth LE
App
.NET MAUI appSteps, GPS, photos, signatures
Local storageWorks offline
Sync
Secure syncWhen the signal returns
Back end
ASP.NET CoreWith Azure SQL
From the Digital Testing Platform for work-at-height anchor and torque checks.
Migration
From Xamarin.Forms to .NET MAUI
The path Microsoft documents
Ended 1 May 2024
Xamarin.Forms
- No longer supported or updated by Microsoft
- Applies to all Xamarin SDKs
Current
.NET MAUI
- Android, iOS, macOS and Windows from one project
- Microsoft notes most apps need extra effort after the tool runs
Source: Microsoft, Xamarin support page and .NET MAUI migration guide, checked 29 October 2026.
Builds
Four builds, three on Xamarin and one on .NET MAUI
Construction safety testing, United Kingdom
Hydrajaws Limited
A Xamarin and .NET app recovered from an abandoned codebase, then shipped as a free and a paid version.
500%Surge in potential clients
Statutory inspection, United Kingdom
Work-at-height anchor and torque platform
The .NET MAUI field app reads pull testers over Bluetooth LE and captures GPS and photos.
70%Faster reporting cycle
Education, Norway
National education analytics platform
A Xamarin mobile app inside a .NET and Angular platform hosted on AWS.
No lossData moved from OPAL 1.0 to OPAL 2.0
Fit check
When a migration is the right call
Pick Xamarin and .NET MAUI when
- Your app still runs on Xamarin.Forms
- It talks to Bluetooth devices or vendor SDKs
- You want one .NET codebase for Android and iOS
Look elsewhere when
- The app has a few screens and a native rewrite costs less than a migration
- Your team has moved to React Native and wants to stay there
- A key package has no .NET MAUI version and no replacement
Related: .NET, Azure, React Native, and the construction and automotive sectors.
Stack
What a .NET MAUI app usually ships with
.NET
Azure
Angular
iOS
Android
DockerFAQs
What buyers ask first
Is Xamarin still supported?
No. Microsoft ended support for Xamarin on 1 May 2024, including Xamarin.Forms. It no longer supports or updates it.
Can the Upgrade Assistant migrate my app automatically?
It converts Xamarin.Forms projects to .NET MAUI, and Microsoft says most apps need extra effort afterwards. Some NuGet packages may have no .NET MAUI version, so we audit them first.
How long does a migration take?
It depends on screens, packages and device SDKs, so we do not quote from a web page. After a 30-minute assessment we price the work in phases.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us what still runs on Xamarin
Thirty minutes on your app, its packages and its device integrations. No sales pitch.