Laravel Migration to Prisma

About this Laravel migration to Prisma converter

Paste the migration files from database/migrations and get the Prisma schema they add up to. The migrations are replayed in order (create, alter, rename, drop), so the result is the schema you would have after running them all, then written as Prisma models with both sides of every relation. Nothing is executed and nothing leaves your browser. This page is the Laravel entry point of the Database Schema Studio: the imported schema is fully editable and can also produce a Laravel project or Prisma for another database.

How to use it

1. Paste your migration files (each starts with <?php) or open them from disk, then Import.
2. Read the diagnostics first: they list every construct that could not be read, with its line.
3. Choose the Prisma version and database, adjust the schema if you like, and copy or download the result.

A worked example

These two migration files:

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration
{
    public function up(): void
    {
        Schema::create('users', function (Blueprint $table) {
            $table->id();
            $table->string('name');
            $table->string('email')->unique();
            $table->timestamps();
        });
    }

    public function down(): void
    {
    }
};

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration
{
    public function up(): void
    {
        Schema::create('posts', function (Blueprint $table) {
            $table->id();
            $table->foreignId('user_id')->constrained()->cascadeOnDelete();
            $table->string('title', 200);
            $table->boolean('published')->default(false);
        });
    }

    public function down(): void
    {
    }
};

become these models (Prisma 7, MySQL):

model User {
  id        BigInt    @id @default(autoincrement()) @db.UnsignedBigInt
  name      String    @db.VarChar(255)
  email     String    @unique @db.VarChar(255)
  createdAt DateTime? @map("created_at") @db.Timestamp(0)
  updatedAt DateTime? @map("updated_at") @db.Timestamp(0)
  posts     Post[]

  @@map("users")
}

model Post {
  id        BigInt  @id @default(autoincrement()) @db.UnsignedBigInt
  userId    BigInt  @map("user_id") @db.UnsignedBigInt
  title     String  @db.VarChar(200)
  published Boolean @default(false)
  user      User    @relation(fields: [userId], references: [id], onDelete: Cascade)

  @@map("posts")
}

Note what was understood: id() is an unsigned big auto-increment primary key; timestamps() is two nullable timestamp columns; foreignId('user_id')->constrained() is a foreign key to users (the table name was assumed from the column, as Laravel does, and the diagnostics say so); and cascadeOnDelete() is onDelete: Cascade.

Type mapping (Blueprint to Prisma on MySQL)

Other databases use their own native types (for PostgreSQL, uuid is @db.Uuid). Blueprint types with no Prisma scalar (year, set, spatial types) become Unsupported() fields with a warning.

What it does not read

• Anything computed at run time: variables, config() values, loops, custom macros.
• Raw SQL (DB::statement) and data changes (DB::table(...)->insert): listed, not applied.
• Migrations that only make sense against tables it was not given: reported as unknown tables.
• down() methods (the rollback direction).