A step-by-step checklist for migrating a Prisma project from local development (Docker Postgres or `prisma dev`) to hosted Prisma Postgres in production. Covers five key steps: local setup with `prisma dev` or Docker, creating the hosted database via Prisma Console, updating environment variables and config with pooled vs. direct connection strings, moving schema and data (fresh deploy with `migrate deploy` or full data copy via `pg_dump`/`pg_restore`), and validating with migration status checks, row counts, and smoke tests. Highlights the difference between pooled and direct connection strings, PgBouncer transaction mode limitations, and how to keep the local development loop intact after deployment.
Table of contents
The local-to-production gapStart local: prisma dev or DockerCreate the hosted databaseUpdate env and configMove the schema and the dataValidate, then deployFrequently asked questionsRecap328 Impressions