prisma-migration-drift-recovery

Prisma migration drift occurs when your database schema and migration history diverge, often after changes made via direct SQL, Supabase, or another ORM. Correcting this drift safely prevents potential data loss during future migrations.

To baseline an existing database to Prisma migrations without data loss, you use SQL-based baselining and migration history alignment. This workflow safely re-syncs your schema.prisma file with the current database state.

Yes, you can adopt Prisma migrations on databases created with direct SQL or another ORM by establishing a baseline. This process aligns Prisma's migration history with your existing schema to enable safe incremental changes.

You need to use prisma migrate resolve and prisma migrate diff when correcting schema drift and baselining existing databases. They help re-sync schema.prisma with the database and apply incremental changes safely.

Prisma migration history diverges from your database schema when structural changes are made outside Prisma, such as through direct SQL, Supabase, or another ORM. This drift requires baselining to safely re-sync.