Upgrade a Prisma 6 project to Prisma 7
Paste your schema.prisma and the code that creates PrismaClient. Your browser lists every Prisma 7 breaking change that applies, with the line to fix, and drafts the v7 files - free, and nothing is uploaded. A paid run audits the upgrade into an ordered plan or rewrites your files, and the page checks them again.
The examples replay saved model runs - the whole page, free.
Your recent runs
What this does, and what it does not
Prisma ORM 7 changes how a project is wired more than how it queries. The client generator
becomes prisma-client with a required output; connection URLs leave
schema.prisma for prisma.config.ts; every SQL database needs a driver adapter;
.env is no longer loaded for you; $use middleware, metrics and
Prisma.validator are gone; migrate dev no longer generates or seeds; and
MongoDB has no Prisma 7 connector at all. The page checks your files for each of these, points
at the line, and writes the mechanical part of the new files itself.
The rules come from the agent skill
@prisma/prisma-upgrade-v7
(prisma/skills, MIT), checked against Prisma's
v7 upgrade guide,
the Prisma Config reference
and the published 7.10.0 packages on 2026-09-28. Where they differ the page follows the official
docs and says so - for example, Prisma Config v7 has no directUrl. It sees only what
you paste; it cannot run your migrations or your tests. See the notice.
Independent tool, not affiliated with or endorsed by Prisma Data, Inc. Prisma is a trademark of Prisma Data, Inc.