Skip to content
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ The risk teams are taking today is gaps in the implementation. This is a bigger

Our own cloud platform API already runs on Prisma 8, so I can say from experience that it's worth it.

For teams already using Prisma 7 on PostgreSQL, I recommend migrating incrementally. Unlike previous versions of Prisma, Prisma 8 and earlier versions can run in parallel against the same database. Queries or execution paths can be switched over one by one and checked to ensure they behave as expected. See the [PostgreSQL upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/postgresql) for more details.
For teams already using Prisma 7 on PostgreSQL, I recommend migrating incrementally. Unlike previous versions of Prisma, Prisma 8 and earlier versions can run in parallel against the same database. Queries or execution paths can be switched over one by one and checked to ensure they behave as expected. See the [PostgreSQL upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/postgresql-incremental) for more details.

Prisma 7 will receive bug fixes and security updates for the next 12 months, so teams that want to wait until they have more confidence can do that too.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ _Every issue on this list started with a developer taking the time to share a pr

Many of the changes in Prisma ORM 8, from TypeScript migrations to the new contract artifact, were shaped by your feedback and discussions on GitHub.

If you tried Prisma before and moved on because of one of these issues, [give Prisma 8 another try](https://www.prisma.io/docs/orm). If you're already on Prisma 7, our [upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/postgresql) will help you make the move.
If you tried Prisma before and moved on because of one of these issues, [give Prisma 8 another try](https://www.prisma.io/docs/orm). If you're already on Prisma 7, our [upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm) will help you make the move.

And if something still doesn't work the way you'd like, [join us on Discord](https://pris.ly/discord), [open a GitHub issue](https://github.com/prisma/orm/issues/new/choose), or upvote an existing one. We use those votes to help prioritize what to build next, and this list shows why your feedback matters.

Expand Down
4 changes: 2 additions & 2 deletions apps/blog/content/blog/prisma-orm-8-nestjs/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -230,7 +230,7 @@ export class PrismaService implements OnModuleDestroy {
}
```

If you are coming from Prisma ORM 7, the [Prisma ORM 7 to 8 upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/postgresql) shows how contracts and the new query APIs fit together, one route at a time.
If you are coming from Prisma ORM 7, the [Prisma ORM 7 to 8 upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/postgresql-incremental) shows how contracts and the new query APIs fit together, one route at a time.

## Deploy the API to Prisma Compute

Expand Down Expand Up @@ -297,7 +297,7 @@ The starter annotates each constructor parameter with `@Inject(PrismaService)` o
Yes, in early access. Scaffold with `npm create prisma@latest -- my-app --template nest --provider mongodb --package-manager pnpm --yes` (plain npm hits an `ERESOLVE` error in the current `create-prisma` release). The scaffold gives you document models in the contract, and the ORM adds a pipeline builder for aggregations and migration plans that create collections and indexes. The Prisma CLI reads `MONGODB_URL` while the dev server reads `DATABASE_URL`, so export both with the same value. Prisma ORM 8 does not run MongoDB transactions yet.
</Accordion>
<Accordion title="How do I move an existing NestJS app from Prisma ORM 7 to Prisma ORM 8?">
The [Prisma ORM 7 to 8 upgrade guide for PostgreSQL](https://www.prisma.io/docs/guides/upgrade-prisma-orm/postgresql) has you install Prisma ORM 8 next to Prisma ORM 7, infer a contract from the existing database, and move queries over one route at a time, with `findMany` and `findFirst` becoming `.all()` and `.first()`. In a NestJS app, replace the service that extends `PrismaClient` with an `@Injectable()` class that holds the shared `db` object and calls query functions from `src/prisma/`.
The [Prisma ORM 7 to 8 upgrade guide for PostgreSQL](https://www.prisma.io/docs/guides/upgrade-prisma-orm/postgresql-incremental) has you install Prisma ORM 8 next to Prisma ORM 7, infer a contract from the existing database, and move queries over one route at a time, with `findMany` and `findFirst` becoming `.all()` and `.first()`. In a NestJS app, replace the service that extends `PrismaClient` with an `@Injectable()` class that holds the shared `db` object and calls query functions from `src/prisma/`.
</Accordion>
</Accordions>

Expand Down
2 changes: 1 addition & 1 deletion apps/docs/content/docs/(index)/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Prisma is a complete TypeScript stack with one workflow: **build** your app and
<IconLink href="/prisma-orm/quickstart/postgresql" title="I'm creating a new app" description="Start from a template" icon={<Rocket />} />
<IconLink href="/prisma-orm/quickstart/existing-app/postgresql" title="I have an app, but no database yet" description="Add Prisma ORM, then create the tables" icon={<FolderPlus />} />
<IconLink href="/prisma-orm/add-to-existing-project/postgresql" title="I have a database already" description="Start from the tables you have" icon={<Database />} />
<IconLink href="/guides/upgrade-prisma-orm/postgresql" title="I have a Prisma 7 app" description="Move to Prisma ORM 8 in steps" icon={<Milestone />} />
<IconLink href="/guides/upgrade-prisma-orm" title="I have a Prisma 6 or 7 app" description="Upgrade to Prisma 8" icon={<Milestone />} />
</IconGrid>

</SectionRow>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ On this page you add Prisma ORM to an app whose PostgreSQL database already has

Your app must reach its PostgreSQL database and run on Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer ([Supported versions](/orm/supported-versions)). Work against a development copy of your database, not production. [Step 9](#9-make-your-first-change-to-the-tables) shows how to apply your changes to production afterwards.

If your database has no tables yet, follow [Add Prisma ORM and PostgreSQL to an existing app](/prisma-orm/quickstart/existing-app/postgresql) instead, which creates the tables for you. If you want Prisma ORM to create a new app for you, follow [Create a new app with PostgreSQL](/prisma-orm/quickstart/postgresql). If your app uses Prisma ORM 7 today, follow [Prisma ORM 7 to 8 (PostgreSQL)](/guides/upgrade-prisma-orm/postgresql).
If your database has no tables yet, follow [Add Prisma ORM and PostgreSQL to an existing app](/prisma-orm/quickstart/existing-app/postgresql) instead, which creates the tables for you. If you want Prisma ORM to create a new app for you, follow [Create a new app with PostgreSQL](/prisma-orm/quickstart/postgresql). If your app uses Prisma ORM 6 or 7 today, follow [Upgrade to Prisma 8](/guides/upgrade-prisma-orm).

:::note[Using Prisma ORM 7?]

Expand Down
2 changes: 1 addition & 1 deletion apps/docs/content/docs/(index)/prisma-orm/from-scratch.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ npm install --save-dev prisma tsx typescript

`temporal-polyfill` is a peer dependency of `@prisma/orm-postgres` too. It adds `Temporal`, the newer JavaScript date and time API, to runtimes such as Node.js 24 that do not have it built in. npm installs it for you, but with Yarn you add it yourself.

The two Prisma packages have different version numbers, for example `prisma` 8.0.0-rc.32 and `@prisma/orm-postgres` 8.0.0-rc.23. That is normal, and any two `latest` versions work together.
The two Prisma packages have different version numbers, for example `prisma` 8.0.0-rc.33 and `@prisma/orm-postgres` 8.0.0-rc.23. That is normal, and any two `latest` versions work together.

## 2. Create the config file and `.env`

Expand Down
4 changes: 2 additions & 2 deletions apps/docs/content/docs/(index)/prisma-orm/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,8 @@ Pick the page that matches where you are starting from:
<Card href="/prisma-orm/add-to-existing-project/postgresql" title="I have a database already" icon={<Database className="text-primary" />}>
Generate the file that holds your models from the tables you have, then make your next schema change.
</Card>
<Card href="/guides/upgrade-prisma-orm/postgresql" title="I have a Prisma 7 app" icon={<Milestone className="text-primary" />}>
Run Prisma ORM 8 next to Prisma ORM 7 in the same app, and move your code over in steps.
<Card href="/guides/upgrade-prisma-orm" title="I have a Prisma 6 or 7 app" icon={<Milestone className="text-primary" />}>
Upgrade in one pass, or run Prisma ORM 7 and Prisma 8 side by side and move one route at a time.
</Card>
</Cards>

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ metaDescription: 'Add Prisma ORM to an app you already have: run orm init, write

This page uses PostgreSQL. [Use MongoDB instead](/prisma-orm/quickstart/existing-app/mongodb).

Use this page when you already have an app and its database has no tables yet. By the end, your app has one model, the database has a table for it, and a script writes and reads a row. You also change the model once and apply the change to the database with a migration. If your database already has tables, follow [Add Prisma ORM to an existing PostgreSQL database](/prisma-orm/add-to-existing-project/postgresql) instead. If your app uses Prisma ORM 7 today, follow [Prisma ORM 7 to 8 (PostgreSQL)](/guides/upgrade-prisma-orm/postgresql).
Use this page when you already have an app and its database has no tables yet. By the end, your app has one model, the database has a table for it, and a script writes and reads a row. You also change the model once and apply the change to the database with a migration. If your database already has tables, follow [Add Prisma ORM to an existing PostgreSQL database](/prisma-orm/add-to-existing-project/postgresql) instead. If your app uses Prisma ORM 6 or 7 today, follow [Upgrade to Prisma 8](/guides/upgrade-prisma-orm).

:::note[Using Prisma ORM 7?]

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"[I'm creating a new app](/prisma-orm/quickstart/postgresql)",
"[I have an app, but no database yet](/prisma-orm/quickstart/existing-app/postgresql)",
"[I have a database already](/prisma-orm/add-to-existing-project/postgresql)",
"[I have a Prisma 7 app](/guides/upgrade-prisma-orm/postgresql)"
"[I have a Prisma 6 or 7 app](/guides/upgrade-prisma-orm)"
],
"hiddenPages": [
"mongodb",
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -312,7 +312,7 @@ rm postgres-to-prisma-postgres.dump postgres-restore.list row-counts.sql source-

## Recommended next step: adopt Prisma ORM

Your database migration is complete, and upgrading Prisma ORM is a separate application change. Prisma ORM 8 is a [release candidate](/orm/release-status); to adopt it, follow the [incremental Prisma ORM 7 to 8 guide](/guides/upgrade-prisma-orm/postgresql) after the application is stable on Prisma Postgres.
Your database migration is complete, and upgrading Prisma ORM is a separate application change. Prisma ORM 8 is a [release candidate](/orm/release-status); to adopt it, follow the [incremental Prisma ORM 7 to 8 guide](/guides/upgrade-prisma-orm/postgresql-incremental) after the application is stable on Prisma Postgres.

If you want to complete both changes on the same day, deploy and verify the Prisma Postgres connection first. Upgrade Prisma ORM in a separate commit or deployment so failures have one clear cause.

Expand Down
2 changes: 1 addition & 1 deletion apps/docs/content/docs/cli/orm-init.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ After you confirm, `orm init`:

It does not write a starter contract, and it changes nothing in `prisma/` or in the database. Prisma ORM 7 keeps owning the schema and its migrations. From now on, `prisma` runs Prisma ORM 8 and `prisma7` runs Prisma ORM 7, so a Prisma ORM 7 command such as `migrate dev` becomes `npx prisma7 migrate dev`. Your application keeps using the Prisma ORM 7 client until you move its routes, one at a time, to the Prisma ORM 8 client in `src/prisma/db.ts`. If the project still uses a Prisma ORM version before 7, so that your `package.json` lists `@prisma/client` below version 7, `orm init` upgrades `@prisma/client` to version 7, because the Prisma ORM 7 CLI it installs needs a client of the same major version. Run `npx prisma7 generate` afterwards to generate the upgraded client.

To finish, set `DATABASE_URL` and run `npx prisma db sign` once. [`db sign`](/cli/db-sign) checks that the database matches the contract and then writes the marker, a row that records which contract the database matches. The row goes in the table `prisma_contract.marker`, which the first `db sign` creates in a PostgreSQL schema of its own named `prisma_contract`, so your own tables do not change. After each Prisma ORM 7 migration, whether you ran `npx prisma7 migrate dev` or `npx prisma7 migrate deploy`, run `npx prisma contract emit` and then `npx prisma db sign` again. [Configuration](/cli/configuration#use-a-prisma-orm-7-schema) explains `prisma7Schema`, and [the upgrade guide](/guides/upgrade-prisma-orm/postgresql) covers the rest of the move.
To finish, set `DATABASE_URL` and run `npx prisma db sign` once. [`db sign`](/cli/db-sign) checks that the database matches the contract and then writes the marker, a row that records which contract the database matches. The row goes in the table `prisma_contract.marker`, which the first `db sign` creates in a PostgreSQL schema of its own named `prisma_contract`, so your own tables do not change. After each Prisma ORM 7 migration, whether you ran `npx prisma7 migrate dev` or `npx prisma7 migrate deploy`, run `npx prisma contract emit` and then `npx prisma db sign` again. [Configuration](/cli/configuration#use-a-prisma-orm-7-schema) explains `prisma7Schema`, and [the upgrade guide](/guides/upgrade-prisma-orm) covers the rest of the move.

## On a Prisma ORM 6 MongoDB project

Expand Down
1 change: 1 addition & 0 deletions apps/docs/content/docs/compute/getting-started.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -149,3 +149,4 @@ To browse and manage the same resources without the CLI, open the [Console](http
- [Deployments](/compute/deployments): inspect, promote, roll back, start, stop.
- [Environment variables](/compute/environment-variables): production, preview, and per-branch overrides.
- [Environments](/compute/branching): how branches isolate work and map to Git.
- [Deploy an existing app](/guides/compute/deploy-existing-app): move a Node.js server already on Prisma 8 onto Compute.
1 change: 1 addition & 0 deletions apps/docs/content/docs/compute/github.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -91,3 +91,4 @@ Uninstalling the app disconnects every repository that was connected through it,
- [Deploy on push](/compute/deploy-on-push): the full walkthrough, from connection to a preview for every pushed branch other than the default one.
- [Environments](/compute/branching): how platform branches map to Git.
- [Environment variables](/compute/environment-variables): per-branch config for previews.
- [Deploy an existing app](/guides/compute/deploy-existing-app): move a Node.js server already on Prisma 8 onto Compute.
Loading
Loading