Accounting

QuickBooks Data Extractor

When a new customer signs up with their QuickBooks account, Vern's QuickBooks extractor pulls their full accounting history — invoices, customers, payments, and accounts — straight into your product through a single managed migration. You don't ask them to export spreadsheets or wire up QuickBooks's auth flow yourself. It's built for teams onboarding users off QuickBooks and getting their books into your app on day one.

Start migration

Browse all extractors

QuickBooks

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 QuickBooks objects (28 total), including: Accounts, Bill Payments, Bills, Budgets, Classes, Credit Memos, Customers, Departments, Deposits, Employees, Estimates, Invoices, Items, Journal Entries, Payment Methods, Payments, Purchase Orders, Purchases, Refund Receipts, Sales Receipts, Tax Agencies, Tax Codes, Tax Rates, Terms, Time Activities, Transfers, Vendor Credits, and Vendors. All 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 accounting system (e-conomic, Fastbill, FreeAgent) 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

OAuth 2.0 (Authorization Code flow). Your new user authorizes QuickBooks once during onboarding — their credentials never touch your code. QuickBooks access tokens are short-lived and refresh tokens roll on the provider's own schedule, so Vern manages the full token lifecycle and refresh and the import never drops midway. See QuickBooks's authentication guide.

Pagination

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

QuickBooks enforces its own API rate limits (see QuickBooks's rate-limit docs). Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.

OAuth-based sources expire access tokens frequently and require a working refresh flow — a dropped refresh is the most common cause of a half-finished import. Vern owns the refresh loop so a new user's onboarding completes even on a long extraction.

API quickstart

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

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

View docs

Common questions

Can I keep a user's QuickBooks data in sync after the first import? Yes — 28 QuickBooks 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 QuickBooks to e-conomic? Yes — Vern normalizes the QuickBooks data model into typed tables that map cleanly onto e-conomic and into your own product.

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