Hi digital neighbor! This page supplies instructions for how to extract data from Quickbooks’ backend and replicate it into Amazon Redshift. (If this DIY process is a bit more involved than you’d prefer, check out Stitch, which can do all the heavy lifting in just a few clicks.)
Pulling Data Out Of Quickbooks
The first step of getting your Quickbooks data into AWS Redshift is actually pulling that data off of Quickbooks’ servers. You can do this using the Quickbooks Accounting and Payments API’s which are available to everyone who uses the service. The full programming guide can be accessed here.
Sample Quickbooks Data
The API returns XML-formatted data. Below is an example of the kind of response you might see when querying the api.
<div class="codeDiv"> <pre> <code><p><IntuitResponse xmlns="http://schema.intuit.com/finance/v3" time="2013-04-03T10:22:55.766Z"> <QueryResponse startPosition="10" maxResults="2"> <Customer> <Id>2123</Id> <SyncToken>0</SyncToken> ... <GivenName>Srini</GivenName> </Customer> <Customer> <Id>2124</Id> <SyncToken>0</SyncToken> ... <GivenName>Peter</GivenName> </Customer> </QueryResponse> </IntuitResponse> </p></code> </pre> </div>
Preparing Quickbooks Data for Redshift
Here’s the tricky part: you need to map the data that comes out of each Quickbooks API endpoint into a schema that can be inserted into a Redshift database.
This means that, for each value in the response, you need to identify a predefined datatype (i.e. INTEGER, DATETIME, etc.) and build a table that can receive them. The Quickbooks API documentation can give you a good sense of what fields will be provided by each endpoint, along with their corresponding datatypes.
Inserting Quickbooks Data into Redshift
Once you have identified all of the columns you will want to insert, you can use the CREATE TABLE statement in Redshift to create a table that can receive all of this data.
With a table built, it may seem like the easiest way to add your data (especially if there isn’t much of it), is to build INSERT statements to add data to your Redshift table row-by-row. If you have any experience with SQL, this will be your gut reaction. But beware! Redshift isn’t optimized for inserting data one row at a time, and if you have any kind of high-volume data being inserted, you would be much better off loading the data into Amazon S3 and then using the COPY command to load it into Redshift.
Keeping Data Up-To-Date
So, now what? You’ve built a script that pulls data from Quickbooks and loads it into Redshift, but what happens tomorrow when you have 150 new transactions?
The key is to build your script in such a way that it can also identify incremental updates to your data. Thankfully, Quickbooks’ API results include fields like ‘time’ that allow you to quickly identify records that are new since your last update (or since the newest record you’ve copied into Redshift). You can set your script up as a cron job or continuous loop to keep pulling down new data as it appears.
Other Data Warehouse Options
Redshift is totally awesome, but sometimes you need to start smaller or optimize for different things. In this case, many people choose to get started with Postgres, which is an open source RDBMS that uses nearly identical SQL syntax to Redshift. If you’re interested in seeing the relevant steps for loading this data into Postgres, check out Quickbooks to Postgres
Easier and Faster Alternatives
If all this sounds a bit overwhelming, don’t be alarmed. If you have all the skills necessary to go through this process, chances are building and maintaining a script like this isn’t a very high-leverage use of your time.
Thankfully, products like Stitch were built to solve this problem automatically. With just a few clicks, Stitch starts extracting your Quickbooks data via the API, structuring it in a way that is optimized for analysis, and inserting that data into your Amazon Redshift data warehouse.