Ryz Labs/Migrations/Xamarin to React Native
Migrations

Xamarin to React Native Migration Runbook

How to get a Xamarin app shipping again: a release-unblock plan, a native shell, React Native screens one flow at a time, and store phased rollouts.

Moving from Xamarin or Xamarin.Forms to React Native means rebuilding the UI and app logic in TypeScript on React Native, flow by flow, inside a native host shell that builds with current Apple and Google SDKs. The recommended approach is incremental: first unblock store releases, then move screens one at a time behind remote flags and ship each slice through phased store rollouts. What decides success is the native dependency audit. Every Xamarin binding, DependencyService call and custom renderer needs a named replacement before you port the screen that uses it.

Why teams migrate now

For Xamarin teams the pressure is not a vague end-of-life notice. Your next release gets rejected. The dates line up like this:

Put those side by side: Xamarin stops at Xcode 15 and API 34, while the stores now ask for Xcode 26 and API 36. A new Xamarin build cannot meet either store's upload rule. The version already in the store keeps running on the devices that have it, but you cannot push a fix, a security patch or a new SDK version. On Android you also start losing new installs on newer phones, because your target API is below 35.

The business consequence is a frozen app. A payment SDK update, a login provider's new redirect rules, a crash on a new OS version: none of these can be fixed in the field, and security reviews flag the unsupported runtime and the SDKs you can't update.

On the React Native side, the target is stable. The React Native versions page lists 0.88 as the latest release (announced October 19, 2026). The New Architecture became the default in 0.76, and from 0.82 React Native runs only on the New Architecture; opt-out flags are ignored. That last fact shapes the whole dependency audit below.

Before you start: inventory and baseline

Mobile migrations fail on things nobody wrote down. Inventory first.

The strangler-fig plan, phase by phase

A mobile strangler fig is not a web one. You can't route a URL path to two servers; one binary ships to each store, and it must build with current SDKs.

Phase 0: Decide the shell and unblock releases

Choose the host that ships to the store from now on. For most teams it is a thin native shell in Swift and Kotlin that owns app startup, navigation chrome, push registration, deep links and the platform extensions, with React Native added through its official integration-with-existing-apps path. Either way, set up the shell with the same bundle ID, application ID and signing identity as the Xamarin app, and prove you can upload a build to TestFlight and a Play internal track. If you have a critical fix that can't wait for the port, Microsoft's path from Xamarin.iOS and Xamarin.Android to .NET for iOS and Android (see the .NET MAUI migration guide) is the stopgap for getting the existing code shipping again. Exit criteria: an empty shell signed with production identity passes store processing on both platforms.

Phase 1: Native module and bindings audit

Walk the native surface list and give every item a replacement: a maintained React Native library, a platform SDK called from a native module you write as a TurboModule in Swift or Kotlin, or deletion. Because React Native 0.82 and later run only on the New Architecture, a library that only supports the old bridge is a blocker, not a warning. Check each candidate against the New Architecture before you commit to it. Custom renderers usually become plain React components; renderers that wrap a native view become Fabric native components. Exit criteria: no item in the inventory without a named replacement and a spike that proves it builds on both platforms.

Phase 2: Data, auth and session continuity

Build the migration code before the screens. On first launch of the new binary, read the Xamarin app's local data and move it into the new store: open the existing SQLite file where it lives or copy it, run a schema check, and keep the old file until the new one is verified. For tokens, the new app must read what Xamarin.Essentials SecureStorage wrote. On iOS that means the same Keychain service name and access group; on Android it means the same Keystore alias and preferences file, read from a native module, then rewritten into react-native-keychain or your chosen secure store. If a token can't be migrated safely, plan a silent refresh or a single re-login and measure it. Exit criteria: an upgrade test from the current store build to the new build keeps the user signed in and keeps offline data, on real devices for both platforms.

Phase 3: Screen-by-screen port behind remote flags

