prisma-mongodb-upgrade

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

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/AlvaroCG123/BancoAtividade --skill prisma-mongodb-upgrade-alvarocg123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-mongodb-upgrade
Source: https://github.com/AlvaroCG123/BancoAtividade/tree/main/AtividadeBanco/.windsurf/skills/prisma-mongodb-upgrade
Command: npx skills add https://github.com/AlvaroCG123/BancoAtividade --skill prisma-mongodb-upgrade-alvarocg123

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: Evaluates blockers like $transaction usage, MongoDB server version, and tolerance for pre-1.0 breaking changes to recommend migrating to Prisma Next or staying on v6. - API and Schema Mapping: Maps v6 client calls, raw queries, schema attributes, and composite types to Prisma Next contract and ORM equivalents. - Cutover Verification: Provides a checklist for migrating code against the same database with index parity, validator impact checks, and staged rollback. - 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 Prisma v6 maintenance line.

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

Author a Prisma Next contract describing existing collections, map v6 client calls to Next ORM and mongoRaw equivalents, and run plan, migrate, verify, and sign against the same database. The data never moves; only the client code and workflow change.

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 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 check the server version before planning a migration.

When should I stay on Prisma v6 instead of migrating?▼

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