Productivity

Guru Data Extractor

Vern's Guru extractor imports a new user's productivity data — collections, folder items, folders, and folders parent — into your product through a single managed migration, handling Guru's auth, pagination, and rate limits for you. It's built for teams onboarding customers off Guru who want their data in your app from day one.

Start migration

Browse all extractors

Guru

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 Guru objects (12 total), including: Collections, Folder Items, Folders, Folders Parent, Group Collection Access, Group Members, Groups, Members, Search Cardmgr, Tag Categories, Team Analytics, and Teams. 7 of these support incremental change tracking, so syncs pull only what changed.

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 productivity system (Acuity Scheduling, Airtable, BoldSign) 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 Guru account once; Vern stores the credential encrypted and signs each request. See Guru's authentication guide.

Pagination

Vern detects and handles Guru'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

Guru 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 Guru
curl -X POST https://app.vern.so/api/v1/migrations \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Guru → Postgres", "source": "Guru" }'
→ { "migration_id": "mig_..." }
2. Generate the extraction recipe (pulls live via the Guru 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 guru_export.csv

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

View docs

Common questions

Can I keep a user's Guru data in sync after the first import? Yes — 7 Guru objects support incremental change tracking, so after the first full import Vern pulls only what changed on re-run.

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

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