Technical variant · Next.js migration
W-Make Batch · Next
W-Make Batch with a new Next.js interface on the same Express/SQLite core. In domain terms it matches the complete operations version.
- My role
- Migration architecture, backend interface and interface modernisation.
- Technology
- Next.js 16 · TypeScript · Node.js · Express · SQLite · Playwright
- Status
- Live · migration in progress
- Who it is for
- The domain rules stay in the backend while the new interface takes over step by step.
Situation
A production system cannot be switched to a new interface on a single date. Postings, roles and shift logic have to keep running throughout.
Next.js therefore sits on the same domain core. Production, stock and calculations are not copied into new browser logic.
Key decisions
- 01
Express and SQLite stay responsible for domain logic, sign-in and data integrity.
- 02
The Next client talks to a defined API and takes over the pages one after another.
- 03
Checks on system health, roles and routes make each migration step traceable.
A look inside
A look at the application.
The instance shows the Next version with demo data. Access is available on request.
The process at a glance.
01
Domain core
Backend, data model and posting rules remain the shared basis.
02
Next client
Working pages are introduced as a typed Next.js interface.
03
Checks
API, role and smoke tests secure the migration.
04
Operations
Its own container and domain keep the variant separate.
What carries over
A migration works when the new interface uses the domain core and does not rebuild it.
Password-protected. Temporary access is available on request.
First call · 30 minutes · free
Tell me where your process gets stuck.
A few sentences about the process are enough: what runs in lists or side calculations today, and who works with it. Within two working days you get a reply and a clear view of whether I am the right person for it.
Arrange a callAssess your own process →