Make an application-aware backup before exporting for a new destination. Recoverable files, catalog records, and annotations are separate deliverables; verify each before shutting the old server down.
Inventory the moving parts
List ebook directories, application databases, configuration, and annotation stores. Record which reader owns each kind of data. A container image is not a backup of the mounted library or database.
Export a neutral reading copy
Keep original files and a portable catalog alongside the application backup. That gives you both a recovery route and a destination-independent record. Avoid changing file names during the first migration pass.
Retire access in stages
Switch your reading workflow only after the destination passes the pilot. Keep the old service recoverable while you verify exports. Retire remote access and credentials when the migration is truly complete.
The details, at a glance.
| Consider | What to look for |
|---|---|
| Application backup | Rebuild the old environment if needed |
| Original files | Preserve independently of the server |
| Catalog export | Retain organization in a portable form |
| Reader state | Export notes and capture current locations |
A few things worth asking.
Is my server backup enough for another service?
It may restore the original software but may not be importable elsewhere. Keep neutral files and records too.
Should I rename files while migrating?
Avoid combining unrelated cleanup and migration steps. Fewer simultaneous changes make errors easier to trace.
Go to the source
Documentation consulted for the routes and terminology on this page. Product behavior can change; verify your exact setup.
Calibre-Web project and feature documentationWritten by Binge Reader. Our comparisons explain documented workflows and practical tradeoffs; they are not independent product benchmarks.