Does Netlify’s rollback automatically revert external database schema changes?

No, Netlify rollbacks do not revert external database changes

Netlify rollbacks are strictly application-layer operations. When you roll back a deploy, Netlify restores the static assets, serverless functions, and environment variables associated with a previous deploy ID. It has no visibility into, or control over, external data stores. Any schema changes executed by a serverless function or build script during a deployment are permanent side effects that persist regardless of which code version is currently active.

The Gap Between Code and Schema

Because Netlify treats deploys as immutable snapshots of the application but not the infrastructure, a mismatch occurs during a rollback: the code reverts to version A, but the database remains at version B. If version A is not forward-compatible with the schema changes introduced in version B, the application will likely encounter runtime errors or data corruption.

Automation Constraints

Netlify does not currently provide a native "on-rollback" hook or a specific API event that triggers when a user manually reverts a production deploy via the UI. Consequently, you cannot configure Netlify to automatically invoke a "down" migration script from tools like Prisma or TypeORM during a rollback.

Recommended Strategies for Schema Safety

To achieve schema-safe deployments without manual intervention during a crisis, consider these architectural patterns:

• Expand and Contract (Parallel Changes): Instead of modifying existing columns, add new ones. Deploy the code that supports both old and new schemas. Only after the deployment is confirmed stable should you deploy a second change to remove the old columns.
• External Migration Orchestration: Move migration logic out of the Netlify build/deploy pipeline and into a dedicated CI/CD pipeline (e.g., GitHub Actions). This allows you to trigger a specific "rollback" workflow that handles both the Netlify API rollback and the database down-migration in a single coordinated sequence.
• Feature Flags: Wrap new schema-dependent logic in feature flags. If a deploy fails, disable the flag via an external provider rather than rolling back the entire deploy, keeping the code and schema in sync.

Verification

To verify this behavior in your own environment:

1. Deploy a version that adds a column to an external table via a serverless function.
2. Use the Netlify UI to roll back to the previous deploy.
3. Query your database; the column will still exist, confirming that the rollback did not affect the external state.

Diagnostic Detail: Are you currently executing migrations during the build step or via a serverless function triggered after deployment? This distinction determines whether you can use build-plugin hooks to manage the "up" migration, though it does not solve the "down" migration problem.