Linkwarden Migration Guide: Pocket, Raindrop, and Pinboard to Self-Hosted Bookmarks 2026

TL;DR

Linkwarden is the best fit when your bookmarking problem has moved beyond saving links. It gives teams and individuals a self-hosted archive for bookmarks, tags, collections, web page preservation, and long-term ownership. If Pocket is too consumer-oriented, Raindrop is too tied to a hosted account, or Pinboard no longer fits your workflow, Linkwarden is a credible open source migration target.

The migration is straightforward if you treat it as an information-architecture project instead of a one-click import. Export everything first, clean the tag model, decide which collections matter, then import into a staged Linkwarden instance before making it your daily capture tool.

Who should migrate to Linkwarden?

Linkwarden is strongest for people who care about durable reference libraries:

• researchers building a source archive;
• engineering teams saving vendor docs, API references, and architecture notes;
• agencies collecting client research and competitor links;
• operators who want bookmark data in their own database and backup flow;
• teams that want shared collections without moving every saved link into a proprietary SaaS workspace.

If you only need a private read-it-later queue, a browser reading list may be simpler. If you need shared, searchable, self-hosted bookmark knowledge, Linkwarden is the more interesting choice.

Migration checklist

Step	What to do	Why it matters
Export	Download Pocket, Raindrop, or Pinboard data before touching the source account	Gives you a rollback point and an audit trail
Normalize	Review duplicate URLs, throwaway tags, and private notes	Prevents clutter from becoming permanent
Design collections	Map old folders/tags to Linkwarden collections	Makes the new archive easier to browse
Test import	Use a staging collection first	Catches malformed URLs and tag surprises
Back up	Add database and upload storage backups	Self-hosting only helps if recovery is real

Pocket to Linkwarden

Pocket exports are usually the easiest to reason about because most users have a simple saved/read/archive model. Start by exporting your Pocket list, then split it into active reading, long-term reference, and discard groups. Do not import years of unread links blindly. Pocket accounts often contain hundreds of stale articles that will dilute search quality.

A useful pattern is to create three Linkwarden collections: Inbox, Reference, and Archive. Import recent unread items into Inbox, evergreen sources into Reference, and older saved material into Archive only if you actually expect to search it later.

Raindrop to Linkwarden

Raindrop migrations need more tag discipline. Many Raindrop users rely on nested collections, visual previews, and casual tags. Before importing, export your data and decide which collection hierarchy should survive. Linkwarden can handle organized collections, but it should not inherit every abandoned experiment.

Pay special attention to shared collections. If a Raindrop collection was collaborative, decide whether it becomes a Linkwarden team collection, a private collection, or a one-time archive. This is also the moment to remove duplicate tags such as js, javascript, and frontend if they mean the same thing in your library.

Pinboard to Linkwarden

Pinboard users usually have the cleanest portable data but the roughest tag history. A decade of flat tags can be powerful, but it can also create noisy search. Export all bookmarks, then group tags by current workflow: projects, technologies, clients, and reference types.

If you used Pinboard private bookmarks heavily, test privacy expectations carefully in Linkwarden before inviting collaborators. A self-hosted tool still needs clear collection boundaries and access rules.

Self-hosting decisions

Before switching daily capture to Linkwarden, decide how it will be operated:

• where the app and database run;
• who applies upgrades;
• how often database backups run;
• whether archived page assets are backed up separately;
• how users authenticate;
• who can create shared collections;
• what happens if the host is offline when someone needs to save a link.

For most small teams, the right first deployment is boring: one small server, managed DNS, automated database backups, a documented upgrade command, and a monthly restore test.

Common mistakes

The biggest mistake is importing everything and calling the migration done. Bookmark tools are only useful when retrieval works. If the new archive starts with thousands of stale links, the team will stop trusting it.

The second mistake is ignoring backups. Linkwarden gives you control, but control includes responsibility for the database and stored page snapshots. A self-hosted bookmark archive without restore testing is just another fragile SaaS dependency with extra steps.

The third mistake is over-designing collections on day one. Start with a small set of durable collections, then let real search behavior tell you which categories deserve structure.

Verdict

Choose Linkwarden if you want bookmark ownership, shared collections, and an archive that can live inside your self-hosted stack. Pocket users should prune aggressively before import. Raindrop users should simplify collections and tags. Pinboard users should preserve the best of their tag model while cleaning old noise.

The best migration is not the largest import. It is the one that leaves you with a smaller, searchable, backed-up knowledge library that your team will actually use.