Prisma MongoDB Upgrade Path

Prisma MongoDB Upgrade Path

MongoDB projects are the one Prisma cohort with no road into Prisma 7: v6 is the terminal classic-ORM major for MongoDB, and v7 never ships a MongoDB connector. The successor path is Prisma 8, where MongoDB support is in Early Access while PostgreSQL is a release candidate. The official Prisma ORM 6 to 8 (MongoDB) guide is the source of truth for the migration steps. This skill frames the real decision — migrate to Prisma 8 (the encouraged path), or stay on v6 where a hard blocker applies — and carries the migration mechanics.

Never do either of these:

• Never advise a MongoDB project to "upgrade to Prisma 7". The connector does not exist there. The prisma-upgrade-v7 guide does not apply to MongoDB projects.
• Never solve the version question by rewriting the app onto a SQL database. Changing the database engine is a separate, much larger decision that is not yours to make implicitly.

The version landscape

The decision, up front

Migrating to Prisma 8 is the encouraged path. MongoDB support in Prisma 8 is Early Access: functional and moving quickly — and the Prisma team wants MongoDB users to migrate early and share feedback. The migration mechanics are detailed in the references.

Staying on the latest v6 remains a legitimate choice where a hard blocker applies — stated plainly: Prisma 8 has no MongoDB transaction method yet (multi-document writes use the mongodb driver's sessions directly), and MongoDB behavior can still change between Prisma 8 release candidates.

Decision table

Note: this section will be updated when Prisma 8 adds a MongoDB transaction method.

If staying on v6: hygiene (a deliberate stay, not neglect)

• Pin the Prisma packages to the latest 6.x line and keep taking 6.x patch releases.
• Track Prisma release notes and security advisories for the 6.x line.
• Keep the classic v6 MongoDB setup: url = env("DATABASE_URL") in the schema, db push workflow, no SQL driver adapters (see prisma-orm-setup for the v6 MongoDB shape).
• Re-evaluate when Prisma 8's MongoDB support leaves Early Access, or when the blockers are resolved.

Reference files

Verified against

Prisma 8 claims in this skill were checked against the Prisma ORM 6 to 8 (MongoDB) guide, written for @prisma/​orm-mongo 8.0.0-rc.13, and the prisma-8 skill in prisma/​orm at commit 75c1460515fa2f11971533f6a1dec5dab35d4123. MongoDB support still changes between release candidates: before acting on any Prisma 8 claim, check the installed version (npm ls @prisma/​orm-mongo) and its synced prisma-8 skill.

Prisma 8 on MongoDB requires Node.js 22.18+ (24.11+ on the 24 line; 24 recommended), TypeScript 5.9+, MongoDB 8.0+, and mongodb@7 as a peer dependency. The mongodb@7 driver no longer accepts AWS credentials in the connection string.

Hand-off rule

This skill is the discovery bridge, not a replacement for Prisma 8's own documentation. After a project switches to Prisma 8, run prisma skills sync, read the synced prisma-8/​SKILL.md, and follow it for day-to-day work — do not keep working from this skill's summaries.