skills.rest
dlptho356
dlptho356COMMUNITY
Explore all skills by this author →
GitHub

prisma-mongodb-upgrade

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

Updated Jun 9, 2026
Search Tags:#migration#orm#mongodb#prisma#cutover#database upgrade#prisma next
One-click install
npx skills add https://github.com/dlptho356/TTTN --skill prisma-mongodb-upgrade-dlptho356
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-mongodb-upgrade
Source: https://github.com/dlptho356/TTTN/tree/main/DATN/backend/.windsurf/skills/prisma-mongodb-upgrade
Command: npx skills add https://github.com/dlptho356/TTTN --skill prisma-mongodb-upgrade-dlptho356

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 Prisma 7 upgrade or silently rewriting the app onto SQL — and frames the real decision: migrate to Prisma Next (Early Access MongoDB support) or deliberately stay on v6. ## 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 line. - Migration Mappings: Reference guides translating v6 schema concepts (@db.ObjectId, composite types, @@map), client API calls ($runCommandRaw, findRaw, $transaction), and the db push workflow into Prisma Next's contract, ORM, raw lane, and plan/migrate/verify/sign lifecycle. - Cutover Verification: A 10-step checklist for a no-data-moves cutover — same database, index parity, validator impact, staged read-only soak, and code-only rollback. - 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 walks the team 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 ORM v7 ships 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. Follow the cutover checklist: confirm MongoDB 8.0+, verify index parity, 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 a user-supplied peer dependency and fully accessible. 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 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 line, keep taking patches, and re-evaluate at Prisma Next GA.

Why does db.orm.User return undefined in Prisma Next?▼

Prisma Next's Mongo ORM is addressed by collection storage names, not model names. Use db.orm.users — the @@map name or lowercased model name — instead of db.orm.User, which is the most common porting mistake from v6.

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
Sambhav242005Sambhav242005

prisma-mongodb-upgrade

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

Community
Advanced
ohmyhotelcoohmyhotelco
1

fm-parity

Runs visual, API contract, WebView bridge, and telemetry parity gates on migrated pages before route flip.

Official
Advanced
firstaxelfirstaxel

prisma-mongodb-upgrade

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

Community
Advanced