SkillsAdd

prisma/skills · Official

prisma-mongodb-upgrade

Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7.

All-time #211 Trending #124 Hot #6755 First seen Jul 6, 2026
8-week activity · all time api

Installation

$ npx skills add prisma/skills --skill prisma-mongodb-upgrade
View on skills.sh ↗ GitHub repository ↗

Summary

  • Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7.
  • Use when a MongoDB project asks about upgrading Prisma, when "upgrade to prisma 7" comes up in a project with provider = "mongodb", or when evaluating a move to Prisma Next.
  • Triggers on "upgrade prisma mongodb", "prisma 7 mongodb", "mongodb prisma migration", "prisma next mongodb".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
better-auth-best-practices Shared topics
better-auth/skills 106K installs
mongodb-query-optimizer Similar name
mongodb/agent-skills

>- Help with MongoDB query optimization and indexing. Use only when the user asks for optimizat…

4.9K installs
mongodb-schema-design Similar name
mongodb/agent-skills

MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing sch…

4.9K installs
mongodb-connection Similar name
mongodb/agent-skills

Optimize MongoDB client connection configuration (pools, timeouts, patterns) for any supported …

4.2K installs
mongodb-search-and-ai Similar name
mongodb/agent-skills

Guides MongoDB users through implementing and optimizing Atlas Search (full-text), Vector Searc…

3.9K installs

Security audits

Partner security reviews for this skill.

agent-trust-hub SAFE

Analyzed Jul 10, 2026

The skill provides a legitimate technical migration guide for Prisma ORM MongoDB users moving from version 6 to Prisma Next. It contains architectural advice, API mapping, and safety checklists. All external references point to official Prisma resources and established package registries.

snyk LOW

Analyzed Jul 10, 2026

No issues detected.

socket Score 0.9000 · 0 alerts

Analyzed Jul 10, 2026

  • license 1
  • maintenance 1
  • quality 0.9
  • supply chain 1
  • vulnerability 1

0 alerts

Also in this package

Other skills from prisma/skills.

npx skills add prisma/skills
prisma-database-setup 269.8K prisma-client-api 269.3K prisma-cli 267K prisma-postgres 263K prisma-driver-adapter-implementation 258.3K prisma-upgrade-v7 258.1K prisma-postgres-setup 257.4K prisma-compute 253.4K

Browse all from prisma/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 56
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.0
LicenseMIT
More metadata
author
prisma
version
0.1.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,386 B
  • docs SUMMARY.md 414 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 253,633 installs

SKILL.md

Prisma MongoDB Upgrade Path

MongoDB projects are the one Prisma cohort with no road into Prisma 7: v6 is the terminal classic-ORM major for MongoDB, and v7 never ships a MongoDB connector. The successor path is Prisma Next, where MongoDB support is in Early Access with GA planned after Postgres. This skill frames the real decision — migrate to Prisma Next (the encouraged path), or stay on v6 where a hard blocker applies — and carries the migration mechanics.

Never do either of these:

  • Never advise a MongoDB project to "upgrade to Prisma 7". The connector does not exist

there. The prisma-upgrade-v7 guide does not apply to MongoDB projects.

  • Never solve the version question by rewriting the app onto a SQL database. Changing the

database engine is a separate, much larger decision that is not yours to make implicitly.

The version landscape

Version MongoDB status
Prisma ORM v6 Fully supported (mongodb provider); latest 6.x is the current stable path; maintenance line
Prisma ORM v7 No MongoDB connector — not an option, ever
Prisma Next MongoDB support in Early Access, actively developed, GA planned after Postgres — the successor path for MongoDB projects

The decision, up front

Migrating to Prisma Next is the encouraged path. MongoDB support in Prisma Next is Early Access: functional and moving quickly, with GA planned after Postgres — and the Prisma team wants MongoDB users to migrate early and share feedback. The migration mechanics are detailed in the references.

Staying on the latest v6 remains a legitimate choice where a hard blocker applies — stated plainly: the Next Mongo façade does not wrap transactions yet (the underlying driver is available directly; this is expected to change soon), and pre-1.0 minors can carry breaking changes with published upgrade recipes.

Decision table

Signal Direction
No blockers below apply Migrate to Next; run the verify-cutover-checklist and share feedback with the Prisma team
Greenfield / prototype / internal tool Migrate to Next
Codebase uses multi-document transactions ($transaction) — check with grep, do not ask Plan raw-driver session equivalents first (see client-api-mapping), or stay on v6 until the façade wrapper lands
Team cannot absorb pre-1.0 breaking upgrades between minors Stay on v6 until GA
Risk-averse but interested Run a staged Next round-trip on a copy (see verify-cutover-checklist), then migrate

Note: the transactions gap is expected to close soon — this section will be updated when façade transactions merge in Prisma Next.

If staying on v6: hygiene (a deliberate stay, not neglect)

  • Pin the Prisma packages to the latest 6.x line and keep taking 6.x patch releases.
  • Track Prisma release notes and security advisories for the 6.x line.
  • Keep the classic v6 MongoDB setup: url = env("DATABASE_URL") in the schema, db push

workflow, no SQL driver adapters (see prisma-database-setup for the v6 MongoDB shape).

  • Re-evaluate when Prisma Next's MongoDB is GA, or when blockers for trying EA are resolved.

Reference files

Reference What it covers
references/decision-stay-or-migrate.md The full decision framing, blocker checks, and stay-hygiene detail
references/schema-contract-mapping.md v6 schema (mongodb provider, @db.ObjectId, composite types) → Next contract concepts
references/client-api-mapping.md v6 client calls → Next equivalents, incl. raw escape hatches and transactions — names map, parity does not
references/migrations-mapping.md v6 db push-only story → Next's plan/migrate/verify/sign flow
references/verify-cutover-checklist.md No-data-moves verification: same DB, index parity, staged round-trip before cutover

Verified against

Behavioral claims about Prisma Next in this skill were verified against prisma/prisma-next at commit a2791c5dd59d579b4b3052942ae7f8fe5e2ee852 (pre-1.0, ~v0.14/0.15 line). Prisma Next moves quickly in Early Access: before acting on any Next-side claim, verify it against the version actually installed (check the project's @prisma-next/* versions and the prisma-next skills installed with it). Next's Mongo target requires MongoDB 8.0+ and expects mongodb@^7 as a user-supplied peer dependency.

Hand-off rule

This skill is the discovery bridge, not a replacement for Prisma Next's own documentation. After a project switches to Prisma Next, run Prisma Next's init/skill installation and follow its own skills (quickstart, contract, queries, migrations, runtime) for day-to-day work — do not keep working from this skill's summaries.