Migrating to Navigation 3 sounds straightforward until you try to ship it in a real production app. In this talk, I'll share what it actually took to migrate an Android app with 170+ screens to Nav3 manually, under tight timelines, and with real users in production. This is not a polished success story. It's a practical breakdown of what worked, what didn't, and what had to be fixed after release. What I'll cover: Manual migration of 170+ screens: No automation, no AI tools, just screen-by-screen migration. What this process looked like in reality, and where it became painful. Deep links during migration : How existing deep link flows behaved with Nav3 and what needed to be adjusted to keep everything working. Bottom sheets as navigation destinations: Nav3 doesn't handle bottom sheets the way Nav2 did. I'll show what broke, why, and the workaround we shipped to keep them working without a full redesign. Production reality: The stabilization phase after release: unexpected issues, debugging under pressure, and shipping a hotfix to fix critical problems. This talk is for Android engineers who are planning a real migration, not just experimenting, but shipping Navigation 3 in production.