Labsco
prisma logo

prisma-upgrade-v7

✓ Official43

by prisma · part of prisma/skills

Complete migration guide for upgrading Prisma ORM from v6 to v7 with ESM, driver adapters, and new configuration. Covers seven critical rule categories: schema migration, driver adapters, ESM support, configuration, removed features, and Accelerate-specific changes Requires Node.js 20.19.0+ and TypeScript 5.4.0+; MongoDB not yet supported in v7 Breaking changes include ESM-only modules, required driver adapters, explicit output paths, and prisma.config.ts configuration Provides step-by-step...

🔥🔥🔥🔥✓ VerifiedFreeQuick setup
🧩 One of 7 skills in the prisma/skills package — works on its own, and pairs well with its siblings.

Complete migration guide for upgrading Prisma ORM from v6 to v7 with ESM, driver adapters, and new configuration. Covers seven critical rule categories: schema migration, driver adapters, ESM support, configuration, removed features, and Accelerate-specific changes Requires Node.js 20.19.0+ and TypeScript 5.4.0+; MongoDB not yet supported in v7 Breaking changes include ESM-only modules, required driver adapters, explicit output paths, and prisma.config.ts configuration Provides step-by-step...

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.


name: prisma-upgrade-v7 description: Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required". license: MIT metadata: author: prisma version: "7.6.0"

Upgrade to Prisma ORM 7

Complete guide for migrating from Prisma ORM v6 to v7. This upgrade introduces significant breaking changes around the new prisma-client generator, driver adapters, prisma.config.ts, explicit environment loading, and generated client entrypoints.

When to Apply

Reference this skill when:

  • Upgrading from Prisma v6 to v7
  • Updating to the prisma-client generator
  • Setting up driver adapters
  • Configuring prisma.config.ts
  • Fixing import errors after upgrade

Rule Categories by Priority

PriorityCategoryImpactPrefix
1Schema MigrationCRITICALschema-changes
2Database ConnectivityCRITICALdriver-adapters
3Module SystemCRITICALesm-support
4Config and EnvHIGHprisma-config, env-variables
5Removed FeaturesHIGHremoved-features
6AccelerateHIGHaccelerate-users

Quick Reference

  • schema-changes - generator migration, required output paths, generated entrypoints, and Prisma.validator replacement
  • driver-adapters - required adapter installation for SQL providers, pool differences, and Prisma Postgres adapter choices
  • esm-support - ESM-first setup plus CommonJS fallback with moduleFormat = "cjs"
  • prisma-config - creating and using prisma.config.ts
  • env-variables - explicit environment loading
  • removed-features - removed middleware, metrics, and legacy CLI behavior
  • accelerate-users - migration notes for Accelerate users

Important Notes

  • MongoDB projects should stay on Prisma 6.x - do not migrate MongoDB apps to Prisma 7's SQL client path
  • Node.js 20.19.0+ required
  • TypeScript 5.4.0+ required
  • Latest stable Prisma ORM version: 7.6.0

Upgrade Steps Overview

  1. Update packages to v7
  2. Choose your module format (esm by default, cjs if needed)
  3. Update TypeScript configuration
  4. Update the schema generator block
  5. Create prisma.config.ts
  6. Install and configure a driver adapter for SQL providers
  7. Update Prisma Client imports
  8. Update client instantiation
  9. Replace deprecated helper patterns like Prisma.validator
  10. Run prisma generate and test

Quick Upgrade Commands

Copy & paste — that's it
# Update packages
npm install @prisma/client@7
npm install -D prisma@7

# Install a driver adapter (PostgreSQL or Prisma Postgres via direct TCP)
npm install @prisma/adapter-pg pg

# Install dotenv for env loading
npm install dotenv

# Regenerate client
npx prisma generate

Breaking Changes Summary

Changev6v7
Module formatImplicit / mixedESM-first, moduleFormat = "cjs" supported
Generator providerprisma-client-jsprisma-client is the default, while prisma-client-js still exists for legacy setups
Output pathAuto (node_modules)Required explicit
Driver adaptersOptionalRequired for SQL providers
Config file.env + schemaprisma.config.ts
Env loadingAutomaticManual (dotenv)
Generated entrypointsSingle package exportclient, browser, models, enums entrypoints
Type-safe query fragmentsPrisma.validator()TypeScript satisfies
Middleware$use()Client Extensions
MetricsPreview featureRemoved

Rule Files

Detailed migration guides for each breaking change:

Copy & paste — that's it
references/esm-support.md        - ESM and CommonJS configuration
references/schema-changes.md     - Generator, output, imports, and generated entrypoints
references/driver-adapters.md    - Required driver adapter setup
references/prisma-config.md      - New configuration file
references/env-variables.md      - Environment variable loading
references/removed-features.md   - Middleware, metrics, and CLI flags
references/accelerate-users.md   - Special handling for Accelerate

Step-by-Step Migration

1. Update package.json for ESM-first projects

Copy & paste — that's it
{
  "type": "module"
}

If you need to stay on CommonJS, keep your app as CJS and set moduleFormat = "cjs" in the generator block instead of forcing ESM.

2. Update tsconfig.json

Copy & paste — that's it
{
  "compilerOptions": {
    "module": "ESNext",
    "moduleResolution": "bundler",
    "target": "ES2023",
    "strict": true,
    "esModuleInterop": true
  }
}

3. Update schema.prisma

Copy & paste — that's it
// Before (v6)
generator client {
  provider = "prisma-client-js"
}

// After (v7)
generator client {
  provider = "prisma-client"
  output   = "../generated/prisma"
  // Optional if you need CommonJS:
  // moduleFormat = "cjs"
}

4. Create prisma.config.ts

Copy & paste — that's it
import 'dotenv/config'
import { defineConfig, env } from 'prisma/config'

export default defineConfig({
  schema: 'prisma/schema.prisma',
  migrations: {
    path: 'prisma/migrations',
  },
  datasource: {
    url: env('DATABASE_URL'),
  },
})

5. Install a driver adapter (SQL providers only)

Copy & paste — that's it
# PostgreSQL
npm install @prisma/adapter-pg pg

# MySQL
npm install @prisma/adapter-mariadb mariadb

# SQLite
npm install @prisma/adapter-better-sqlite3 better-sqlite3

# Prisma Postgres in standard Node.js apps (recommended)
npm install @prisma/adapter-pg pg

# Prisma Postgres serverless driver (edge/serverless)
npm install @prisma/adapter-ppg @prisma/ppg

# Neon
npm install @prisma/adapter-neon

MongoDB does not have a SQL @prisma/adapter-* package in the published Prisma 7.6.0 packages. If you're upgrading a MongoDB project, stop and keep that project on the latest Prisma 6.x release instead of following the standard Prisma 7 migration path.

6. Update client instantiation

Copy & paste — that's it
// Before (v6)
import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

// After (v7)
import { PrismaClient } from '../generated/prisma/client'
import { PrismaPg } from '@prisma/adapter-pg'

const adapter = new PrismaPg({
  connectionString: process.env.DATABASE_URL
})

const prisma = new PrismaClient({ adapter })

7. Replace Prisma.validator with satisfies

Copy & paste — that's it
import { Prisma } from '../generated/prisma/client'

const userSelect = {
  id: true,
  email: true,
  name: true,
} satisfies Prisma.UserSelect

8. Run migrations and generate

Copy & paste — that's it
npx prisma generate
npx prisma migrate dev  # if needed

Resources