Lesson 3 of 9 · Basics
Moving your reading data: CSV files, profile imports and APIs
The three ways your reading history moves between apps, and what gets left behind.
Best Book Tracker Apps editors · 29 September 2026 · 2 min read
Reading data moves in three ways: a CSV file you export and import, a profile import that reads your public account elsewhere, or an API that lets software connect directly. Friends lists, comments and challenge history rarely come across, so keep a CSV copy of your library whatever method you use.
Contents
What is a CSV export?
A CSV file is a plain-text table, one row per book, with commas between the fields. The format is documented in RFC 4180. Goodreads exports your library as CSV, and most trackers can read that file: Fable accepts a Goodreads CSV, and BookBuddy imports CSV from Goodreads, LibraryThing and Google Books. BookBuddy also exports CSV, PDF or HTML, and StoryGraph emails you a link to a CSV export when you request one in settings.
What is a profile import?
A profile import skips the file. Literal can read your public Goodreads profile directly, and Fable offers an in-app Goodreads sign-in. It is quicker, but you do not end up with a file of your own.
What does an API add?
An API lets software talk to an app directly. Hardcover publishes a GraphQL API with OAuth, and Literal publishes API documentation for developers. Goodreads stopped issuing new API keys in December 2020, so Goodreads data now leaves mainly through the export file.
What usually gets left behind?
Friends lists, comments and likes on reviews, and reading challenge history. Literal's import guide lists all three among the things that do not come across from Goodreads. Whatever method you use, keep a CSV copy of your library: it is the most widely accepted format among the apps we rank. The import and export table shows each app's options.