Migration rollback
Also called rollback, down migration, schema rollback.
A migrationA migration is a controlled change in the structure or location of data or content. rollback undoes a change to how stored data is structured, or records that a failed change was undone.
Example
A migrationA migration is a controlled change in the structure or location of data or content. added a notes column and filled it. Rolling that change back removes the column. Notes that lived only in that column are gone. The history keeps a record that the column was added and then removed.
Why it matters
Prisma's migrateA migration is a controlled change in the structure or location of data or content. docs call a down migration a migration rollback: a script that reverses the schema change in the matching up migration. They separate two situations. If the migration failed partway, that down script can put the schema back and the history can record that the migration was rolled back. If the migration already succeeded, undoing it means a new migration that changes the schema back. Erasing the old step from the story is not the same thing.
A rollback can drop a column, and values that lived only in that column go away. Wiping the whole databaseA database is an organized collection of data that software can store, search, and update. and replaying every migrationA migration is a controlled change in the structure or location of data or content. is a different operation, and it deletes the data.
How it shows up on bot.ski
On bot.ski, databaseA database is an organized collection of data that software can store, search, and update. changes are stored as Prisma migrationA migration is a controlled change in the structure or location of data or content. files in the project. This page does not run a migration, and reading it does not change the database. A rollback is a deliberate database change. It is separate from deploying the website.
Common confusion
A migrationA migration is a controlled change in the structure or location of data or content. rollback is not a deployTo deploy is to make a version of software available where it can run or be served, such as a preview, a test system, or production., and it is not an undo button on a public page. A migration that already succeeded is undone by a further migration. Marking a failed migration as rolled back records the history. It does not by itself restore data that was dropped.
Sources
Updated October 2, 2026.