The One-Way Import Problem: Why Book Apps Should Make Leaving as Easy as Joining
8 minutes read
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.