Import & Export

Export to CSV, JSON, SQL, MQL, or XLSX. Import SQL files with transaction safety and progress tracking.

Import & Export

Export data in five formats (CSV, JSON, SQL, MQL, XLSX), import SQL files with gzip support, and paste tabular data from the clipboard into the grid.

Export Data

1. Run a query or open a table
2. Click Export in the toolbar (Cmd+Shift+E)
3. Choose a format, select tables, configure options
4. Click Export

MongoDB: SQL export is not available. Use CSV, JSON, MQL, or XLSX. MQL generates db.collection.insertMany([...]) scripts for mongosh.

Redis: SQL and MQL exports are not available. Use CSV, JSON, or XLSX.

Export Formats

CSV

Option	Default
Header row	Yes
Delimiter (comma, semicolon, tab, pipe)	Comma
Quote handling (always, as needed, never)	As needed
NULL to empty strings	Yes
Line breaks in values to spaces	No
Line ending (LF, CRLF, CR)	LF
Decimal separator (period, comma)	Period
Formula sanitization	Yes

JSON

Exports as an array of objects.

Option	Default
Pretty print	Yes
Include NULL values	Yes
Preserve all values as strings	No

SQL

Global options:

Option	Default
Compress with gzip (.sql.gz)	No
Batch size (rows per INSERT)	500

Per-table options (configurable individually for multi-table exports):

Option	Default
Include CREATE TABLE	Yes
Include DROP TABLE IF EXISTS	Yes
Include INSERT data	Yes

MQL

MongoDB only. Generates insertMany() scripts that run directly in mongosh.

Option	Default
Batch size (documents per insertMany)	500

Output is a .js file:

db.users.insertMany([
  {"_id": {"$oid": "507f1f77bcf86cd799439011"}, "name": "Alice", "age": 30},
  {"_id": {"$oid": "507f1f77bcf86cd799439012"}, "name": "Bob", "age": 25}
]);

XLSX

Option	Default
Include headers (bold first row)	Yes
NULL as empty cells	Yes

Each table exports as a separate worksheet. Numbers are stored as numeric cells for proper Excel formatting. Tables exceeding 1,048,576 rows (Excel’s limit) auto-split into multiple sheets.

Exporting Query Results

Right-click the results grid and select Export Results…, or go to File > Export Results…. Choose a format, configure options, and click Export. Only in-memory results are exported.

Use LIMIT in your query to control export size for large tables.

Exporting Entire Tables

Click a table in the sidebar and click Export, or run SELECT * FROM table_name and export.

Export multiple tables at once via the export dialog’s tree view. SQL exports support per-table options for structure, DROP, and data.

Streaming Export

Table exports stream rows directly from the database to disk (shipped v0.33.0). No in-memory buffering, no row-count limit: tables larger than RAM export fine.

Properties:

• Streamed write per row, constant memory regardless of table size
• Atomic file write: the destination file appears only on success, partial files are removed on failure
• Cancellable from the progress dialog. Cancellation removes the partial file
• Per-row error handling, configurable in the export dialog:

Mode	Behavior
Stop and Rollback	Stop on first row error and discard the output file.
Stop and Commit	Stop on first row error but keep rows already written.
Skip and Continue	Skip the failing row, log it, and continue. A summary lists skipped rows at the end.

Streaming applies to whole-table exports. Result-grid exports use in-memory data.

Clipboard Paste (CSV/TSV)

Paste tabular data directly into the data grid. Press Cmd+V after selecting a row. Format is auto-detected: tabs parse as TSV, commas as CSV.

Import Data

Import .sql and .sql.gz files (statements execute directly against your database: backups, migrations, seed data), or .json / .jsonl files into a table (see Import JSON Data).

MongoDB: SQL import is not available. Use mongoimport or the MQL shell.

Import Workflow

1. Open Import Dialog

   Click File > Import > From SQL (Cmd+Shift+I), or drag and drop a .sql / .sql.gz file onto the app.

2. Configure Options

   Set encoding, transaction wrapping, and foreign key check options.

3. Preview and Import

   Review the SQL preview, statement count, and file size. Click Import to execute.

Import Options

Option	Description	Default
On error	How to handle failed statements (see below)	Stop and Rollback
Encoding	File encoding: UTF-8, UTF-16, Latin1, or ASCII	UTF-8
Wrap in transaction	Execute all statements within a single transaction	Yes
Disable foreign key checks	Temporarily disable FK constraints during import	Yes

For PostgreSQL the checkbox runs SET session_replication_role = replica, which requires the REPLICATION role or superuser. Most managed Postgres providers (RDS, Neon, Supabase) reject it, so the checkbox may have no effect there. TablePro’s SQL exports already emit foreign key constraints with ALTER TABLE ... ADD CONSTRAINT after data load, so the dump round-trips without needing the privilege.

For MySQL the checkbox runs SET FOREIGN_KEY_CHECKS = 0 and is supported on standard accounts. SQLite uses PRAGMA foreign_keys = OFF. Drivers without an equivalent (most NoSQL drivers) ignore the option.

Error Handling Modes

Three modes for handling errors during import:

Mode	Behavior
Stop and Rollback	Stops on first error. If transaction is enabled, rolls back all changes. Default.
Stop and Commit	Stops on first error. Commits statements that succeeded before the error.
Skip and Continue	Logs failed statements and continues importing. Shows a summary with all errors at the end. Transaction wrapping is disabled in this mode.

In Skip and Continue mode, failed statements are collected (up to 1,000) with line numbers and error messages. After import completes, a summary dialog shows how many succeeded vs failed, with a scrollable error list and a “Copy Errors to Clipboard” button.

Import JSON Data

Choose File > Import > From JSON and pick a .json, .jsonl, or .ndjson file, and TablePro opens a dedicated JSON import sheet. It accepts an array of objects [{...}, {...}], newline-delimited JSON (one object per line, streamed for large files), and TablePro’s own JSON export shape { "table": [ {...} ] }, so an export round-trips back in.

Choose a destination:

• Existing table: pick the table, then map each JSON field to a column. Fields are auto-matched by name; toggle any field off to skip it, or remap it to a different column. Columns with no matching field keep their default or NULL.
• New table: name the table and review the columns TablePro infers from the data. Each column’s name, type, primary key, nullable flag, and default are editable before the table is created.

Rows insert through parameterized statements, so JSON values are never concatenated into SQL. Nested objects and arrays are stored as JSON text. The on-error, transaction, and “delete existing rows” options work the same as SQL import.

Progress and Errors

During import, a progress bar shows statements processed and overall completion.