Port flows in the order your inventory gives you, starting with a low-risk, high-traffic screen such as settings or a read-only list. Each React Native screen is mounted as its own root view in the native shell, so navigation can mix native and React Native screens while the port runs. Shared logic moves into a TypeScript package with unit tests ported from the C# tests. Every new screen ships behind a remote flag, so a release can carry a finished screen that stays off until QA signs off. Exit criteria per flow: parity suite passes, accessibility checks pass, and crash-free sessions on the flagged cohort match the baseline.

Phase 4: Staged store releases

Ship the first public build with only the shell, migration code and a few React Native screens switched on. Use App Store Connect's phased release for automatic updates and Google Play's staged rollout percentages, and watch crash-free sessions, login success and data-migration error events before widening. Turn flags on per flow for growing cohorts. Exit criteria: full rollout on both stores with metrics at or above baseline.

Phase 5: Remove Xamarin and set the OTA policy

Delete the last C# screens, the Xamarin build pipeline and, once telemetry shows no users on old local formats, the migration shims. Decide your over-the-air update policy now: an OTA service (for example Expo's EAS Update or a self-hosted bundle server) can ship JavaScript and assets, never native code, so pin each JS bundle to a runtime version that matches the native binary. Keep OTA for fixes that stay within the current Apple and Google review guidelines, and send anything that changes native code or app behavior meaningfully through the stores. Exit criteria: no Xamarin code in the repo, and a documented OTA runbook with a rollback command.

PhaseGoalKey techniqueExit criteria
0. ShellShip to stores againThin Swift/Kotlin host with React Native integration, same bundle ID and signingEmpty shell passes TestFlight and Play processing
1. AuditNo unknown native codeMap bindings, DependencyService and renderers to New Architecture libraries or TurboModulesEvery item has a replacement and a working spike
2. ContinuityUsers stay signed in, data survivesFirst-launch migration of SQLite/Realm files and SecureStorage tokensUpgrade test from store build keeps session and offline data
3. PortMove flows one by oneReact Native root view per screen, remote flags, shared TypeScript packageParity suite and crash-free baseline met per flow
4. RolloutReach all users safelyApp Store phased release, Play staged rollout, flag cohortsFull rollout at or above baseline metrics
5. CleanupOne codebase, clear update rulesDelete C# code and shims, OTA bundles pinned to runtime versionNo Xamarin in repo; OTA rollback documented

Cutover and rollback

Traffic on mobile moves through three dials: the store rollout percentage, the remote flag per flow, and later the OTA channel.

Go/no-go checklist for each public release: upgrade test from the current store build passes on both platforms; crash-free sessions on internal and beta tracks at or above baseline; login success rate unchanged; data-migration error events at zero in beta; push notifications and deep links verified; accessibility pass on new screens; store metadata and privacy declarations updated for any new SDKs; rollback owner named.

Rollback path by phase:

Risk matrix

RiskLikelihoodImpactMitigationEarly warning signal
A critical bug in the frozen Xamarin version before the new shell shipsMediumHighKeep a .NET for iOS/Android stopgap branch ready; prioritize the shell firstRising crash rate on a new OS version in store analytics
Third-party library lacks New Architecture supportHighMediumAudit in Phase 1; write a TurboModule over the vendor's native SDKLibrary issue tracker shows open New Architecture requests
Users logged out after update because Keychain or Keystore items can't be readMediumHighMatch service name, access group and aliases; test upgrade on real devicesLogin screen views spike in the first rollout cohort
Offline data lost or corrupted during first-launch migrationMediumHighCopy, verify, then switch; keep the original file until verifiedMigration error events or empty-state views for returning users
Signing identity or bundle ID mismatch blocks the update pathLowHighProve production signing on an empty shell in Phase 0Store processing errors or "different app" warnings on internal track
Performance regression on low-end Android devicesMediumMediumProfile with Hermes and release builds; virtualize long listsCold start and frame-drop metrics worse than baseline on beta track
OTA update ships JS that expects native code not in the installed binaryMediumHighPin bundles to runtime version; block mismatched channels in CICrash spike immediately after an OTA publish
Backend change breaks the old binary still in the fieldMediumMediumVersioned APIs; contract tests for both client versionsError rates by client version in API logs

