How to Migrate Your Feed Reader With OPML
TL;DR
OPML is a simple file format that packages all your RSS subscriptions so you can move them between readers in one import. Export from your old app, import into the new one, and your feeds and folders come along for the ride.

Switching feed readers feels like it should be painful. You have dozens — maybe hundreds — of subscriptions, carefully sorted into folders, built up over years. The fear of rebuilding all of that by hand is often the only thing keeping people on an app they've outgrown.
Here's the good news: you almost never have to rebuild anything. A small, boring file format called OPML does the heavy lifting, and nearly every serious reader supports it.
In this guide you'll learn what OPML actually is, how to export and import it, what can go wrong during a migration, and how to pick a reader that won't lock you in next time.
What OPML Actually Is
OPML stands for Outline Processor Markup Language. It's a plain-text XML file designed to store nested outlines — and it turns out a list of feed subscriptions sorted into folders is exactly that: an outline.
When you export your subscriptions, your reader writes every feed's title and URL into a single .opml file. Folders become nested outline nodes, so your "Tech," "News," and "Design" groupings travel with the feeds inside them.
The format has been around since the early 2000s and was formalized alongside the rise of RSS itself. It's documented publicly by the OPML specification, and that stability is exactly why it still works across apps that were built decades apart.
The practical upshot: OPML is portable. One file holds your entire subscription graph, and any compliant reader can read it back. You own that file. If a service shuts down — as Google Reader famously did in 2013, stranding millions of users and sparking a wave of feed-reader alternatives — your OPML export means your subscriptions survive the app that held them.
Exporting Your Subscriptions
Before you can import anywhere, you need to get the file out of your current reader. The wording varies, but the option is almost always there.
Where to look
Most readers tuck OPML export into Settings → Account, Import/Export, or a Subscriptions menu. Look for a button labeled "Export OPML," "Export subscriptions," or simply "Backup."
A few popular examples:
- Feedly: Organize → the gear or "Export to OPML" under your account settings.
- Inoreader: Preferences → Import/Export → Export your subscriptions.
- NetNewsWire and most desktop apps: File → Export Subscriptions.
Click export, and your browser downloads a .opml file — often named something like subscriptions.opml. Save it somewhere you'll remember. It's small, usually just a few kilobytes even for a large library, because it stores links and titles, not article content.
One habit worth building: export an OPML backup every few months regardless of whether you're migrating. It's the cheapest insurance you'll ever buy against a service outage or a surprise shutdown.
Importing Into a New Reader
Importing is the mirror image of exporting, and it's usually even faster.
Open your new reader, find the matching Import option — again, typically under Settings, Import/Export, or an onboarding "Add subscriptions" step — and select the .opml file you saved. The reader parses it, recreates your folders, and begins fetching each feed.
Within a minute or two, your subscriptions reappear, grouped the way you left them. The new app then pulls the latest articles from each feed, so you're reading again almost immediately.
What transfers and what doesn't
It's important to set expectations. OPML carries the structure of your subscriptions — feed URLs, titles, and folder hierarchy. That's it.
What OPML does not carry:
- Read/unread state
- Starred, saved, or tagged articles
- Highlights and personal notes
- Per-feed rules or filters you configured
Those live in each service's own database, not in the portable file. If keeping highlights and annotations matters to you, that's a reason to pick a reader that stores them durably and lets you export them too — not just the subscription list.
When Migrations Go Sideways
Most OPML transfers are uneventful. But a few predictable issues trip people up, and they're all fixable.
Dead or redirected feeds
Over years of subscribing, some feeds go offline, change domains, or move platforms. After import, your new reader may flag a handful as unreachable. That's not always a sign the feed is actually dead — a redirect the old reader handled silently, or an access requirement the new one doesn't have yet, can also trigger the flag. Before removing anything, check the feed's current URL in a browser and confirm it isn't simply gated behind a login the new reader needs set up. Only prune the ones that are genuinely gone.
Duplicate subscriptions
If you import the same OPML file twice, or import into an account that already has feeds, you can end up with duplicates. Import once into a clean account, and check your folder counts before and after to confirm the numbers line up.
Giant libraries and rate limits
If you follow thousands of feeds, some readers throttle how fast they fetch to avoid hammering servers. The import itself completes quickly, but populating every feed with fresh articles can take a little while. Healthy feed fetching respects each site's bandwidth — the kind of courteous polling encouraged by guidance like Mozilla's overview of RSS. Give it an hour and everything settles.
Encoding quirks
Occasionally a feed title with unusual characters imports oddly. It's cosmetic — the underlying URL still works — and you can rename the feed in a few seconds.
Choosing a Reader You Won't Have to Leave
Migration is easiest when you only have to do it once. The best way to avoid serial migrations is to pick a reader that respects your ownership of your data and matches how you actually consume content.
A few questions worth asking before you commit:
- Does it support OPML export, not just import? Import-only is a warning sign. You want to be able to leave.
- Can it do more than display text? Many people subscribe to far more than they'll ever read. A reader that lets you listen to articles turns a backlog you feel guilty about into something you can clear on a walk or commute.
- Does it handle the rest of your inputs? Newsletters, YouTube channels, and podcasts are feeds too. A reader that unifies them beats juggling four apps.
This is where Omphalis fits in. It's built as a modern rss feed reader with OPML import, so moving your subscriptions over is a single step — and it unifies RSS, newsletters, and podcasts in one place so you stop context-switching between apps.
Omphalis also leans into the reality that people collect more than they consume. You can read articles by listening with natural voices, highlight and annotate web articles you want to remember, and get a daily audio brief of what's new — so your reading backlog becomes something you can work through instead of a source of guilt.
If your goal is simply to stop losing feeds every time an app shuts down, that combination of open import, durable annotations, and listen-anywhere playback is what makes a reader worth settling into.
The Bottom Line
OPML turns what sounds like a dreaded chore into a two-step task: export one file from your old reader, import it into your new one, and your feeds and folders come along intact. Just remember that read state, stars, and highlights stay behind — so choose a new home that stores that history durably and lets you export it, too.
If you're ready to move your subscriptions somewhere that lets you both read and listen, Omphalis imports your OPML in seconds and helps you finally work through everything you've been saving.