The email usually lands on an ordinary weekday: your read-it-later app is closing, and you have a few weeks to get your data out. If your queue holds hundreds of links, the notice feels oddly personal, because that pile is a record of what you were curious about.
The good news is that a closing read-it-later app rarely means lost data, provided you act before the deadline. Here is a calm way to handle it.
Export first, shop later
Resist the urge to compare each new read-it-later app right away. Deadlines are real, and export tools are sometimes slowed down or removed in the final weeks when servers get busy.
Look in your account settings for words like export, backup or download your data. Most services offer an HTML bookmarks file, a CSV spreadsheet, a JSON file, or some mix of them. Download everything on offer, even if it looks redundant, then open the files and check them. Does the count roughly match your library? Are tags there? Highlights and notes are the thing people forget most often, and some exports leave them out entirely. If yours does, copy the important ones by hand before the account closes.
Keep the raw export in two places, say a cloud folder and a local drive. Treat it as your master record, whatever you do next. A plain CSV file is especially handy because any spreadsheet can open it.
Links are not the same as articles
Many people assume a read-it-later app export contains their saved pages. Often it contains only the web addresses. That matters, because pages move, get rewritten or vanish behind paywalls. If your read-it-later app kept a clean text copy, that copy may be the only surviving version of something you saved years ago.
Check whether the export includes full text. If it does not, be selective. Running ten thousand links through a web archiving service is a waste of an evening, but archiving the fifty you cite or reread is not.
Here is a useful exercise: sort the library by age and be honest. Articles you saved three years ago and never opened will not suddenly become urgent after the move. Many people discover that migration is the best excuse they will ever get to delete most of the backlog.
Pick a read-it-later app that fits how you read
Before comparing features, ask what you actually used your old read-it-later app for. A commuter who sends links from a phone needs a good share button and offline reading. A researcher who highlights and tags needs strong search and annotation. Someone who barely opened the app may be happy with the reading list built into their browser. And a note-taker may be better served by a general notes tool than by a dedicated reader.
Whichever way you lean, ask four questions. Can it import the format your old service produced? Can you export from it later in an open format? Does the way it earns money look durable? Does it run on every device you use?
The money question deserves honest thought. Any read-it-later app can close because the business did not work or the owner changed priorities. A tool with clear subscription revenue is usually a safer bet than a free one with no visible means of support, though neither is a guarantee. Self-hosted and open-source options trade convenience for control, and if you are comfortable running a small server, they remove the risk of someone else pulling the plug. If you went through a similar scramble with other business software, our checklist on what to do when a cap table tool shuts down follows much the same logic.
Test a small import before the big one
Do not push the whole library across in one go and hope for the best. Import a sample of fifty to a hundred items into your top choice and inspect the result. Common problems include tags merged into one long label, every date showing as today, duplicate entries, missing titles that leave bare web addresses, and highlights that failed to carry over.
If the test goes badly, clean up the file first. A spreadsheet is ideal for this, since you can fix titles, delete duplicates and trim tags before trying again. If it goes well, import the rest and keep the old account open until you have confirmed everything arrived.
Rebuild the habit, not just the library
A migration is a chance to fix whatever was not working. If your old list was a guilt pile, set a rule this time. Some people cap the queue at a number they can honestly read. Others do a short weekly review and archive anything older than a month.
Then make the new read-it-later app part of a real routine. Install the browser extension, add the share option on your phone, and test saving one article from each device today. Teams facing a bigger version of this problem, a whole shared chat history rather than a personal list, can borrow the steps from our guide to migrating when a workplace chat tool closes.
To sum up: export today, verify the files, trim the backlog, test a small import, and only then commit to a new home. Keep the original export for at least a year, even after the new read-it-later app feels like home. Your future self, hunting for that one article about something half remembered, will be glad you did.
