Best way to manage Prisma migrations across multiple developers?

[Saif0933]

Discussion Body (Question)

Hi everyone,

I am working on a Node.js + Prisma + PostgreSQL project with multiple developers.

Sometimes one developer creates migrations and pushes them to GitHub, while another developer already has local database changes. This occasionally causes migration conflicts or drift issues.

What is the recommended workflow for managing Prisma migrations in a team environment?

Specifically:

1. Should every schema change create a migration?
2. How should developers sync their local databases?
3. What is the best way to avoid migration drift?
4. How do teams handle production migrations safely?

I would appreciate hearing about real-world workflows and best practices.

Thanks!

Answer

A workflow that works well for many teams is:

1. Every schema change should be committed as a migration.

   Example:
   prisma migrate dev --name add_employee_table

2. Commit both:

   • schema.prisma
   • prisma/migrations folder

   Never commit only the schema file.

3. Before starting work, pull the latest changes and run:

   prisma migrate dev

   This keeps your local database synchronized with the migration history.

4. Avoid manually modifying the database outside Prisma migrations.

   Direct database changes often cause migration drift.

5. For production environments, use:

   prisma migrate deploy

   instead of prisma migrate dev.

6. Keep one shared migration history in Git and make migration reviews part of the pull request process.

This approach helps prevent drift, keeps all environments consistent, and makes deployments more predictable.