Zuora to Redshift

This page provides you with instructions on how to extract data from Zuora’s backend and load it into Amazon Redshift. (If this manual process is a bit more involved than you’d prefer, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)

Pulling Data Out of Zuora

In order to get your Zuora data into AWS Redshift, you have to start by extracting it from Zuora’s servers. You can do this using the Zuora API, which is available to all Zuora customers. Full API documentation can be accessed at this link.

Zuora offers both SOAP and REST API options. We’ll focus on the REST API here as it is easier to implement and is more suited to our analytical needs.

As with most billing system APIs, Zuora’s API goes in both directions and can be used for actually sending them new data and changing things like customer billing information or payment terms. However, for our purposes (getting reporting data into an analytical database), we only need to focus on endpoints that return data to us.

Sample Zuora Data

The Zuora REST API returns data in JSON format. Below is an example of the kind of response you might receive.


{
  "success": true,
  "products":  [
     {
      "sku": "SKU-00000443",
      "name": "Gonkulator",
      "description": "Monthly access",
      "productRatePlans":  [...]
    },
  ]
}

Preparing Zuora Data for Redshift

All that data you’re pulling down from Zuora’s API now needs to be inserted into a table inside 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 Zuora API documentation can give you a good sense of what fields will be provided by each endpoint, along with their corresponding datatypes.

Inserting Zuora 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 Zuora and loads it into Redshift, but what happens tomorrow when you have a hundred new transactions?

The key is to build your script in such a way that it can also identify incremental updates to your data. Thankfully, Zuora’s API results include fields like updated_at 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 Zuora 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 Zuora data via the API, structuring it in a way that is optimized for analysis, and inserting that data into your Amazon Redshift data warehouse.