Exporting data from Coda

Hi,

Does anyone have any ideas for exporting data from Coda? The options their FAQ suggest aren’t particularly useful -

  • print the page (but it only prints the current section, so you would have to do them all one by one, and in any case, the data isn’t useable so really, it’s a pointless suggestion);
  • copy and paste (fine for text, but tables with multi-line text just doesn’t paste cleanly into another spreadsheet);
  • the ‘export data’ option in account settings, but you just get a bunch of tab separated text files, and again this doesn’t import cleanly into another spreadsheet. XML or another modern equivalent would be much more useful.

I’ve had a look through the packs and can’t even find a Google Sheets pack.

Just wondering if anyone has a miracle suggestion?

Thanks,

Rohan

1 Like

@anon86103599

I currently use the API to pull the table, then create my own html output, and print to pdf. It has been the only way to reliably export full docs that I have found.

1 Like

This works fine for table-based data, but fails to protect text and the many [potentially] embedded data and analytics in texts. Then there’s images embedded in texts - a lot to think about and mentioned here.

Here’s how I create a full-text search and also capture important Coda-based texts.

  • Create an automation that emails each important section to a role account in G-Suite.
  • Harvest inbound emails from the automation process in Coda.
  • Transform the section content into a Google Drive document where the name is the section title that creates a new document when one doesn’t exist, and simply overwrites one that already exists.
1 Like

Thanks @Joshua_Upton and @Bill_French for your replies.

Unfortunately I have no web development skills so the API is beyond me at this point.

Fortunately I had not committed anything critical to Coda, just a fair bit of data entry on a couple of gaming related docs. I have the text output so maybe one day I will find the time to write a program that will parse those and put the data into another database.

I think other users would do well to consider the ramifications of the fact that there isn’t a practical way to get your data out of Coda. For my own software, if a client decides they don’t want to use it anymore they get a copy of their data in an Access database, making their data readily available to whatever system they are moving to.

Yep - and there’s the added issue of formulas, filters, grouping, etc. All of the business logic that makes an application work. Making snapshots is easy - just duplicate the document, right? Um, no - there are hidden elements and backing up offline in a comprehensive manner is not so simple.

And Access is probably not ideal either since it is on a fast-track to sunset.

1 Like

An option that might work somewhat is to use the Gmail Pack to email sections (using a button I would suggest). The emailed tables actually look decent, and I believe you could copy-and-paste into a spreadsheet in a pinch. Note that this might be included in what @Bill_French suggested?

That solution still does not back-up formulas, so it’s only somewhat useful depending on your use case.

1 Like

Thanks @Ian_Nicholson, I will give that a try.

1 Like

My backup process does use the Gmail pack, but with an action that happens every night. This is fine for section content, but I do not harvest data this way (even though it is embedded in the section texts).

Instead, I configure the service to acquire JSON representations of the tables and store those in parallel to each document maintained as a complete backup instance in Google Drive.

1 Like