Analytics & BI

Metabase Data Extractor

Vern's Metabase extractor imports a new user's analytics & bi data — users, cards, collections, and collections items dashboards — into your product through a single managed migration, handling Metabase's auth, pagination, and rate limits for you. It's built for teams onboarding customers off Metabase who want their data in your app from day one.

Start migration

Browse all extractors

Metabase

SaaS API (REST)

Managed auth, retries, and throttling

Normalized JSON, CSV, and DB-ready output

Cleaned JSON, CSV, and DB-ready output

Export coverage

Know exactly what Vern pulls before you migrate.

Objects Vern extracts

Vern extracts the full set of queryable Metabase objects (7 total), including: Cards, Collections, Collections Items Dashboards, Dashboards, Databases, Native Query Snippets, and Users.

Output schema

Normalized JSON per object with referential keys preserved, so the relationships between your user's records survive the import. Timestamps are returned in ISO 8601. Delivered as JSON or CSV, or loaded straight into your own application database or pushed to your API — whatever your product expects.

Where it can land

Your own application database (Postgres, MySQL), a direct push to your API or webhook, or JSON/CSV files, plus another analytics & bi system (Appfigures, Appfollow, Chartmogul) when a user is switching tools.

Source details

Built for the source type shown above, with extractor content refreshed from the collection record.

Managed by Vern

The details you normally have to build yourself.

Authentication

Basic authentication (username + password / secret). Your user connects their Metabase account once; Vern stores the credential encrypted and signs each request. See Metabase's authentication guide.

Pagination

Vern detects and handles Metabase's paging model (cursor, page-number, or offset) internally and returns one consistent, de-duplicated result set — so you import a user's complete data without ever managing page tokens.

Rate limits and gotchas

Metabase enforces its own API rate limits. Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.

Basic-auth sources transmit credentials on every call and often lack granular scopes, so have your user connect a read-only account where possible. Vern stores the credential encrypted and never logs it.

API quickstart

1. Create a migration for Metabase
curl -X POST https://app.vern.so/api/v1/migrations \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Metabase → Postgres", "source": "Metabase" }'
→ { "migration_id": "mig_..." }
2. Generate the extraction recipe (pulls live via the Metabase API)
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "generate", "extract_via_api": true }'
3. Run the approved extraction
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "execute" }'
4. Download the normalized CSV export
curl https://app.vern.so/api/v1/migrations/$MIGRATION_ID/exports/{template} \
  -H "x-api-key: $VERN_API_KEY" -o metabase_export.csv

A cleaner way to extract without rebuilding source-specific plumbing.

View docs

Common questions

Can I keep a user's Metabase data in sync after the first import? Vern supports re-running an import on demand; incremental change tracking depends on what Metabase's API exposes for each object.

Can I move a user from Metabase to Appfigures? Yes — Vern normalizes the Metabase data model into typed tables that map cleanly onto Appfigures and into your own product.

What does it cost to read the Metabase API? Metabase's own API access follows Metabase's pricing/plan; Vern is billed separately per import. Check Metabase's developer docs for their current limits.