← Every conversion

Convert a Google BigQuery schema to SQLite

Paste the CREATE TABLE statements from Google BigQuery and ERD Designer draws them as a diagram. Change the diagram's target database to SQLite and every column's datatype is converted. You review each change before it is applied, then generate the SQLite script.

Google BigQuery DDL script

Source database

Diagram name (optional)

You sign up free and land on your diagram. Your script is held for 15 minutes and deleted from our server the moment you open it.

What changes in the sample

Converted to SQLite, these columns of the sample above change type. Everything else keeps its type; names, keys, nullability and lists of allowed values are left as they are.

Column	Google BigQuery	SQLite	Note
`customers.customer_id`	`INT64`	`BIGINT`
`customers.email`	`STRING(255)`	`VARCHAR(255)`
`customers.full_name`	`STRING(120)`	`VARCHAR(120)`
`customers.notes`	`STRING`	`TEXT`
`customers.is_active`	`BOOL`	`BOOLEAN`	default: TRUE → 1
`customers.created_at`	`TIMESTAMP`	`DATETIME`	default: CURRENT_TIMESTAMP() → CURRENT_TIMESTAMP
`orders.order_id`	`INT64`	`BIGINT`
`orders.customer_id`	`INT64`	`BIGINT`
`orders.public_id`	`STRING(36)`	`VARCHAR(36)`	default: GENERATE_UUID() removed
`orders.status`	`STRING(10)`	`VARCHAR(10)`
`orders.receipt_pdf`	`BYTES`	`BLOB`

What it tells you

Where a conversion loses something, ERD Designer says so rather than picking for you. These are the messages for the sample:

orders.public_id: default GENERATE_UUID() does not apply to VARCHAR — removed; generate new keys with a sequence or identity.

The SQLite script

This is what ERD Designer generates for the sample, for SQLite. Our test suite applies this conversion to a real SQLite server and then reads the database back to confirm it matches the diagram exactly.

PRAGMA foreign_keys=OFF;

-- Create table customers
CREATE TABLE "customers" (
  "customer_id" INTEGER NOT NULL,
  "email" TEXT NOT NULL,
  "full_name" TEXT NOT NULL,
  "notes" TEXT,
  "is_active" INTEGER NOT NULL DEFAULT 1,
  "created_at" TEXT NOT NULL DEFAULT CURRENT_TIMESTAMP,
  CONSTRAINT "customers_PK" PRIMARY KEY ("customer_id")
);

-- Create table orders
CREATE TABLE "orders" (
  "order_id" INTEGER NOT NULL,
  "customer_id" INTEGER NOT NULL,
  "public_id" TEXT NOT NULL,
  "status" TEXT NOT NULL DEFAULT 'new',
  "total" NUMERIC NOT NULL,
  "placed_at" TEXT NOT NULL,
  "receipt_pdf" BLOB,
  CONSTRAINT "orders_PK" PRIMARY KEY ("order_id"),
  CONSTRAINT "orders_FK1" FOREIGN KEY ("customer_id") REFERENCES "customers" ("customer_id")
);

-- Add foreign key orders (customer_id) → customers (customer_id)
-- stated inside CREATE TABLE "orders" above;

PRAGMA foreign_keys=ON;

How to convert your own schema

Paste your Google BigQuery script above and press Open in ERD Designer. The diagram opens laid out and ready to edit.
Click the diagram's name in the toolbar to open its properties, choose SQLite under Target Database / Version, and press Apply Changes.
If SQLite offers more than one way to store a kind of column, choose one and press Continue.
Read the list of retyped columns and any warnings, then press Apply Conversion. Save the diagram to keep it.
Press Generate DDL (the database icon) to copy or download the SQLite script — or apply it to a database on your own network with the ERD Designer Agent.

What it reads, and what it does not

It reads CREATE TABLE, ALTER TABLE … ADD CONSTRAINT and CREATE INDEX: tables, columns, keys, foreign keys, unique constraints, check lists and indexes. Anything else in the script is skipped and listed.
It converts the schema, never the data: no rows are read, moved or changed.
It does not convert views, stored procedures, functions, triggers or packages.

Which plan you need

Pasting a script and working with it as a diagram is free on the Basic plan, with no card. Converting a diagram to another database is part of the Pro and Advanced plans, which also generate its script and can apply it through the Agent.

Other conversions

Questions? Write to support@erddesigner.com. · ERD Designer · Terms · Privacy