← ClaudeAtlas

prisma-mongodb-upgradelisted

Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when "upgrade to prisma 7" comes up in a project with provider = "mongodb", or when evaluating a move to Prisma Next. Triggers on "upgrade prisma mongodb", "prisma 7 mongodb", "mongodb prisma migration", "prisma next mongodb".
nateruze/ghost_ai · ★ 0 · API & Backend · score 65
Install: claude install-skill nateruze/ghost_ai
# 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 Next](https://github.com/prisma/prisma-next), where MongoDB support is in Early Access with GA planned after Postgres. This skill frames the real decision — migrate to Prisma Next (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 | Version | MongoDB status | |---------|----------------| | Prisma ORM v6 | Fully supported (`mongodb` provider); latest 6.x is the current stable path; maintenance line | | Prisma ORM v7 | **No MongoDB connector — not an option, ever** | | Prisma Next | MongoDB support in **Early Access**, actively developed, GA planned after Postgres — the successor path for MongoDB projects | ## The decision, up front **Migrating to Prisma Next is the encouraged path.** MongoDB support in Prisma Next is Early Access: functional and moving quickly, with GA planned after Postgres — and the Pr