Import Excel to Supabase

Did you know that more than 80 % of businesses still store critical data in isolated Excel files? Imagine turning those static spreadsheets into a live, query‑able backend in minutes—no DBA required. In this guide we’ll show you exactly how to import an Excel workbook into Supabase, so your formulas like VLOOKUP or XLOOKUP can power real‑time dashboards and apps.

If you’re new to Supabase, think of it as a modern, open‑source alternative to Firebase that gives you a Postgres database, authentication, storage, and serverless functions all in one place. If you’re a seasoned Power User, you’ll find that the same tools let you take your spreadsheet workflows to the cloud with minimal friction.

In This Article

• Why Move Your Excel Data to Supabase?
• Preparing Your Spreadsheet for Import
• Step‑by‑Step Walkthrough: Importing Excel (CSV) into Supabase
• Beyond the Import: Turning Your Data Into Apps
• Actionable Takeaways & Best Practices
• Frequently Asked Questions

Why Move Your Excel Data to Supabase?

Collaboration at scale – multiple users edit data simultaneously without version‑conflict headaches. Security & backup – automatic snapshots, row‑level security, and GDPR‑ready hosting. From static to dynamic – enable APIs, triggers, and server‑less functions that react to changes in your spreadsheet. I’ve found that when a team suddenly needs to pull in new sales data, an Excel file on OneDrive can feel like a single point of failure. Supabase eliminates that bottleneck by providing a reliable, versioned data store that’s accessible from anywhere.

Preparing Your Spreadsheet for Import

• Clean‑up checklist – remove merged cells, ensure a single header row, and convert dates/numbers to proper formats. Excel loves to auto‑format, but Postgres wants plain text.
• Using formulas before export – how VLOOKUP/XLOOKUP can enrich data that will be persisted in Supabase. Remember, formulas don’t carry over; only the values do.
• Saving as CSV vs. XLSX – pros and cons; why the article recommends CSV for a frictionless upload. CSV is the lingua franca of data, and Supabase’s dashboard will happily ingest it.

But let’s be real: you’re probably thinking, “I could just copy and paste.” That works for tiny tables, but as soon as you hit a few hundred rows, the process becomes error‑prone. Stick with CSV and watch the headaches shrink.

Step‑by‑Step Walkthrough: Importing Excel (CSV) into Supabase

1. Create a Supabase project & table

Head to Supabase.io and create a new project. Once the dashboard loads, click Table Editor and hit New Table. Name it after your sheet—say customers. Pick column types that match your Excel headers: text, int, date, etc. If you’re unsure, Postgres will auto‑detect, but double‑check the created_at column to be timestamp with time zone for consistency.

2. Upload the CSV via Supabase Dashboard

Drag and drop the file onto the “Import CSV” panel. Supabase will preview the first few rows and ask you to map columns. Make sure the header names match exactly; Postgres column names are case‑sensitive. If you hit an error, check for hidden characters or extra spaces in your header row.

3. Programmatic import with JavaScript (Node.js)

For recurring imports, a script is the way to go. Below is a condensed example that reads an Excel file in memory, converts it to CSV, and uses Supabase’s REST API to bulk‑insert. Notice the upsert so you can re‑run the script without duplicating rows.

import fs from 'fs';
import xlsx from 'xlsx';
import { createClient } from '@supabase/supabase-js';

const supabase = createClient(
  process.env.SUPABASE_URL,
  process.env.SUPABASE_SERVICE_ROLE_KEY
);

async function importExcelToSupabase(filePath, tableName, pkCols) {
  const workbook = xlsx.readFile(filePath);
  const sheet = workbook.Sheets[workbook.SheetNames[0]];
  const rows = xlsx.utils.sheet_to_json(sheet, { defval: null });

  const cleaned = rows.map(row => ({
    ...row,
    created_at: row.created_at
      ? new Date(row.created_at).toISOString()
      : null,
  }));

  const { data, error } = await supabase
    .from(tableName)
    .upsert(cleaned, { onConflict: pkCols.join(',') });

  if (error) {
    console.error('❌ Import failed:', error.message);
  } else {
    console.log(`✅ Imported ${data.length} rows into ${tableName}`);
  }
}

importExcelToSupabase('./data/Customer_List.xlsx', 'customers', ['customer_id']);

4. Verification

Open the SQL Editor and run: SELECT * FROM customers LIMIT 10;. If the data looks good, you’re done. You can now access the table via the Restful endpoint /rest/v1/customers and feed it into any front‑end.

Beyond the Import: Turning Your Data Into Apps

• Generating API endpoints – instantly expose your spreadsheet as JSON for front‑end consumption. Supabase does this for you behind the scenes; just enable the Row Level Security policy and you're good to go.
• Connecting Supabase to Power BI / Looker – live dashboards that refresh whenever the underlying Excel data changes. Connect via the Postgres connection string.
• Automating updates – use Supabase Edge Functions or Zapier to re‑import an updated Excel file on a schedule. A simple cron job on a server can run the script we just wrote.

Actionable Takeaways & Best Practices

One‑time vs. recurring imports – if your spreadsheet updates monthly, set up a scheduled script. If you’re just prototyping, manual upload is fine.

Data‑type hygiene – keep column types consistent to avoid VLOOKUP/XLOOKUP mismatches later. Dates should be stored as ISO strings; numbers as integers or decimals.

Performance tips – batch size limits (Supabase allows 10k rows per request), indexing key columns, and using upsert for incremental loads keep your API calls snappy.

Resources – Supabase docs, Excel Power Query, and the original dev.to article for deeper dives.

Frequently Asked Questions

How do I import an Excel file directly into Supabase without converting to CSV?

Supabase currently accepts CSV for bulk import. Use a small script (Node.js or Python) with a library like xlsx to read the .xlsx file and stream it as CSV to Supabase’s /rest/v1/{table} endpoint.

Can I keep Excel formulas (VLOOKUP, XLOOKUP) after importing the data?

Formulas themselves are not stored in the database; only the resulting values are. Run the formulas in Excel before export, or recreate the logic in Supabase using SQL functions or PostgREST filters.

What’s the size limit for a CSV upload to Supabase?

The Supabase dashboard allows files up to 100 MB per upload. For larger datasets, split the file or use the Supabase client library to perform chunked inserts via the REST or RPC API.

Is it possible to schedule automatic re‑imports of an updated Excel workbook?

Yes. Combine a cloud scheduler (e.g., GitHub Actions, Supabase Edge Functions, or a cron job on a server) with a script that pulls the latest Excel file from OneDrive/Google Drive, converts it to CSV, and calls the Supabase upsert endpoint.

Will importing Excel data affect my existing Supabase tables or relationships?

If you import into a new table, there’s no impact. When inserting into an existing table, use upsert with a primary key to avoid duplicate rows and preserve foreign‑key relationships.

---

Related reading: Original discussion

What do you think?

Have experience with this topic? Drop your thoughts in the comments - I read every single one and love hearing different perspectives!