prisma-mongodb-upgrade

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

1|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/Sima-Malla/Digital_Menu --skill prisma-mongodb-upgrade-sima-malla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-mongodb-upgrade
Source: https://github.com/Sima-Malla/Digital_Menu/tree/main/my-app/.windsurf/skills/prisma-mongodb-upgrade
Command: npx skills add https://github.com/Sima-Malla/Digital_Menu --skill prisma-mongodb-upgrade-sima-malla

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 because v7 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 covering transaction usage, MongoDB server version, and tolerance for pre-1.0 breaking changes. - Migration Mappings: Maps v6 schema concepts, client API calls, and the db push workflow to Prisma Next contracts, ORM calls, and the plan/migrate/verify/sign lifecycle. - Cutover Verification: Supplies a no-data-moves checklist covering index parity, validator impact, storage-name addressing, and staged read-only soak testing. - Use Case: A team on Prisma 6 with 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 from v6 is impossible. The forward path is Prisma Next, where MongoDB support is in Early Access, or staying on the latest v6 maintenance line.

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 a staging copy. The data never moves; only the client and workflow change, with v6 kept runnable until cutover is verified.

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 with startSession and 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 check 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 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, keep taking patches, and re-evaluate at GA.