CREATE TABLE from PostgreSQL, MySQL, SQLite. The tool extracts columns, types, constraints, and generates Prisma models.

Does it detect relationships?

Foreign keys are mapped to Prisma relations. Many-to-many joins (with explicit junction tables) are recognized and mapped appropriately.

Postgres ENUM types become Prisma enums. MySQL CHECK-constraint enums need manual review — Prisma prefers explicit enum definitions.

Will the Prisma schema round-trip?

Run `prisma migrate diff` to compare. Minor drift is likely (defaults, indexes). Use this as a starter; hand-tune the Prisma schema for production.

SQL → Prisma Schema | DevTools Surf

DevTools Surf

Example: SQL → Prisma Schema

A worked example, rendered from real sample data. Sign in to run the tool on your own input.

Input

CREATE TABLE users (
  id SERIAL PRIMARY KEY,
  email VARCHAR(255) NOT NULL UNIQUE,
  name VARCHAR(100),
  role VARCHAR(20) DEFAULT 'user',
  active BOOLEAN DEFAULT true,
  created_at TIMESTAMP DEFAULT NOW()
);

CREATE TABLE posts (
  id SERIAL PRIMARY KEY,
  title VARCHAR(255) NOT NULL,
  body TEXT,
  user_id INTEGER REFERENCES users(id),
  published BOOLEAN DEFAULT false
);

Output

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id        Int       @id @default(autoincrement())
  email     String    @unique
  name      String?
  role      String?   @default("user")
  active    Boolean?  @default(true)
  createdAt DateTime? @default(now()) @map("created_at")
  posts     Post[]

  @@map("users")
}

model Post {
  id        Int      @id @default(autoincrement())
  title     String
  body      String?
  userId    Int?     @map("user_id")
  published Boolean? @default(false)
  user      User?    @relation(fields: [userId], references: [id])

  @@map("posts")
}

About SQL → Prisma Schema

SQL → Prisma Schema preview - Data / SQL tool

Convert SQL CREATE TABLE statements to Prisma schema. Part of the DevTools Surf developer suite. Browse more tools in the Data / SQL collection.

Use Cases

Backend developers migrating legacy SQL databases to Prisma ORM
Full-stack teams bootstrapping Prisma schemas from existing tables
Database architects converting SQL DDL for Node.js projects
Developers reverse-engineering database schemas into type-safe models

Tips

Map SQL foreign keys to Prisma relation decorators accurately
Check that column defaults translate to @default() annotations
Verify index and unique constraints carry over to the schema

Fun Facts

Prisma was founded in 2016 in Berlin by Johannes Schickling — it evolved from Graphcool, a GraphQL backend-as-a-service, into a standalone ORM for Node.js and TypeScript.
Prisma's schema language (PSL) was designed to be database-agnostic — a single schema file can target PostgreSQL, MySQL, SQLite, MongoDB, or SQL Server with a one-line change.
The Prisma Migrate engine generates SQL migration files that are human-readable and version-controlled, bridging the gap between schema-first and migration-first workflows.

FAQ

Which SQL dialects?: CREATE TABLE from PostgreSQL, MySQL, SQLite. The tool extracts columns, types, constraints, and generates Prisma models.
Does it detect relationships?: Foreign keys are mapped to Prisma relations. Many-to-many joins (with explicit junction tables) are recognized and mapped appropriately.
What about enums?: Postgres ENUM types become Prisma enums. MySQL CHECK-constraint enums need manual review — Prisma prefers explicit enum definitions.
Will the Prisma schema round-trip?: Run `prisma migrate diff` to compare. Minor drift is likely (defaults, indexes). Use this as a starter; hand-tune the Prisma schema for production.

Related Data / SQL Tools

CSV Viewer CSV → SQL INSERT SQL → CSV Fixture TSV ↔ CSV CSV Schema Validator CSV Column Remapper CSV Validator with Schema SQL Identifier Caser