How to Migrate from Goodreads to StoryGraph (Step-by-Step, 2026)

· By IMRAN HOSSAIN

Quick answer: Yes, you can import your Goodreads data into StoryGraph by exporting your Goodreads library as a CSV, cleaning and mapping key columns (title, author, ISBN, rating, shelves, dates), and then uploading that CSV with StoryGraph’s import tool, with a few fixes you can keep ratings, shelves, dates, and reviews intact.

  • Export from Goodreads, then open the CSV in Google Sheets or Excel and normalize titles, authors, and ISBN13.
  • Use StoryGraph’s import UI to map Goodreads fields to StoryGraph fields, check the import report, and correct mismatches.
  • Keep editions straight by preferring ISBN13 and use tools like OpenRefine or Calibre for batch fixes.

How do I export my Goodreads data?

Export your Goodreads library using the Goodreads Export Library tool, which produces a CSV of every book on your shelves.

On the Goodreads website go to My Books, choose the Tools menu, then click Export Library to download a CSV file named goodreads_library_export.csv. That CSV contains columns such as title, author, isbn, isbn13, my_rating, my_review, date_read, and shelves. If you prefer a one‑click route, many users open the desktop site to access the Export Library link directly. If you want step patterns for larger migrations, see our StoryGraph vs Goodreads guide for the platform comparison you will need after migrating.

How should I clean and prepare the Goodreads CSV before import?

Clean the CSV by standardizing ISBNs, fixing author name formats, removing duplicated editions, and ensuring date formats are consistent.

Open the CSV in Google Sheets or Microsoft Excel and check these columns first: title, author, isbn13, my_rating, my_review, date_read, date_added, and shelves. Convert any isbn fields to plain text so leading zeros are preserved, normalize date formats to YYYY-MM-DD, and split multi‑shelf entries into a primary status column such as read, currently-reading, or to-read. For bulk deduplication and precision matching use OpenRefine or Calibre to reconcile ISBNs and edition metadata. If you have hundreds of entries, create a pivot of isbn13 counts to spot mismatches. If you need migration templates or checklists from other apps, the migration checklist patterns in our Wave to Xero guide show the order of export, clean, import steps that generalize well.

Which Goodreads columns map to StoryGraph fields?

StoryGraph accepts the main Goodreads columns: title, author, isbn or isbn13, my_rating, date_read, date_added, pages, and review, plus tags mapped to StoryGraph tags or moods.

During import StoryGraph will ask you to map CSV columns to its fields. Map Goodreads my_rating to StoryGraph rating, date_read to completion date, date_added to added date, and shelves to reading status. Use isbn13 when possible because StoryGraph matches entries against its metadata using ISBN and title/author combinations. Goodreads review text becomes StoryGraph review if you include that column. Tags and shelves can be imported as StoryGraph tags, but you may need to split combined shelf cells first. For batch edition resolution, prefer isbn13 and use OpenRefine reconciliation if many books fail to match.

How do I import the cleaned CSV into StoryGraph?

Import the cleaned CSV in StoryGraph via My Books, Import/Export, then upload the CSV and follow the field mapping steps.

Create or log into your StoryGraph account, go to My Books, choose Import and Export, then Upload CSV. StoryGraph shows a field mapping screen where you match your CSV columns to StoryGraph fields. After mapping you will see a preview; confirm ratings, dates, and reading statuses look right and start the import. When finished StoryGraph presents an import report listing successful matches and items it could not match. For unresolved items, export the report CSV, fix identifiers like ISBN13 or author spelling, and re-import those rows. If you need an official reference for the import flow, check StoryGraph’s help or import documentation for the current UI and limits. Learn how to export or delete your StoryGraph data and exercise control over rights at StoryGraph Privacy & Data Rights: Exporting, Deleting, and Control.

What causes import mismatches and how do I fix them?

Mismatches happen when StoryGraph cannot match your row to a book because of missing or incorrect ISBNs, variant titles, or author name discrepancies.

Open the import report to see rows marked as unmatched. Fixes include: replacing ISBN with ISBN13, removing trailing series numbers from titles such as “Book Title (Series 2)”, standardizing author names to “Last, First” or “First Last” consistently, and correcting OCR or punctuation errors in titles. If the CSV row lacks ISBNs, StoryGraph tries title and author matching which is fragile across editions. For batches, use OpenRefine’s clustering to unify variations and export a corrected CSV. After correcting a small sample, re-import only the corrected rows. If you prefer a technical reconciliation approach, tools used in larger data transfers like our QuickBooks to Sage checklist demonstrate validating keys before import.

