Trello to Panoply

This page provides you with instructions on how to extract data from Trello and load it into Panoply. (If this manual process sounds onerous, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)

What is Trello?

Trello is a collaboration tool that organizes projects into boards, each of which can be filled with lists of notes that outline tasks for a team, complete with photos, documents, and other attachments. It includes tools to comment and collaborate among teammates. You can use it as a web-based project management application.

What is Panoply?

Panoply is a fully managed data warehouse service that can spin up an Amazon Redshift instance in just a few clicks. It uses machine learning and natural language processing (NLP) to learn, model, and automate standard data management activities from source to analysis. It can import data with no schema, no modeling, and no configuration. With Panoply, you can use your favorite analysis, SQL, and visualization tools just as you would if you were creating a Redshift data warehouse on your own.

Getting data out of Trello

To claim your data from Trello, you can extract it from Trello's servers using the Trello API, a REST API that exposes endpoints that provide information on boards, lists, cards, and actions. For instance, to get data about a list, you might run /lists/[id].

Sample Trello data

The Trello API returns JSON-formatted data. Here's an example of the kind of response you might see when querying for the details of a list.

[{
    "id": "4efe314cc72846af4e00008a",
    "data": {
        "list": {
            "id": "4eea4ffc91e31d174600004a",
            "name": "To Do Soon"
        },
        "board": {
            "id": "4eea4ffc91e31d1746000046",
            "name": "Example Board"
        },
        "old": {
            "name": "To Do Later"
        }
    },
    "date": "2017-12-30T21:46:52.874Z",
    "idMemberCreator": "4ee7deffe582acdec80000ac",
    "type": "updateList",
    "memberCreator": {
        "id": "4ee7deffe582acdec80000ac",
        "avatarHash": null,
        "fullName": "Joe Tester",
        "initials": "JT",
        "username": "joetester"
    }
}, {
    "id": "4efe3147c72846af4e00006d",
    "data": {
        "list": {
            "id": "4eea4ffc91e31d174600004a",
            "name": "To Do Later"
        },
        "board": {
            "id": "4eea4ffc91e31d1746000046",
            "name": "Example Board"
        },
        "old": {
            "name": "To Do Eventually"
        }
    },
    "date": "2017-12-30T21:46:47.843Z",
    "idMemberCreator": "4ee7deffe582acdec80000ac",
    "type": "updateList",
    "memberCreator": {
        "id": "4ee7deffe582acdec80000ac",
        "avatarHash": null,
        "fullName": "Joe Tester",
        "initials": "JT",
        "username": "joetester"
    }
}]

Preparing Trello data

This part can get tricky: You need to parse the JSON in the API response and map each field to a corresponding table in the destination database. You'll need a solid handle on the datatypes for each endpoint. The Stitch Trello Docs can give you a sense of what datatypes will come through the API.

Loading data into Panoply

Once you have identified all of the columns you want to insert, you can use the CREATE TABLE statement in Panoply's Redshift data warehouse to create a table to receive all of the data.

With a table built, it may seem like the easiest way to migrate 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. If you have a high volume of data to be inserted, you would be better off loading the data into Amazon S3 and then using the COPY command to load it into Redshift.

Keeping Trello data up to date

At this point you've coded up a script or written a program to get the data you want and successfully moved it into your data warehouse. But how will you load new or updated data? It's not a good idea to replicate all of your data each time you have updated records. That process would be painfully slow and resource-intensive.

Instead, identify key fields that your script can use to bookmark its progression through the data and use to pick up where it left off as it looks for updated data. Auto-incrementing fields such as updated_at or created_at work best for this. When you've built in this functionality, you can set up your script as a cron job or continuous loop to get new data as it appears in Trello.

And remember, as with any code, once you write it, you have to maintain it. If Trello modifies its API, or the API sends a field with a datatype your code doesn't recognize, you may have to modify the script. If your users want slightly different information, you definitely will have to.

Other data warehouse options

Panoply is great, but sometimes you need to optimize for different things when you're choosing a data warehouse. Some folks choose to go with Amazon Redshift, Google BigQuery, PostgreSQL, or Snowflake, which are RDBMSes that use similar SQL syntax. If you're interested in seeing the relevant steps for loading data into one of these platforms, check out To Redshift, To BigQuery, To Postgres, and To Snowflake.

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 Trello data via the API, structuring it in a way that is optimized for analysis, and inserting that data into your Panoply data warehouse.