prisma-mongodb-upgrade

Guides Prisma v6 MongoDB projects through migration decisions and cutover to Prisma Next.

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

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, which ships no MongoDB connector, leaving teams without clear guidance on whether to migrate to Prisma Next or stay on v6. ## Core Features & Use Cases - Decision Framework: Provides a blocker-based decision table for choosing between migrating to Prisma Next (Early Access MongoDB support) or deliberately staying on the latest Prisma v6. - API and Schema Mapping: Maps v6 client calls, raw queries, transactions, and schema concepts (ObjectId, composite types, storage names) to their Prisma Next equivalents. - Verified Cutover Checklist: Supplies a no-data-moves verification checklist covering index parity, validator impact, transaction inventory, and staged rollback. - Use Case: A team on Prisma 6 with provider = "mongodb" asks about upgrading to Prisma 7; the Skill explains v7 is impossible, checks the codebase for $transaction usage, and walks them through a staged Prisma Next migration. ## Quick Start Ask the assistant to evaluate whether your Prisma v6 MongoDB project should migrate to Prisma Next and to run the cutover verification checklist.

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 Next contract describing your existing collections, then run the plan, migrate, verify, and sign flow against the same database with no data movement. Map v6 client calls to Next equivalents, replace $transaction with mongodb driver sessions, and follow the staged cutover checklist.

Does Prisma Next support MongoDB transactions?

The Prisma Next Mongo façade does not wrap db.transaction yet, but the underlying mongodb driver is directly available as a peer dependency. Multi-document atomicity works today via driver sessions using startSession and withTransaction on a replica set.

What MongoDB version does Prisma Next require?

Prisma Next's Mongo target requires MongoDB server 8.0 or later and mongodb@^7 installed as a user-supplied peer dependency. Prisma v6 tolerated older server versions, so verify your 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, or when your team cannot absorb pre-1.0 breaking changes between Next minors. Pin the latest 6.x, keep taking patches, and re-evaluate at Prisma Next GA.