Blue Butterfly produces and accepts several file formats. Pick the right one for the job.
CSV (.csv)
Comma-separated text, one row per line, headers in row 1.
| Direction | Used for |
|---|---|
| Import | Single-sheet data files. Simplest format. See Import Overview. |
| Export | Single-table exports. Pairs well with ZIP file mode for multi-table outputs. |
Tradeoffs:
- Universal — every analysis tool reads CSV
- No types — everything is text. Numbers, dates, booleans all need to be re-parsed by the consumer.
- No multi-sheet — one file per “sheet”; use ZIP to bundle several.
Excel (.xlsx)
Modern Excel format. Multiple sheets in a single file. Preserves typed values (dates as dates, numbers as numbers).
| Direction | Used for |
|---|---|
| Import | Single-sheet or multi-sheet workbooks. See Import a Workbook for multi-sheet imports. |
| Export | Multi-table outputs in one file. Easier for non-technical recipients than ZIP-of-CSVs. |
Tradeoffs:
- Multi-sheet — collar plus all data tables in one file
- Typed values — numbers stay numbers when round-tripped
- More work to parse programmatically than CSV — most analytics pipelines prefer CSV
- Older
.xlsis not supported — convert to.xlsxfirst
ZIP (.zip) — file mode, not format
ZIP is a packaging mode, not a data format. The contents are CSV files (one per data table).
| Direction | Used for |
|---|---|
| Export only | Multi-table CSV outputs bundled into one downloadable archive |
Tradeoffs:
- One download for many CSVs — convenient when you have several data tables
- Recipient extracts to get the individual files — adds a step
- Each CSV is independent — easier to import into tools that expect one file per table
ZIP is selected via the File Mode option in Export Data, in combination with the Format (CSV).
Project Backup JSON (.json)
A custom Blue Butterfly format containing the complete state of a project — schema, drillholes, tables, columns, records, validation rules, formulas, dropdown options, and dropdown colour maps.
| Direction | Used for |
|---|---|
| Backup download | Complete project snapshot — see Backup & Restore |
| Restore upload | Replace current project state with a saved backup |
Tradeoffs:
- Full restoration — a Project Backup is the only file that lets you fully restore a project inside Blue Butterfly
- Specific to Blue Butterfly — not directly readable by external tools (it’s structured JSON, but the schema is bespoke)
- Includes everything — including any sensitive notes; treat backup files as you’d treat the underlying data
Template JSON (.json)
A schema-only JSON file: drillhole template fields, data tables, columns, validation rules, formulas, dropdown options, colour maps. No records.
| Direction | Used for |
|---|---|
| Export | Share schema with another project or another user — see Drillhole Template |
| Import | Load schema into a new or existing project |
Tradeoffs:
- Schema only — perfect for “give me the same setup but a fresh project”
- Same file extension as Project Backup — pay attention which one you’re picking up; they’re produced by different buttons (
Export TemplatevsDownload Backup) - Importing into a project with existing data is supported but cautious work — see the warning in Drillhole Template
SQL Export (.sql)
A Postgres-flavoured SQL dump containing schema definitions and insert statements for the project’s data.
| Direction | Used for |
|---|---|
| Export only | Take data out of Blue Butterfly to load into your own PostgreSQL database |
Tradeoffs:
- Portable — load with
psqlor any Postgres client - Text —
grep,awk, or read directly with a text editor - Not restorable in Blue Butterfly — SQL files don’t round-trip back into the app
- Requires Postgres — not directly importable into MS SQL, MySQL, etc., without translation
Quick reference
| Format | Import? | Export? | Restore? | Best for |
|---|---|---|---|---|
| CSV | ✓ | ✓ | — | Single-table data exchange |
| XLSX | ✓ | ✓ | — | Multi-sheet Excel deliverables |
| ZIP | — | ✓ | — | Bundling multiple CSV exports |
| Project JSON | — | ✓ | ✓ | Full project backup and restore |
| Template JSON | ✓ | ✓ | — | Schema sharing across projects |
| SQL | — | ✓ | — | Loading data into external PostgreSQL |