Skip to main content Skip to complementary content
Already have an account? Sign in

QuickBooks (v21-12-2015)

Last updated: 9/15/2026

QuickBooks integration summary

Stitch’s QuickBooks integration replicates data from a QuickBooks Online instance using the QuickBooks Online API. Refer to the Schema section for a list of objects available for replication.

Note: Currently, replicating data from QuickBooks Desktop apps isn’t supported.

QuickBooks feature snapshot

A high-level look at Stitch's QuickBooks (v21-12-2015) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Deprecated on September 3, 2020

Supported by

Stitch

Stitch plan

Standard

API availability

Not available

Singer GitHub repository

Not applicable

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Unsupported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Unsupported

Column selection

Unsupported

Select all

Unsupported

TRANSPARENCY
Extraction Logs

Unsupported

Loading Reports

Supported

Connecting QuickBooks

QuickBooks setup requirements

To set up QuickBooks in Stitch, you need:

  • An online QuickBooks instance. Support for replicating data from desktop QuickBooks instances isn’t currently supported.

Step 1: Add QuickBooks as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the QuickBooks icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch QuickBooks” would create a schema called stitch_quickbooks in the destination. Note: Schema names cannot be changed after you save the integration.

Step 2: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your QuickBooks integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond QuickBooks’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 3: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

QuickBooks integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 4: Authorize Stitch to access QuickBooks

Lastly, you’ll be directed to QuickBooks’ website to complete the setup.

  1. If you’re not already signed into your QuickBooks account, enter your credentials and click Login.
  2. A screen asking for authorization to QuickBooks will display. Note that Stitch will only ever read your data.
  3. Click Authorize.
  4. After the authorization process successfully completes, you’ll be redirected back to Stitch.
  5. Click All Done.

Initial and historical replication jobs

After you finish setting up QuickBooks, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

QuickBooks table reference


Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!