How do I preserve ratings and shelves correctly when importing?

Ratings and shelves transfer when you map Goodreads my_rating to StoryGraph rating and convert Goodreads shelves into StoryGraph reading status or tags.

Ensure the my_rating column contains numeric values 1 through 5; StoryGraph will import numeric ratings into the same 1 to 5 scale. For shelves, extract the single most relevant shelf into a status column labeled status with values like read, currently-reading, to-read; extra shelves can be imported as tags. If you use multiple personal shelves for categories such as “favorites” or “audiobook”, import them as tags and set your preferred reading status separately. After import, verify a few samples for accuracy. If several ratings fail to appear, check for hidden characters or non‑numeric values in the rating column. The migration approach used for tagging and status conversions in our Keeper to Bitwarden guide is a helpful template for transforming categorical fields consistently.

What trade-offs and hidden costs should I consider before migrating?

Migrating from Goodreads to StoryGraph saves you analytics and mood tagging, but you trade automated Amazon integrations and may face edition cleanup work based on ISBN completeness.

Decision framework: 1) Inventory size, 2) Importance of reviews and comments, 3) Edition accuracy, 4) Desire for analytics. If your library has fewer than 200 items and most rows include isbn13, migration is low effort. If you have thousands of entries with missing ISBNs and many localized editions, expect several hours of cleanup. Goodreads launched in 2006, which explains why legacy exports often include inconsistent metadata due to years of crowdsourced entries (Goodreads Wikipedia page, 2026). That history means older libraries often require more reconciliation. Also consider privacy and permanence: StoryGraph stores imported reviews and tags, so if you need deletion or export policies consult StoryGraph’s privacy documentation. For migration methodology, see the sequence in large IT migrations like our Ahrefs to AccuRanker writeup, which emphasizes staging, sampling, and rollback steps.

Which one fits you?

Choose StoryGraph if you want richer reading stats and mood/tags; stay on Goodreads if you need Amazon purchase sync or broad social club features.

Reader profiles: 1) Casual reader, small library: Choose StoryGraph because import is fast and analytics help discover trends. 2) Heavy collector with many editions: Delay migration until you consolidate ISBN13 using Calibre or OpenRefine, because StoryGraph matches ISBNs strictly. 3) Club organizer who needs event and group features: Keep Goodreads for its large groups, unless you want StoryGraph charts. Decision rules: If most books have ISBN13, import now; if less than 50 percent have ISBNs, spend a day reconciling ISBNs first. Who should NOT use StoryGraph: people who rely on Goodreads’ Amazon integration for purchases and automatic shelf syncing. If you want migration patterns or checklists from other project types, our Anytype to Capacities guide shows gating and rollback practices you can borrow.

What are common mistakes people make when importing?

The most common errors are missing ISBN13, importing combined shelves as one status, and not normalizing date formats.

Specific fixes: export the import report and correct ISBNs, split shelves into separate columns before import, and reformat dates to YYYY-MM-DD. Avoid editing the CSV in a text editor that can change encoding or corrupt commas. Do not rely on title-only matching for long series, because edition differences will produce duplicates. Also, do not import thousands of rows without sampling: import a 50-row sample to validate mapping first. If you need help thinking like a migration project manager, the staged import ideas in our LastPass to 1Password migration guide explain how to import in phases and validate each phase.

What checklist should I follow for a safe migration?

Follow a checklist: backup Goodreads CSV, sample-clean, map fields, import sample, review report, fix unmatched, full import, spot-check, and keep backups.

  • Backup: download Goodreads CSV and save a copy externally.
  • Sample clean: fix 20 rows and confirm mapping in StoryGraph.
  • Map: match columns to StoryGraph fields and preview.
  • Import: run sample import and examine the report for mismatches.
  • Fix and re-import: correct csv rows, then import remaining rows.
  • Archive: keep the original CSV and the final import report for records.

These steps mirror robust migration checklists used in finance and SaaS migrations; for a formal checklist and rollback steps see our HubSpot and Pardot checklist and the NetSuite migration approach in our NetSuite migration resource.

Could you show worked examples?

Example 1: a 300-book personal library with ISBN13 on 85 percent of rows will take roughly 1 to 2 hours to clean and import if you sample and batch-fix the remaining rows.

