Work
2024–2025NDAMigrating a long-lived frontend without stopping the product
A staged renewal of a live website, preserving URLs and continuity of the customer journey.
Client under NDA. The problem, the approach and the stack are published; the name and the assets are not.
Role
- Audit
- Migration architecture
- Development
Stack
- Next.js
- TypeScript
Renewal without one big switch
A live website is not a blank canvas: it has users, URLs and search history. The migration needed to replace the technical foundation while preserving that continuity.
Move in manageable parts
The old and new versions ran behind a shared router. Pages moved gradually and the dual-system period had a defined limit. URLs were preserved, while structural changes received permanent redirects prepared before release.
Design the transition itself
The value lies in a manageable transition, as well as the new version. A page becomes a unit that can be reviewed, routed and followed by the next. This allows the product to evolve in stages around existing user journeys.
- Migration
- Legacy
- Incremental rollout