Migrate your React Native app to New Architecture
Outdated architecture holds your app back even if your React Native version is up to date. We help teams safely migrate to the New Architecture so they can keep shipping features, unlock new platform capabilities, and stay compatible with upcoming React Native releases.
Why you should migrate to New Architecture?
React Native’s Legacy Architecture is frozen as of 0.81, and new capabilities are landing only in the New Architecture. Migrating now keeps your app compatible with future releases, improves startup performance, and prepares your team for upcoming React features.
Future compatibility
Legacy Architecture is no longer receiving new features, and upcoming versions will eventually remove it completely. Migrating early gives you time to adapt on your terms instead of rushing later.
Future compatibility
Legacy Architecture is no longer receiving new features, and upcoming versions will eventually remove it completely. Migrating early gives you time to adapt on your terms instead of rushing later.
Better performance
The New Architecture enables synchronous layout, concurrent React features, and faster startup with lazily loaded TurboModules. These are only available when the New Architecture is enabled.
Better performance
The New Architecture enables synchronous layout, concurrent React features, and faster startup with lazily loaded TurboModules. These are only available when the New Architecture is enabled.
Simplified codebase
Staying on the legacy stack means relying on patterns that will become harder to maintain over time. A structured migration lets you align the codebase with current best practices.
Simplified codebase
Staying on the legacy stack means relying on patterns that will become harder to maintain over time. A structured migration lets you align the codebase with current best practices.
We migrated a multi-platform OTT application to the New Architecture
We partnered with a global consumer electronics company to migrate their multi-platform React Native application to the New Architecture.
The project covered a full upgrade of the core application, native integrations, and platform-specific code across 10+ platforms, including mobile, web and TV.
450+
Legacy tests rewritten
6
React Native versions upgraded
What can go wrong during a New Architecture migration?
Switching on the New Architecture is not just flipping a flag. It affects libraries, native modules, build tooling, and how your app starts up. Here are the most common issues we help teams avoid in production.
Unsupported components
When you enable the New Architecture, most legacy components render through Interop without changes. The ones that do not resolve correctly show up as red boxes and may need updates.
Interop limits
The Interop Layer lets most legacy components run under the New Architecture, but it is not fully compatible with the old rendering and event system, so inconsistencies can appear.
Performance tradeoffs
Benchmarks show the New Architecture faster in some cases and slower in others, and Meta reports neutral overall performance, so migrations should not assume automatic speed boosts.
Native modules
Legacy native modules that rely on old bridge-specific APIs or run heavy work on the main thread can trigger deadlocks, ANR spikes, or crashes once you switch architecture.
View flattening
Changes in the renderer can break assumptions about view hierarchies, causing gesture issues, invisible views, or ref-based code and end-to-end tests that no longer find the right elements.
Rollout stability
Even with solid preparation, apps can see temporary regressions during rollout, like increased crashes on certain devices, so careful monitoring and phased release are key.
Upgrade to the architecture React Native runs on today
Riccardo Cipolleschi explains how the New Architecture unlocks concurrent rendering, the upcoming Activity component, and priority and low-priority rendering paths, and why these capabilities were enabled by the architectural redesign.
He also notes that the New Architecture is no longer considered new, but simply the architecture of React Native today, reflecting how the framework has moved on from its previous model.
Migrate your React Native app to New Architecture
Migrate to New Architecture
Our engineers handle upgrading React Native to at least 0.81 when necessary, bridgeless configuration, Fabric integration, TurboModule setup, library updates, and regression fixes across iOS, Android, and additional platforms such as tvOS.
Assess your app’s readiness
We audit your codebase, native modules, libraries, and build setup to identify gaps and blockers before migration begins.
Design a phased migration plan
We plan the migration around your roadmap, mapping out required changes, identifying risk areas, and structuring the upgrade into manageable phases.
Unlock full potential of New Architecture
Once on new architecture, your app can now benefit from concurrent React features, such as transitions and suspense for data fetching, which improve perceived performance.
Upskill your team
We train your developers on the New Architecture through pairing, documentation, and focused knowledge-sharing sessions, so your team can own the codebase after the handoff.
Get New Architecture readiness audit and migration roadmap
Why leading companies work with Callstack
Meta Official Partners
We are official Meta partner for React Native, co-organizers of React Conf and hosts of React Universe Conf.
Working at scale
We know how to make React Native work at enterprise scale, both technically and organizationally.
React Native Core Contributors
We don’t just use React Native to build cross-platform apps, we help shape it for millions of developers.
Team at scale
We’re a team of 200+ engineers ready to start fast and scale with your needs.
Enterprise-friendly
We hold ISO certifications and follow strict security standards to make onboarding smooth and compliant.
Wide range of services
As a partner for your full application lifecycle, we offer a full range of services around React and React Native.
FAQs
Migrating to the New Architecture touches libraries, native modules, build tooling, and UI behavior across platforms. These frequently asked questions cover the most important considerations so you know what to expect before starting.
In most cases, yes. The New Architecture depends on changes introduced in recent versions of React Native, so upgrades and migration are usually planned together as one coordinated effort.
Not automatically. The goal of the New Architecture is long-term stability and capability, not guaranteed immediate performance gains.
Parts can be prepared gradually, like updating libraries or introducing TurboModules early. But enabling the New Architecture still requires a controlled cutover with focused stabilization.
We identify required updates, replacements, or interop solutions. In many cases, libraries need small adjustments; others may require temporary forks or alternative implementations.
Modules that rely on legacy bridge behavior or main-thread work often need updates. TurboModules, Fabric components, and Codegen-based types offer cleaner patterns but require some refactoring.
Legacy tests or older renderer assumptions can fail under React 18 and Fabric. Part of the migration includes updating or replacing test helpers to keep coverage reliable.
Timelines vary by app size, dependency footprint, and native complexity. The readiness audit defines the exact scope, risks, and estimated trajectory before any migration begins.
Need help with migrating to New Architecture?
Moving to the New Architecture is a strategic step that sets your app up for the future. If you want expert guidance, a clear migration plan, or support delivering the upgrade safely, our team is here to help.
We’ve helped dozens of teams go cross-platform without rewriting everything. Let's see how we can help you.