Typical team shape

A Xamarin exit needs people who know both sides of the bridge: someone who can read the old C# bindings and someone who can write Swift and Kotlin native modules for React Native. A common shape:

Many teams begin with a pod of 3 to 5 senior engineers (a tech lead plus engineers), and a full pod is about seven. Ryz engineers on your team start from $7,000 per month (our published range is $7,000–$15,000 per engineer per month, mostly mid-level to senior), quoted per team. Your project cost is team size × months × monthly rate, so the levers are scope and team size, not a fixed bid. Ryz engineers work on your team, reporting to your leads. Once you say go, engineers can typically start in under two weeks. If you want a team for this, scope your team with us, or see how our mobile app development teams work.

Where an AI pod helps (and where it doesn't)

A lot of a Xamarin port is translation work: XAML layouts to React components, C# view models to hooks, value converters to plain functions, and NUnit tests to Jest. Our AI pod uses coding assistants to draft these translations, to generate the first pass of the parity test scripts from the existing UI flows, to scan the solution for every DependencyService and binding reference, and to triage crash logs and diffs during rollouts.

It doesn't replace judgment on the hard parts. Keychain access groups, Keystore aliases, store review rules and native module threading are where generated code is most often confidently wrong. Every change goes through human code review, runs against the parity suite on real devices, and ships behind a flag. If you decide the .NET path instead, Microsoft documents a GitHub Copilot upgrade agent that lists .NET MAUI and Xamarin among its supported project types.

When not to migrate (yet)

Ryz isn't the right fit if you want a self-serve freelance marketplace or short hourly gigs to patch one screen.

Related

FAQ

How long does a Xamarin to React Native migration take?

It depends on the number of screens and flows, how many native bindings and custom renderers the app uses, how much business logic sits in shared C# code, the offline data model, and how many platform extensions you have. The dependency audit in Phase 1 is the best point to estimate, because it turns unknown native code into a list with a replacement for each item.

Can we keep shipping features while we migrate?

Yes, once the new shell ships. Before that, the Xamarin app can't pass store upload rules, so new features have to wait or go through a .NET for iOS and Android stopgap. After the shell is live, new features are built in React Native only, which also pulls the port forward.

Will users have to log in again or lose offline data?

They shouldn't, if the new app keeps the same bundle ID, signing identity, Keychain access group and Keystore aliases, and runs a first-launch migration of local files. Test the upgrade from the current store build on real devices before every public release, and plan a silent token refresh for any token you can't move safely.

Should we choose .NET MAUI or React Native?

Choose .NET MAUI if your team is C#-first and most of the value is in shared .NET code, since Microsoft's migration path keeps much of it. Choose React Native if you want shared code with a React web app, a wider hiring pool and a large library ecosystem, and you're willing to rewrite the UI layer.

What does a Xamarin migration cost?

Cost is team size multiplied by months multiplied by the monthly rate per engineer. The drivers are screen count, native module work, data migration complexity and how many flows need parity tests. We quote per team after the inventory, with a plan and the names of the engineers, not a fixed project price.

Questions we didn't answer? Email info@ryzlabs.com.

Thanks — your message has been sent. We’ll get back to you soon.

Something went wrong while sending your message. Please try again or email info@ryzlabs.com.

Explore Ryz Labs

Software development servicesAI development companyIndustriesStaff augmentationAI pod teamsNearshore software developmentHire engineers by roleEngineer ratesGuidesBuyer guidesCase studiesHow we vet engineers

Ryz Labs

Senior engineers on your team. AI pod teams that ship.

Tell us what you're building. You get a scoped plan, a price and the names of the people who would do the work.

  • Only the top 1% of tens of thousands interviewed make it
  • On US business hours, including New York hours
  • Trusted by Fortune 500 engineering teams

Tell us who you need

A Ryz partner replies with a scoped team plan.

Start a conversation →

Prefer to talk? Book a 15-min call →