Convert your Firestore backup to CSV, SQL, or JSON in seconds. Migrate to PostgreSQL, analyze in Google Sheets, or import into Supabase — no code, no credentials, no waiting.
Drop your Firebase export files here, or click to browse
Only files named output-0, output-1, etc. are accepted
Whether you're migrating platforms, running analytics, or building something new — Fireloom gets your data ready.
Moving your app off Firebase? Export your Firestore data as SQL INSERT statements and import them directly into PostgreSQL, Supabase, Neon, or any relational database. Stop copying data by hand.
SQL formatNeed to understand your data, build reports, or share with your team? Export to CSV and open it directly in Google Sheets, Excel, or any spreadsheet tool. Every document becomes a row you can filter and chart.
CSV formatBuilding a new backend or switching databases? Export your Firestore documents as JSONL — one JSON object per line. Import into MongoDB, feed into a script, or use it however you need.
JSONL formatIn the Firebase Console, go to Firestore and run an export. You'll get a folder with files named output-0, output-1, etc. That's what Fireloom reads.
Drag and drop your export files into the converter above. Pick the format you need — CSV for spreadsheets, JSON for apps, SQL for databases. No account required.
Your converted file downloads instantly. Import it into PostgreSQL, open it in Google Sheets, or load it into Supabase. Your files are deleted from our server immediately.
Not sure which to pick? CSV works with everything. SQL is best for databases.
Opens directly in Google Sheets, Excel, or any data tool. Each Firestore document becomes a row. Great for reporting and analysis.
One JSON object per document, one per line. Works with any programming language or database that reads JSON. Ideal for custom scripts or NoSQL imports.
Numbers stay as numbers. Booleans stay as booleans. When you need your data types preserved exactly as they were in Firestore.
Ready-to-run INSERT statements for PostgreSQL. Copy-paste into psql, import into Supabase, or pipe into any Postgres-compatible database.
Pay once for a 30-day pass — long enough to finish your Firebase migration. No auto-renewals.
Perfect for trying it out or small projects
For full migrations and production data
Fireloom is a single HTTP endpoint. Curl, cron jobs, CI pipelines — convert exports without ever opening a browser.
curl -X POST 'https://fireloom.io/api/convert?format=sql' \
-H "Authorization: Bearer $FIRELOOM_LICENSE" \
-F 'file=@output-0' \
| psql "$DATABASE_URL"
Read the API docs →
In the Firebase Console, go to your Firestore Database, click the three-dot menu, and select "Export entire database." Choose a Cloud Storage bucket as the destination. Once the export finishes, download the folder — it will contain files named output-0, output-1, etc. Those are the files you upload to Fireloom.
Yes. Export your Firestore data, convert it to SQL with Fireloom, and then import the SQL file into your Supabase project's PostgreSQL database using the Supabase SQL Editor or psql. Your Firestore documents become database rows. The free tier handles small projects up to 10 documents; full migrations use the $19 Pro pass.
Absolutely. Choose the CSV format (it's free), convert your data, and open the downloaded .csv file directly in Google Sheets, Excel, or any spreadsheet app. Each Firestore document becomes a row.
Your files are uploaded to our server for conversion and deleted immediately afterward. Nothing is stored. We don't read, log, or keep your data.
The free tier lets you convert up to 10 Firestore documents in any format (CSV, JSONL, JSONL Typed, or SQL). It's great for testing that the output looks right before you buy Pro for a full migration. No account or credit card needed.
No. Fireloom reads the export files directly. It never connects to Firebase, doesn't use the Firebase SDK, and doesn't need any credentials or API keys.
If Fireloom doesn't handle your export correctly, email us within 7 days and we'll refund you — no questions asked.