Sqemo

Import & Export

Updated

Sqemo is not a silo. Schemas come in from the databases you already have and go out to the formats your pipeline expects.

SQL DDL

Import CREATE TABLE DDL and export it back in seven dialects: MySQL, PostgreSQL, Oracle, SQL Server, SQLite, H2, and CUBRID.

On import, primary keys, foreign keys (including inline REFERENCES column constraints), and comments are recognized — foreign keys become relationship lines on the canvas. Import and export operate on the physical model.

DBML

DBML imports and exports round-trip, so you can move between Sqemo and text-first tools like dbdiagram without retyping a schema.

Project files (.erd.json)

The project file carries everything: logical and physical models, the word list, naming rules, and the schema version. It is a plain JSON file — commit it to your repo, diff it in review, send it to a colleague. The MCP server and CLI operate on the same format.

Word lists, domains, and glossary

The standards side moves as CSV, so it survives a trip through a spreadsheet and back:

  • Word list — export as CSV or JSON, import either back. This is how a team’s abbreviations arrive from an existing convention document.
  • Domains — export and import as CSV.
  • Glossary — export the term definitions as CSV.

Word list and domain imports are disabled while a project is connected to a team standard, since the standard is the source of truth there — see Naming standards.

Specification reports (CSV · Markdown)

Four report exports produce the tables that usually get rebuilt by hand for design reviews and audits — entity, column, index, and relationship definitions. Each is a flat CSV of the physical model with the logical names alongside, so a reviewer who does not open the tool can still read what the schema says.

For a wiki or a pull request, Export schema document (Markdown) puts the same content in a single .md file — a mermaid erDiagram block that GitHub, Notion, and Obsidian render as a picture, an entity index, a column and index table per entity, and the relationship table. Headers follow the app’s UI language, so the file pastes into a Korean or English team page as is. GitHub draws the diagram on its own; in Notion, paste the file into a page and switch the Mermaid code block to its preview mode with the toggle in the block’s top-right corner.

Images and print

Export the canvas as PNG or SVG for design docs and reviews, or use PDF / Print to lay the diagram out on paper — A4 or A3, portrait or landscape — and print it or save it as a PDF from the browser dialog.

Migration SQL (Pro)

Beyond exporting the whole schema, Sqemo can generate the ALTER script between a saved baseline and your current model — see Connect to a live database for the related drift check. This one is a Pro feature.

From the command line

The CLI (part of the MCP package, no login required) exports a project file without opening the app:

npx sqemo-mcp export schema.erd.json --format sql --dialect postgres > schema.sql
npx sqemo-mcp export schema.erd.json --format dbml > schema.dbml