https://developer.android.com/guide/navigation/navigation-3/skill

Migrating from Navigation 2 to Navigation 3 requires replacing NavController and NavHost patterns with NavDisplay, entryProvider, and persistent back stack constructs. You must update dependencies, model routes with NavKey, and translate state management to the new Navigation 3 APIs.

Migrating to Navigation 3 requires a Compose-only destination app using type-safe routes. You need to support compileSdk 36+ and meet NavKey serialization requirements. The migration is a single atomic process, meaning you must validate these assumptions before proceeding.

Navigation 3 migration has unsupported features and constraints. Pre-migration validation highlights these limitations so you do not proceed incorrectly. You must confirm your app uses Compose-only destinations and type-safe routes to avoid hitting unsupported scenarios.

When migrating to Navigation 3, features like bottom sheets, modularized navigation, ViewModel arguments, and result returning are supported but not directly covered in standard steps. You should use AI Agent prompts to check specific recipes for these features during your migration.

Converting routes and state for Navigation 3 involves modeling your route definitions with NavKey and handling state with Navigation 3 back stacks. You replace existing navigation graph concepts with NavDisplay and entryProvider constructs to manage persistent state.