How to fix P1014: The underlying model does not exist in Prisma

PrismaINTERMEDIATEHIGHUpdated Dec 22, 2025· 160 views

This Prisma error occurs when your schema references a model whose underlying database table has not been created yet. The fix involves applying pending migrations or synchronizing your schema with the database.

Quick fix

Fixes P1014: The underlying model does not exist

// Example: Check that your model is properly defined
model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
}
  1. Verify your Prisma schema matches your intent
  2. Apply pending migrations to create missing tables
  3. Check migration file ordering
  4. Reset the shadow database if corrupted
prisma — error
// Example: Check that your model is properly defined
model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
}
P1014: The underlying model does not exist

What this error means

The P1014 error in Prisma indicates a critical mismatch between your Prisma schema file and the actual state of your database. When you define a model in your schema.prisma file, Prisma expects a corresponding table to exist in the database. This error is thrown when Prisma Client or Prisma Migrate attempts to access or reference a model, but the underlying database table is missing. This error commonly occurs during migration operations, particularly when using the shadow database feature in Prisma Migrate. The shadow database is a temporary database that Prisma uses to detect schema drift and validate migrations. If the shadow database doesn't contain the expected tables, or if your migration files are out of order, P1014 will be thrown. Understanding this error is essential for maintaining database schema consistency across development, staging, and production environments. The error message usually includes the specific model name that's causing the issue, making it easier to identify which table is missing.

Typical symptoms

  • Error message "P1014: The underlying table for model `ModelName` does not exist" appears during migration
  • Prisma Client operations fail with P1014 when trying to query a model
  • Migration commands like "prisma migrate dev" or "prisma migrate deploy" throw P1014 errors
  • Shadow database validation fails during migration apply
  • Application crashes at runtime when attempting to use Prisma Client for specific models

Common causes

  1. Migrations have not been applied to the database using "prisma migrate dev" or "prisma db push"
  2. Migration files are out of order or incomplete (e.g., a migration tries to modify a table before it has been created)
  3. The database was manually modified or tables were dropped without corresponding schema changes
  4. Using "prisma db pull" to introspect a database that is missing tables referenced in your schema
  5. Shadow database is out of sync or corrupted during development
  6. Migration history in the "_prisma_migrations" table is incomplete or corrupted
  7. Using PostgreSQL with non-default schemas where Prisma cannot locate the "_prisma_migrations" table

How to fix "P1014: The underlying model does not exist"

1Verify your Prisma schema matches your intent

First, check your schema.prisma file to confirm the model definitions are correct:

prisma
// Example: Check that your model is properly defined
model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
}

Ensure the model causing the error is actually defined in your schema and spelled correctly.

2Apply pending migrations to create missing tables

The most common fix is to apply your migrations to create the missing database tables:

bash
# For development environments
npx prisma migrate dev

# For production environments (applies migrations without prompts)
npx prisma migrate deploy

This will create all tables defined in your schema that don't yet exist in the database. If you're using db push instead of migrations:

bash
npx prisma db push

This syncs your schema directly to the database without creating migration files.

3Check migration file ordering

If you have multiple migration files, ensure they're in the correct chronological order. Each migration should build upon previous migrations:

bash
# List your migrations directory
ls -la prisma/migrations/

Migration folders are timestamped. If you see a migration that modifies a table (e.g., ALTER TABLE) before the migration that creates it (e.g., CREATE TABLE), you have an ordering issue.

To fix:
1. Delete the problematic migration files
2. Reset your database: npx prisma migrate reset
3. Recreate migrations in the correct order: npx prisma migrate dev --name your_migration_name

4Reset the shadow database if corrupted

If the shadow database is causing issues, you can force Prisma to recreate it:

bash
# This resets your development database and recreates the shadow database
npx prisma migrate reset

# Then apply migrations fresh
npx prisma migrate dev

Warning: migrate reset will delete all data in your development database. Only use this in development environments.

5Verify the "_prisma_migrations" table exists

Check if the migration tracking table exists in your database:

sql
-- For PostgreSQL
SELECT * FROM _prisma_migrations;

-- For MySQL
SHOW TABLES LIKE '_prisma_migrations';

If this table is missing or in the wrong schema (PostgreSQL), Prisma cannot track which migrations have been applied. To fix:

bash
# Recreate the migrations table
npx prisma migrate resolve --applied <migration_name>

For PostgreSQL with custom schemas, ensure your schema.prisma includes:

prisma
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
  schemas  = ["public", "your_custom_schema"]
}
6Regenerate Prisma Client after schema changes

After fixing your migrations and database state, always regenerate your Prisma Client:

bash
npx prisma generate

This ensures your application code has the latest type definitions matching your database schema. Restart your development server after generating to pick up the changes.

Advanced notes

Migration File Conflicts: If you're working in a team and multiple developers create migrations simultaneously, you may encounter P1014 when pulling changes. Always coordinate schema changes and resolve migration conflicts by creating a new migration that reconciles the differences.

Production Deployments: Never use prisma migrate dev in production. Always use prisma migrate deploy which applies migrations without interactive prompts and doesn't require a shadow database.

Database Provider Differences: Some database providers (like PlanetScale) don't support Prisma Migrate because they use their own schema management. In these cases, use prisma db push instead or rely on the provider's migration tools.

Prisma Studio Considerations: If you manually delete tables using Prisma Studio or a database client, but don't update your schema, you'll encounter P1014. Always keep your schema.prisma file as the source of truth and use migrations for all schema changes.

Shadow Database Requirements: The shadow database must be accessible and have the same permissions as your main database. If you're in a restricted environment (like some CI/CD pipelines), you may need to disable shadow database checks with the --skip-seed flag or provide a separate shadow database URL.

Frequently asked questions

What does "P1014: The underlying model does not exist" mean?
The P1014 error in Prisma indicates a critical mismatch between your Prisma schema file and the actual state of your database. prisma file, Prisma expects a corresponding table to exist in the database. This error is thrown when Prisma Client or Prisma Migrate attempts to access or reference a model, but the underlying database table is missing.
How do I fix "P1014: The underlying model does not exist"?
This Prisma error occurs when your schema references a model whose underlying database table has not been created yet. The fix involves applying pending migrations or synchronizing your schema with the database.
What causes "P1014: The underlying model does not exist"?
Migrations have not been applied to the database using "prisma migrate dev" or "prisma db push" Migration files are out of order or incomplete (e.g., a migration tries to modify a table before it has been created) The database was manually modified or tables were dropped without corresponding schema changes
Is the "P1014: The underlying model does not exist" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading