Fable Lets You Import Goodreads. But Can You Easily Take Your Reading Library Back Out?

Moving into a reading app should not be easier than moving out of it.

As of September 26, 2026, Fable documents a Goodreads import feature that can bring reading data into the platform. What its public help center does not currently document is a comparable self-service reading-library export for downloading that library back out as a CSV or similar file.

That distinction matters.

MyBibliotheca is built around a different expectation: if you spend years building a reading history, you should be able to download a copy of it when you want.

Importing is easy. Leaving should be easy too.

Import tools are useful because they remove one of the biggest barriers to switching reading platforms.

Fable lets readers bring Goodreads data in. That is a real convenience.

But portability should work in both directions.

A reading tracker can eventually contain:

• hundreds or thousands of books
• ratings
• reading dates
• lists
• highlights
• notes
• reading habits
• years of personal history

After enough time, the important question is no longer:

Can I get my books into this app?

It becomes:

Can I get my reading history back out in a form I can reuse?

Those are different questions.

What Fable currently documents

Fable's public support documentation includes Goodreads import workflows and tools for stats, lists, highlights, goals, and account management.

As of this article's verification date, its help center does not document a normal self-service library-export feature comparable to a downloadable CSV export.

That does not mean Fable users have no data rights.

Fable's privacy policy says eligible users in certain jurisdictions may request access to personal information and, where applicable, receive it in a structured, commonly used, machine-readable format.

That is an important legal privacy right.

But a privacy-rights request and a normal product-level export are not the same experience.

One is a formal request process.

The other is a feature readers can use whenever they want.

Why self-service export matters

Imagine using a reading tracker for eight years.

You carefully enter:

• every book you finish
• start and finish dates
• ratings
• lists
• notes
• highlights
• goals

Then your needs change.

Maybe another app has better ebook integration.

Maybe you want deeper audiobook tracking.

Maybe you want to build your own database.

Maybe the company changes direction.

Maybe you simply want a backup.

A self-service export turns that decision into a software choice.

Without one, changing platforms can become a data-recovery project.

The valuable part is the history you created

Book metadata is replaceable.

Your personal history is not.

The title and author of a book can be found in many catalogs.

Only you know:

• when you read it
• what you rated it
• what edition you used
• what you wrote about it
• what you highlighted
• whether you abandoned and restarted it

That is the layer worth protecting.

MyBibliotheca makes export a product feature

MyBibliotheca explicitly includes data export.

Its help center documents the ability to download a private CSV copy of supported account and reading data, including books, ratings, notes, dates, and reading logs.

That is not a workaround.

It is part of the product.

The idea is simple:

Your library should still be useful if you stop using MyBibliotheca.

Portability is bigger than one CSV button

A real portability philosophy also changes how the rest of the app works.

MyBibliotheca lets readers bring data in from Goodreads, StoryGraph, and CSV.

It lets readers take data out again.

It is private by default.

It supports external reading tools such as KOReader and Readwise.

The goal is not to trap every part of your reading life inside one ecosystem.

The goal is to make MyBibliotheca a useful home for data you still control.

Goodreads gets an important thing right here

Goodreads provides a CSV library export.

You may prefer another tracker for privacy, integrations, audiobook logging, TBR organization, or deeper reading history.

But the ability to export is valuable and deserves credit.

Data portability should be a baseline feature.

Ask two questions before joining any reading platform

Can I import?

This tells you how easy it is to arrive.

Can I export without contacting support?

This tells you how easy it is to leave.

A platform that enthusiastically accepts another service's CSV should ideally be willing to create one for you too.

MyBibliotheca is designed to be a place you choose to stay

There is a difference between retention and lock-in.

A useful product retains readers because they want to keep using it.

Lock-in retains them because leaving is painful.

MyBibliotheca would rather compete on:

• detailed reading sessions
• audiobook tracking
• KOReader progress sync
• KOReader highlights and notes
• Readwise imports
• private TBR organization
• timelines and statistics
• private-by-default libraries
• data export

Your history should make MyBibliotheca more useful.

It should not make you afraid to leave.

Build your library with MyBibliotheca and keep the ability to take your reading data with you.

Sources

• Fable Goodreads CSV Import
• Fable Reader Support
• Fable Privacy Policy
• MyBibliotheca Help Center
• MyBibliotheca Privacy Policy

Your Reading History Is Not Just App Content. It Is Your Data.

A reading tracker looks harmless when you first sign up.

You add a few books. Mark one finished. Rate another. Save a few titles for later.

Then years pass.

Now that account contains a detailed record of what you read, when you read it, what you thought about it, what you abandoned, what you highlighted, and what you want to read next.

That is not disposable app content.

It is your reading history.

MyBibliotheca is built around the idea that a reading tracker should help preserve that history without making the platform itself the only place where it can exist.

Reading data gets more valuable with time

A book title can be looked up again.

A decade of reading activity cannot be reconstructed accurately from memory.

You may have recorded:

• editions
• start and finish dates
• rereads
• abandoned books
• ratings
• private notes
• highlights
• audiobook listening
• series progress
• reading sessions
• TBR reasons

The value comes from accumulation.

Every year you use a tracker, the cost of losing that history increases.

"It's in my account" is not the same as practical control

A common assumption is:

I entered the data, so I control the data.

Privacy laws may give users important rights over personal information.

But from a practical software perspective, the more useful question is:

Can you get the information back in a format you can actually use?

That is portability.

If the only meaningful copy of your reading history exists inside one company's interface, your practical control is limited by what that interface allows.

Social reading platforms have different priorities

Goodreads and Fable are social reading platforms in different ways.

Social features are not inherently bad.

They can make reading more communal and help people discover books.

But social platforms naturally devote product attention to communities, engagement, recommendations, feeds, clubs, public lists, and reviews.

A personal archive has a different priority.

Its first job is preserving your own record.

MyBibliotheca is intentionally closer to that model.

There is no social feed you need to maintain.

Your library is private by default.

Data export is a first-class feature.

Fable illustrates why product-level portability matters

Fable currently documents ways to import Goodreads information into Fable.

Its privacy policy also describes legal access and portability rights for eligible users.

But as of September 26, 2026, Fable's public support center does not document a general self-service reading-library export comparable to downloading a library CSV from Goodreads or MyBibliotheca.

That is worth knowing before building years of history there.

The distinction is not whether users have privacy rights.

The distinction is whether portability is part of the everyday product experience.

Goodreads does offer a library export

Goodreads provides a library-export feature that generates a CSV.

That is useful.

It is also why migration tools such as MyBibliotheca can help Goodreads users move historical libraries without manually rebuilding them book by book.

Portability does not mean a platform is perfect.

It means an important exit door exists.

Data ownership should include integrations too

Portability is not just about downloading a file when you leave.

It should also mean your reading tracker can coexist with tools you already use.

MyBibliotheca supports:

• KOReader progress sync
• KOReader highlights and notes
• Readwise highlight imports
• Goodreads imports
• StoryGraph imports

Your e-reader does not have to be MyBibliotheca.

Your annotation system does not have to be MyBibliotheca.

Your previous tracker does not have to disappear.

MyBibliotheca can be the place those pieces come together.

Private by default is part of control

Control also means deciding what becomes public.

MyBibliotheca begins with a private library.

Public sharing is optional.

Private notes stay private.

Its current privacy policy says it does not sell personal information or reading history and does not use advertising cookies.

That matters because reading data can be revealing.

A library can expose interests involving health, politics, religion, work, relationships, travel, and personal questions even when none of that is explicitly entered into a profile field.

Export before you need to export

Do not wait until you are angry with a service to think about backups.

Periodically export your reading history from any platform that allows it.

Keep a copy somewhere you control.

The ideal reading tracker makes that boring and easy.

Ask whether the app is preserving your history or holding it

A useful test is:

If this service shut down next month, what would I have?

Would you have:

• a current copy of your library?
• ratings?
• dates?
• notes?
• reading logs?
• enough structured information to import somewhere else?

If the answer is unclear, your reading archive is more fragile than it looks.

Choose a tracker you can leave

This sounds counterintuitive.

Why would an app advertise that you can leave?

Because the strongest form of trust is not making departure artificially difficult.

MyBibliotheca aims to keep readers through usefulness:

• deeper reading logs
• audiobook minutes and positions
• KOReader sync
• highlights
• private TBR planning
• detailed statistics
• flexible editions and series
• privacy
• portability

Not because your history has nowhere else to go.

Try MyBibliotheca and build a reading history you can keep, back up, and move.

Sources

• Fable Privacy Policy
• Fable Reader Support
• MyBibliotheca Privacy Policy
• MyBibliotheca Help Center

Goodreads vs Fable vs MyBibliotheca: What Happens When You Want Your Reading Data Back?

Readers usually compare book apps by asking what they can do after you join.

A more revealing question is:

What can you take with you when you leave?

Goodreads, Fable, and MyBibliotheca all let readers build substantial reading histories, but their publicly documented approaches to portability are different.

As of September 26, 2026:

• Goodreads provides a CSV library export.
• Fable supports importing Goodreads data, but its public help center does not currently document a comparable self-service reading-library export.
• MyBibliotheca supports both importing reading libraries and downloading a private data export.

That difference becomes more important every year you use the service.

Why portability belongs in every book-app comparison

Most comparisons focus on:

• reviews
• recommendations
• statistics
• reading goals
• social features
• book clubs
• interface design

Those matter.

But they mostly describe the experience while everything is going well.

Data portability describes what happens when your needs change.

A reading tracker can hold a decade of:

• books
• ratings
• reviews
• notes
• reading dates
• lists
• goals
• highlights
• reading logs

When you decide to switch, that record suddenly becomes the most important feature.

Goodreads: established CSV export

Goodreads has long offered a library export that generates a CSV file.

That file is one reason moving from Goodreads to another reading tracker can be relatively practical.

Services such as MyBibliotheca can accept Goodreads exports and use them to rebuild supported parts of your library.

Goodreads may not offer every tracking feature a reader wants, but its export capability is meaningful.

Fable: easy to bring Goodreads data in

Fable provides Goodreads import options.

Its documentation explains direct Goodreads import and a CSV import workflow.

That lowers friction for Goodreads users moving into Fable.

But as of this article's verification date, Fable's public help center does not list a normal self-service reading-library export feature.

Its privacy policy provides eligible users with access and portability rights under applicable law, including the possibility of receiving personal information in a structured, machine-readable format.

That is valuable.

But it is not the same user experience as clicking Export library inside the product.

MyBibliotheca: import and export are both part of the product

MyBibliotheca was built with movement in both directions.

You can import supported data from:

• Goodreads
• StoryGraph
• CSV files

And you can download supported reading data including books, ratings, notes, dates, and reading logs.

The purpose is not merely backup.

It is to make your reading history portable enough that using MyBibliotheca does not become a one-way commitment.

Comparison at a glance

Capability	Goodreads	Fable	MyBibliotheca
Goodreads import	N/A	Yes	Yes
StoryGraph import	Not a core migration feature	Not prominently documented	Yes
Self-service reading-library export	Yes, CSV	Not currently documented in public help center	Yes
Privacy/data access rights	Depends on applicable law	Yes, where applicable	Yes, where applicable
Private-by-default personal ledger	Social-oriented	Social reading platform	Yes
KOReader progress sync	Not a core feature	Not publicly documented	Yes
KOReader highlights/notes	Not publicly documented	Not publicly documented	Yes
Readwise import	Not a core reading-history integration	Not publicly documented	Yes

Features change. Always verify current documentation before choosing a service based on a single capability.

Portability is not the same as privacy

These concepts are related but separate.

Privacy asks:

Who can see or use my reading data?

Portability asks:

Can I take my reading data somewhere else?

A service can have strong privacy controls but weak migration tooling.

It can also have excellent exports while being highly social.

Readers should evaluate both.

Why MyBibliotheca emphasizes both

MyBibliotheca is designed as a personal reading ledger rather than a social network.

That changes the priorities.

The core experience focuses on:

• current books
• reading sessions
• audiobook minutes
• reading history
• notes
• highlights
• series
• TBR planning
• personal statistics

Your library is private by default.

And because the history is meant to belong to you, export is part of the product.

Integrations reduce another kind of lock-in

There is also ecosystem lock-in.

A tracker becomes harder to leave when every part of your reading process has to happen inside it.

MyBibliotheca works with external tools.

KOReader can send reading progress.

The MyBibliotheca KOReader plugin can send highlights and notes.

Readwise can remain your annotation source while MyBibliotheca imports a copy into your library.

This lets readers build a reading stack instead of surrendering everything to one platform.

Check the exit door before the library gets huge

Nobody joins a reading app because they are excited about leaving.

That is exactly why exit features are easy to ignore.

But people may use reading trackers for 5, 10, or 20 years.

A small portability limitation today can become a major problem after thousands of records accumulate.

So before choosing a platform, check the exit door.

Different platforms, different priorities

Goodreads remains powerful for its public review ecosystem.

Fable emphasizes social reading, clubs, discovery, and community.

MyBibliotheca emphasizes private reading history, integrations, deeper tracking, and portability.

Different readers will value different things.

But regardless of which platform you choose, your reading history should not become difficult to preserve simply because you were loyal enough to build a large one.

Try MyBibliotheca and bring your Goodreads or StoryGraph history into a reading tracker designed to let you take it back out again.

Sources

• Fable Reader Support
• Fable Goodreads CSV Import
• Fable Privacy Policy
• MyBibliotheca Help Center
• MyBibliotheca Privacy Policy

The One-Way Import Problem: Why Book Apps Should Make Leaving as Easy as Joining

There is a simple test for any app that wants years of your personal data.

Look at how easy it makes two actions:

Join.

Leave.

If importing your old library takes three clicks but exporting the new one requires a support conversation, a legal request, or manual copying, the product has an asymmetry.

Data flows easily toward the platform.

It does not flow as easily away from it.

For a reading tracker, that should matter.

MyBibliotheca is intentionally designed to support both directions: bring a reading history in, build on it, and download your data again when you need it.

Imports are good product design

To be clear, importing is useful.

Nobody wants to manually re-enter 600 Goodreads books.

A good importer can preserve years of reading statuses, ratings, dates, notes, and book records.

MyBibliotheca provides imports for Goodreads, StoryGraph, and general CSV files for exactly that reason.

Fable also provides Goodreads import functionality.

The problem begins when import is treated as acquisition while export is treated as an edge case.

Reading trackers are unusually sticky

A reading tracker can contain decades of history.

The longer you use it, the harder switching becomes.

Not because the interface is impossible to replace.

Because the history is difficult to replace.

This creates switching costs.

Some switching cost is natural.

Moving data takes effort.

But a platform should not make that cost unnecessarily high by failing to provide practical export tools.

One-way migration creates dependency

Suppose Platform A lets you import Goodreads.

You move 800 books into it.

Over the next five years you add:

• 300 more books
• 200 ratings
• dozens of lists
• 1,000 highlights
• reading goals
• personal notes
• progress history

Now you discover Platform B fits your reading habits better.

If Platform A does not provide a convenient structured export, your original Goodreads history may be portable while the five years you added afterward are much harder to migrate.

That is the one-way import problem.

Fable is a useful current example

Fable currently documents Goodreads import tools.

As of September 26, 2026, its public support center does not document a general self-service reading-library export comparable to Goodreads' CSV export or MyBibliotheca's account-data export.

Fable's privacy policy separately grants eligible users important data-access and portability rights under applicable laws.

Those legal rights matter.

But a reader should not need to understand privacy statutes just to back up a book list.

Portability is strongest when it is both a legal right and a normal product feature.

Goodreads gets this part right

Goodreads provides a CSV export.

That does not settle every question about Goodreads.

Readers may still want different privacy defaults, better audiobook history, deeper stats, a modern TBR, or KOReader integrations.

But giving users a practical way to download their library is valuable.

Competitors should meet or exceed that baseline.

MyBibliotheca treats export as normal

MyBibliotheca includes export because readers should not have to justify wanting a backup.

You may want a copy because:

• you are switching apps
• you are building a personal database
• you want an offline archive
• you want to inspect your own data
• you simply believe backups are sensible

All of those are legitimate.

A reading tracker should not interpret export as a breakup.

Open integrations reduce lock-in further

MyBibliotheca also connects with tools outside its own application.

That includes:

• KOReader progress sync
• direct KOReader highlights and notes
• Readwise imports

This matters because lock-in does not only happen at the database level.

It also happens when one service tries to become the only place every part of your workflow can exist.

MyBibliotheca's approach is closer to:

Use the tools you like. Let your reading history connect them.

What a reader-first migration policy looks like

A healthy reading platform should make these four things straightforward:

Import

Bring your history from another service.

Export

Download your current history in a structured format.

Backup

Create a copy even when you have no intention of leaving.

Integrate

Let other tools participate without forcing everything into one closed ecosystem.

If a platform supports only the first item, portability is incomplete.

Do not wait until your library is huge

This is easiest to evaluate on day one.

Before committing to a new tracker, ask:

If I add 2,000 books here, how do I get 2,000 books back?

Search the help center.

Look for a real export page.

Check what fields are included.

If the answer is vague, treat that uncertainty as part of the product decision.

A good app earns retention instead of manufacturing it

MyBibliotheca would rather give readers reasons to stay:

• useful reading logs
• audiobook tracking
• KOReader integration
• highlights
• private TBR tools
• timelines
• detailed stats
• private-by-default design

than make leaving painful.

Importing should be easy.

Exporting should be easy too.

Build your library in MyBibliotheca and keep an exit door open from the beginning.

Sources

• Fable Goodreads CSV Import
• Fable Privacy Policy
• Fable Reader Support
• MyBibliotheca Help Center
• MyBibliotheca Privacy Policy

Before You Spend 10 Years in Another Book App, Ask These 7 Data Ownership Questions

Choosing a reading tracker feels like a small decision.

It is not.

If the app works, you may still be using it ten years from now.

By then it could contain hundreds or thousands of books and an irreplaceable history of what you read.

Before committing to Goodreads, Fable, StoryGraph, MyBibliotheca, or any other reading service, evaluate more than the interface.

Ask how the platform treats your data.

MyBibliotheca was built around this exact concern: private-by-default tracking, imports from other reading services, integrations with tools such as KOReader and Readwise, and the ability to export your reading data again.

Here are seven questions worth asking before you invest years in any tracker.

1. Can I export my library without contacting support?

This should be the first question.

Not:

Does the company legally recognize my data rights?

That matters too.

But the practical product question is:

Is there a button that gives me my reading history?

Goodreads provides a CSV library export.

MyBibliotheca provides an account-data export.

StoryGraph publicly supports data export.

As of September 26, 2026, Fable's public help center documents Goodreads imports but does not document a comparable self-service reading-library export.

Fable's privacy policy separately provides eligible users with legal access and portability rights.

Those are two different things.

For a long-term reading archive, a self-service export is preferable.

2. What is actually included in the export?

An "Export" button is only as useful as the data it contains.

Look for fields such as:

• titles
• authors
• ISBNs
• editions
• shelves or statuses
• ratings
• reviews or notes
• start dates
• finish dates
• reading logs
• progress
• tags

A bare list of titles is better than nothing.

But it is not a complete reading history.

MyBibliotheca's documentation says its export can include books, ratings, notes, dates, and reading logs.

That makes the file useful as both a backup and a migration source.

3. Is my library private by default?

Privacy defaults matter because most users never change every setting.

Fable describes itself as a social reading platform, and its support documentation says lists are public by default unless changed to private.

Goodreads is also fundamentally social.

StoryGraph offers substantial privacy controls.

MyBibliotheca begins with a private library.

There is no required social feed.

Public sharing is something you deliberately enable.

Neither model is inherently right for everyone.

But you should know which one you are choosing.

4. Does the platform work with other tools?

A reading tracker becomes more useful when it does not insist on owning the entire workflow.

For example, MyBibliotheca connects with:

• KOReader progress sync
• KOReader highlights and notes
• Readwise highlights and notes

That means your e-reader or annotation service can remain useful on its own.

The tracker becomes a hub rather than a closed island.

This is particularly important if you use Kobo, PocketBook, Kindle with KOReader, or several reading formats.

5. Can I import the history I already have?

Portability works in both directions.

A new tracker should not require you to abandon the past.

MyBibliotheca supports Goodreads and StoryGraph imports.

Fable supports Goodreads imports.

This matters because a good new system should improve your future reading history without erasing the old one.

6. What happens if the company changes direction?

Software companies change.

They are acquired.

They launch subscriptions.

They remove features.

They shift product focus.

Fable, for example, now operates alongside Everand and offers Fable Plus features in addition to its free experience.

None of that automatically makes a service bad.

It simply illustrates why readers should avoid designing their personal archive around the assumption that today's product will remain identical forever.

An export gives you optionality.

7. If I stop using the service tomorrow, what do I still have?

This is the final test.

Imagine the account disappears from your daily routine tomorrow.

What remains under your control?

Do you have:

• a recent library export?
• your notes?
• ratings?
• dates?
• reading logs?
• highlights?
• enough metadata to rebuild elsewhere?

If the answer is "nothing unless I log back into the app," you do not have a durable archive.

You have access to a database controlled by someone else.

How MyBibliotheca answers the checklist

MyBibliotheca is deliberately designed around long-term personal reading history.

Import

Bring in Goodreads, StoryGraph, or supported CSV data.

Export

Download your reading data when you want a copy.

Privacy

Your library is private by default.

Integrations

Connect KOReader progress, KOReader annotations, and Readwise highlights.

Deep tracking

Keep pages, percentages, audiobook minutes, reading sessions, dates, notes, series, editions, and TBR information.

No required social feed

The dashboard is designed around your reading rather than engagement with other users.

A reading tracker is an archive in disguise

It is easy to choose an app based on what looks nicest today.

But the more successful the tracker becomes in your life, the more important its data policies become.

Ten years from now, you are unlikely to care which service had the trendiest onboarding screen in 2026.

You may care very much about whether you can still access ten years of reading history.

Choose accordingly.

Start a private MyBibliotheca library and keep your reading history portable from day one.

Sources

• Fable Privacy Policy
• Fable Reader Support
• Fable: Are my lists public?
• MyBibliotheca Help Center
• MyBibliotheca Privacy Policy

KOReader already knows where you stopped reading. Goodreads can show that you are reading a book, but its own integration with KOReader does not keep that progress updated for you.

As of September 26, 2026, community-made plugins offer another route. ShelfSync lists KOReader progress syncing for Goodreads, but says Goodreads uses an unofficial session-cookie API that may break when the site changes. Its README also notes Goodreads cannot send a current page position back to KOReader. Check the plugin’s current setup and limitations before relying on it.

As of September 2026, Goodreads’ public help materials do not document a native KOReader connection. KOReader’s built-in Progress Sync shares a reading position between KOReader devices; it does not, by itself, post that position to Goodreads.

If you want your ebook progress recorded automatically alongside the rest of your reading history, MyBibliotheca connects KOReader with your personal library.

What happens when you use KOReader and Goodreads together?

You can still open Goodreads and update a book manually. That works if you remember to do it after each session. Without a separate syncing plugin, KOReader and Goodreads are separate systems, so your Goodreads percentage can fall behind your actual reading.

This is especially easy to miss when you read across a Kobo, PocketBook, Kindle, or another device running KOReader. KOReader can sync the document position between supported KOReader devices, but Goodreads is not the destination for that sync.

Keep KOReader progress with your reading history

MyBibliotheca can receive KOReader progress and connect the ebook to a book in your library. Once the correct title is linked, future progress can be part of your private reading record.

If an ebook’s title or edition is unclear, you can confirm the match yourself. That helps keep progress attached to the right translation or edition.

You can also send KOReader highlights and notes through a separate MyBibliotheca plugin. Progress tells you where you stopped. Highlights preserve what you wanted to remember.

You do not have to throw away years of Goodreads history to change your workflow. Import your existing library into MyBibliotheca, then let KOReader update your reading record going forward.

Ready to stop re-entering your ebook progress? Start your MyBibliotheca library.

Cover image: Bookshelves with books in a library (JPG, public domain) · Public-domain source and license