Exporting downloads a snapshot of your database to your laptop. Use it before risky changes, when migrating to another host, or when handing the data to a developer for local testing. For long-term backups, use JetBackup instead. It runs nightly, stores off-server, and includes the whole account, not just one database.Documentation Index
Fetch the complete documentation index at: https://help.noxity.io/llms.txt
Use this file to discover all available pages before exploring further.
Quick export (the fast path)
Pick the database from the left tree
Click the database name. Don’t click into a single table unless you only want that table.
Custom export
Custom mode reveals every option. Useful when:- You only want some tables, not all
- You want compressed output (
.zipor.gz) - You want the dump in CSV, JSON, or another format
- You need
INSERT IGNOREinstead ofINSERT, or noDROP TABLEstatements


| Option | What to set |
|---|---|
| Tables | Pick a subset, or click Unselect All then re-pick |
| Output: Compression | gzipped for big databases, usually 1/10th the size |
| Format | SQL is the standard. CSV for spreadsheets. JSON for programmatic use |
| Object creation: Add DROP TABLE | Tick if you want the dump to recreate from scratch on import |
| Data dump: Use extended INSERTs | Untick if you’ve ever hit “MySQL server has gone away” on import |
Format choices
| Format | When to use |
|---|---|
| SQL | Re-importing into another MySQL/MariaDB server |
| CSV | Opening in Excel or Google Sheets, or feeding into a data pipeline |
| JSON | Loading into a script that doesn’t speak SQL |
| XML | Legacy enterprise tools that demand it |
| Printing a snapshot for compliance (schema only, no data) |
Export a single table
Common issues
The download is empty or 0 bytes
The download is empty or 0 bytes
Browser blocked the download, or the export hit a timeout. Switch to Custom, tick Save output to a file, and pick
gzipped compression. Smaller files finish before any timeout.For very large exports, use SSH and mysqldump:The dump has DEFINER clauses I don't want
The dump has DEFINER clauses I don't want
Custom export → scroll to Object creation options → untick Add CREATE PROCEDURE / FUNCTION / EVENT statement if you’re moving the dump to a host that doesn’t run procedures. Or use the SSH route with
mysqldump --skip-definer.I want to re-import on a different host
I want to re-import on a different host
Tick Add DROP TABLE / VIEW / PROCEDURE / FUNCTION / EVENT / TRIGGER statement in the Custom export. This makes the dump self-replacing. Re-importing replaces existing tables instead of failing on duplicates.Watch for
utf8mb4_0900_ai_ci if exporting from MySQL 8 to a MariaDB target. See the import common issues for the workaround.Next
Re-import the dump elsewhere
Same Import tab on another phpMyAdmin or another host.
Set up nightly off-server backups
JetBackup runs without you needing to remember.
Need a hand?
Open a ticket
Best for anything that needs an account check or a config change on our end.
Live chat
Faster for quick questions during business hours.



