prisma-mongodb-upgrade

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

7|2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/ysfcl/GeoMorphosis --skill prisma-mongodb-upgrade-ysfcl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-mongodb-upgrade
Source: https://github.com/ysfcl/GeoMorphosis/tree/main/.windsurf/skills/prisma-mongodb-upgrade
Command: npx skills add https://github.com/ysfcl/GeoMorphosis --skill prisma-mongodb-upgrade-ysfcl

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-check decision table covering $transaction usage, MongoDB 8.0+ server requirements, and pre-1.0 breaking-change tolerance to choose between migrating to Prisma Next or staying on v6. - Migration Mappings: Maps v6 schema concepts, client API calls ($runCommandRaw, findRaw, aggregateRaw, $transaction), and the db push workflow to Prisma Next contract, mongoRaw lane, and plan/migrate/verify/sign 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 asks whether to upgrade their Prisma 6 MongoDB app to Prisma 7; the Skill explains v7 is impossible, greps the codebase for $transaction blockers, 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 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 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; both stacks read the same database until cutover is verified.

Does Prisma Next support MongoDB transactions?▼

The Prisma Next Mongo client facade 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 the latest 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 minors. Pin to the latest 6.x line and keep taking patch releases.

What replaces $runCommandRaw and aggregateRaw in Prisma Next?▼

The v6 raw method names do not exist in Prisma Next. Use the mongoRaw lane for raw collection operations like aggregate and insertOne, the typed aggregation-pipeline builder for grouping, or the mongodb driver directly for arbitrary database commands.