skills.rest
singhaditya73
singhaditya73COMMUNITY
Explore all skills by this author →
Website𝕏@aditya_singh73GitHub

prisma-mongodb-upgrade

Guides Prisma v6 MongoDB projects through migration to Prisma Next or deliberate v6 retention.

Updated Aug 9, 2026
Search Tags:#migration#orm#mongodb#prisma#cutover#database upgrade#prisma next
One-click install
npx skills add https://github.com/singhaditya73/Naviq --skill prisma-mongodb-upgrade-singhaditya73
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-mongodb-upgrade
Source: https://github.com/singhaditya73/Naviq/tree/main/packages/db/.agents/skills/prisma-mongodb-upgrade
Command: npx skills add https://github.com/singhaditya73/Naviq --skill prisma-mongodb-upgrade-singhaditya73

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Prisma ORM v7 ships no MongoDB connector, leaving MongoDB projects on v6 with no standard upgrade path. This Skill prevents the two common failure modes — advising an impossible v7 upgrade or silently rewriting the app onto SQL — and frames the real decision: migrate to Prisma Next (Early Access MongoDB support) or stay on v6 with proper hygiene. ## Core Features & Use Cases - Decision Framework: A blocker-check table (transactions usage, MongoDB server version, tolerance for pre-1.0 breaking changes) that determines whether to migrate to Prisma Next or stay on the latest v6. - Migration Mappings: Detailed references mapping v6 schema concepts (@db.ObjectId, composite types, @@map) to Prisma Next contracts, v6 client calls ($runCommandRaw, findRaw, $transaction) to Next equivalents, and the db push workflow to Next's plan/migrate/verify/sign lifecycle. - Cutover Verification: A 10-step checklist ensuring the migration moves only code, never data — same database, index parity, validator impact, staged read-only soak, and a code-only rollback path. - Use Case: A team on Prisma 6 with provider = "mongodb" asks about upgrading to Prisma 7. The Skill intercepts the impossible request, greps the codebase for $transaction usage, checks the MongoDB server version, and produces a staged migration plan to Prisma Next. ## 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 to Prisma 7 with MongoDB?▼

No. Prisma ORM v7 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 Prisma Next contract describing your existing collections, then run the plan, migrate, verify, and sign lifecycle against the same database — no data moves. Map v6 client calls to Next equivalents and validate everything on a staging copy before cutover.

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 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.

What replaces prisma db push for MongoDB in Prisma Next?▼

Prisma Next gives MongoDB first-class migrations: emit the contract, plan a content-hashed migration package, apply it, verify the live schema, and sign. A db update command remains as the push-style analogue for local prototyping without migration history.

Related Skills

Explore More Software Engineering Skills→
MahdiaMayatiMahdiaMayati

prisma-mongodb-upgrade

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

Community
Advanced
vasuguptadot-jpgvasuguptadot-jpg

prisma-mongodb-upgrade

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

Community
Advanced
nethangabrielbnethangabrielb

prisma-mongodb-upgrade

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

Community
Advanced
team-zerolatencyteam-zerolatency

prisma-mongodb-upgrade

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

Community
Advanced