Productivity - Setup Guide

How to set up Metabase

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• AGPL v3 license on the open-source edition. If Metabase-derived work is exposed as a networked service, the whole thing must be AGPL. Read this carefully before embedding OSS Metabase inside a commercial product (Source: Coefficient: https://coefficient.io/metabase-pricing)
• Starter tier caps at 5 users. The jump to Pro is 5.75x — no gentle middle tier for a growing team of 6-9
• Row-level "sandboxing" (RLS-style permissions) is Pro/Enterprise-only. OSS and Starter can't restrict what data a user sees at row level
• Question caching helps but is per-question; heavy dashboards on cheap data warehouses can still cost real money downstream
• Self-hosted upgrades occasionally require Postgres migrations — read the changelog before yolo-upgrading
• Embedding: static embeds are free, interactive/signed embeds require Pro; embed pricing scales unusually and has changed multiple times

The 7-step setup

1. 1

   Create your Metabase account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Metabase signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Metabase pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Metabase into the rest of your stack. The integrations that most people set up first: Postgres, MySQL, SQL Server, Snowflake, BigQuery, Redshift, Databricks, MongoDB, Presto/Trino, Google Analytics (limited), SQLite, ClickHouse, Druid. Slack (dashboard subscriptions), Email (scheduled reports), Google Sheets (via connector), Zapier/Make (via API).. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Metabase deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Metabase - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Metabase when: business_size is 5-100, needs dashboards, and either has a database or is on a modern warehouse. Highest fit for B2B SaaS, ecommerce, and any team where "we want to see our data without paying for Tableau" is the ask. Do NOT recommend for solo, trades/services with no database, or enterprises needing formal governance. If comparing to Tableau: Metabase wins on price and speed-to-first-dashboard; Tableau wins on visualization power and enterprise governance. If comparing ...