prisma-mongodb-upgrade

Guides Prisma v6 MongoDB projects through migration to Prisma Next or staying on v6.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/jpmartirez/kilatis --skill prisma-mongodb-upgrade-jpmartirez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-mongodb-upgrade
Source: https://github.com/jpmartirez/kilatis/tree/main/frontend/.windsurf/skills/prisma-mongodb-upgrade
Command: npx skills add https://github.com/jpmartirez/kilatis --skill prisma-mongodb-upgrade-jpmartirez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? MongoDB projects on Prisma v6 have no upgrade path to Prisma 7, since v7 ships no MongoDB connector. This Skill prevents the two common failure modes — advising an impossible v7 upgrade or silently rewriting the app onto SQL — and frames the real decision: migrate to Prisma Next (Early Access MongoDB support) or deliberately stay on v6. ## Core Features & Use Cases - Decision Framework: A blocker-check table (transactions usage, MongoDB server version, tolerance for pre-1.0 breaking changes) that determines whether to migrate to Prisma Next or stay on the latest v6 line. - Migration Mappings: Reference guides translating v6 schema concepts (@db.ObjectId, composite types, @@map), client API calls ($runCommandRaw, findRaw, $transaction), and the db push workflow into Prisma Next's contract, client, and plan/migrate/verify/sign lifecycle. - Cutover Verification: A no-data-moves checklist covering index parity, validator impact, storage-name addressing, and staged read-only soak before switching writes. - Use Case: A team on Prisma 6 with provider = "mongodb" asks about upgrading to Prisma 7. The Skill intercepts the question, greps the codebase for $transaction, checks the MongoDB server version, and produces a concrete migrate-or-stay plan. ## Quick Start Ask the assistant whether your Prisma 6 MongoDB project should upgrade to Prisma 7 and have it check your codebase for migration blockers.

Frequently Asked Questions about prisma-mongodb-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Can I upgrade Prisma 6 MongoDB to Prisma 7?

No. Prisma 7 has no MongoDB connector, so v6 is the terminal classic-ORM major for MongoDB projects. The forward path is Prisma Next, where MongoDB support is in Early Access with GA planned after Postgres.

How do I migrate a Prisma MongoDB project to Prisma Next?

Author a Prisma Next contract describing your existing collections, then run the plan, migrate, verify, and sign lifecycle against the same database — no data moves. Check for blockers first: grep for $transaction usage and confirm the server runs MongoDB 8.0+.

Does Prisma Next support MongoDB transactions?

The Prisma Next Mongo façade does not wrap db.transaction yet, but the underlying mongodb driver is a user-supplied peer dependency and fully accessible. Multi-document atomicity works today via driver sessions using client.startSession() and session.withTransaction() on a replica set.

What MongoDB server version does Prisma Next require?

Prisma Next's Mongo target requires MongoDB 8.0 or later and mongodb@^7 installed as a user-supplied peer dependency. Prisma v6 tolerated older server versions, so verify the server version before planning a migration.

When should I stay on Prisma v6 instead of migrating?

Stay on v6 when your codebase relies on multi-document $transaction calls you cannot port to driver sessions yet, or when your team cannot absorb pre-1.0 breaking changes between Prisma Next minors. Pin the latest 6.x, keep taking patches, and re-evaluate at GA.

Does Prisma Next support Prisma Migrate for MongoDB?

Yes. Unlike v6, where MongoDB only had db push, Prisma Next gives MongoDB first-class contract-driven migrations with plan, migrate, verify, and sign steps, plus Mongo-specific operations like createCollection, setValidation, and createIndex.