Steps: export CSV, open in Google Sheets, convert isbn to text, fill missing ISBNs using LibraryThing or Amazon metadata, normalize dates, import a 50-row sample, fix issues, then import remaining rows. Example 2: an active reviewer with 1,500 entries and mixed editions faces more work and should reconcile ISBNs with OpenRefine, use Calibre to manage EPUB metadata, and import in 500-row batches. These sample plans follow the same staging and validation from larger migrations such as our Dotloop to DocuSign process where testing small batches prevents large rollbacks.

Comparison: Goodreads versus StoryGraph

Product Price range Best for Key strengths Main limits
Goodreads Free (ad supported) Large social groups and Amazon integration Wide user base, purchase sync, book club features Fewer analytics, dated UI
StoryGraph Free, optional paid tiers Readers who want detailed stats and mood/tags Advanced reading analytics, mood tags, import tools Limited social features compared with Goodreads

What practical tools help with edition matching?

Use OpenRefine for clustering title variants, Calibre to inspect ebook metadata, and ISBNdb or LibraryThing for lookups when ISBNs are missing.

OpenRefine helps cluster similar titles and normalize author names. Calibre can read EPUB and MOBI metadata to extract standardized titles and authors. ISBNdb and LibraryThing provide ISBN lookups if you need to fill missing identifiers. For spreadsheet fixes, Google Sheets has VALUE and TEXT functions to standardize isbn fields. If you are automating reconciliation at scale, export unmatched rows and run them through an ISBN lookup service before reimporting. Use the same staging and sampling concepts used in other migrations like our Airbnb to Hostaway guide, which emphasizes small test imports to validate automated lookups.

Common migration mistakes and how to recover from them

Common mistakes include importing without a sample, overwriting tags accidentally, and failing to save original CSV backups.

Recovery steps: restore from the original CSV, import using smaller batches, and maintain a changelog of edits. If you accidentally imported duplicates, delete the problematic entries in StoryGraph, correct the CSV, then re-import only those rows. If tags were mapped incorrectly, export current StoryGraph books, correct the tag column, and re-import tags only if the platform supports tag-only updates. For procedural safeguards used in other contexts, consult our OneNote to Notion transition guide which shows exporting, archiving, and validating before final cutover.

FAQ

Can you transfer data from Goodreads to StoryGraph?

Yes. Export your Goodreads CSV and import it into StoryGraph using StoryGraph’s import tool, mapping title, author, ISBN, rating, and dates to preserve your library and reading history.

Why are people no longer using Goodreads?

Several users switch because Goodreads’ interface and moderation workflows are less focused on reading analytics and personalized tags, which StoryGraph emphasizes with charts, moods, and granular stats. Learn to apply moods tags and reading pace in StoryGraph to improve discovery and habits with this guide descriptive anchor text.

Can StoryGraph and Goodreads be synced?

No. There is not a built‑in two‑way sync; each platform stores its own data. You can periodically export from Goodreads and re-import to StoryGraph, but this is a one‑time or occasional manual process.

How do I import my data from Goodreads?

Export from Goodreads via My Books > Import and Export, download the CSV, clean any problematic fields, then upload and map the CSV in StoryGraph’s import interface.

Will my Goodreads ratings move to StoryGraph?

Yes, ratings move when you map the Goodreads my_rating column to StoryGraph rating; verify numeric values and scale during the import preview to avoid mismatches.

How do I fix import mismatches after importing to StoryGraph?

Open the StoryGraph import report, correct ISBN13, titles or author spellings in your CSV, and re-import only the corrected rows to resolve the remaining mismatches.

Summary: Export your Goodreads CSV, clean ISBNs and dates, map fields carefully in StoryGraph’s import, fix unmatched rows with ISBN13 or normalized author names, and import in samples before full migration. For a broader comparison to decide if a move is right, see the StoryGraph vs Goodreads guide; for migration process patterns and checklists consult related migration guides like HubSpot and Pardot and NetSuite migration.

External references: the Goodreads export tool is available on the Goodreads site at the Export Library page, which is the starting point for CSV downloads, and historical context for Goodreads is documented on the Goodreads Wikipedia page.

If you want a tailored walkthrough for your exact CSV (sample rows and problem entries), save your export and follow the sample-clean-import cycle described above; for further migration project methods see our related guides such as LastPass to 1Password and Wave to Xero that apply the same staging and rollback principles.

Edit Template