Preparing the next view without exposing private workflow data.
Database engineering · Phased project
Migrate customer identifiers without breaking old clients
A fictional support platform stores a mutable external account code as its primary relationship key. Renames and imports now break references in several tables.
Practice brief · Version 5
Project scope
10 tickets / 3 phases
Total focused work estimate
32h + setup
Suggested stack
PostgreSQL · Prisma · TypeScript
Recommended next step
Start with AMIGRATE-101
Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
Practice migration ordering, compatibility and referential integrity.
What the team gains
Review a reversible schema transition with measurable completeness checks.
Before you start
Create a disposable database with synthetic customers and dependent records.
Apply real migration files; never use production db push.
Delivery agreement
Ten scoped tickets across three phases. Build a synthetic local service or select a ticket after recreating its prerequisites; estimates exclude setup.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.