prisma-mongodb-upgrade

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

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/samu412/Development_kisan_basket --skill prisma-mongodb-upgrade-samu412
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-mongodb-upgrade
Source: https://github.com/samu412/Development_kisan_basket/tree/main/category_kisan_basket/.agents/skills/prisma-mongodb-upgrade
Command: npx skills add https://github.com/samu412/Development_kisan_basket --skill prisma-mongodb-upgrade-samu412

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 decision table and blocker checks (transactions usage, MongoDB server version, pre-1.0 tolerance) to choose between migrating to Prisma Next or deliberately staying on v6. - Migration Mappings: Maps v6 schema concepts, client API calls, raw queries, and the db push workflow to Prisma Next contract, ORM, and migration equivalents. - Cutover Verification: Supplies a no-data-moves checklist covering index parity, validator impact, storage-name addressing, and staged read-only soak before cutover. - 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 check the 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 upgrading a MongoDB project to Prisma 7 is impossible. Prisma v6 is the terminal classic-ORM major for MongoDB, and the successor path is Prisma Next, where MongoDB support is in Early Access.

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

Author a Prisma Next contract describing your existing collections, then run the plan, migrate, verify, and sign flow against the same database with no data movement. Follow the cutover checklist: confirm MongoDB 8.0+, verify index parity, audit storage-name addressing, and run a staged read-only soak before switching writes.

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 user-supplied peer dependency. 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 MongoDB server versions, so check your server version before planning a migration.

When should I stay on Prisma v6 instead of migrating to Prisma Next?

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