Keep the source export and define a small trial
Start by exporting from the browser or app that currently owns the bookmarks. Keep an untouched copy with its export date. Raindrop.io documents support for HTML, CSV, JSON, TXT, and ENEX, with source-specific qualifications. An available format does not mean every note-taking record or attachment in the source becomes a bookmark.
For an original fictional research library, choose a few harmless links: an onboarding reference, a pricing reference, and one repeated URL. Write down the titles, folder paths, notes, and tags you expect. A small sample makes it easier to identify a changed field without confusing a successful upload with a complete migration.
Review the import summary before starting
Upload the sample on the Import page and inspect the detected counts. Confirm whether the file expresses the folder and annotation structure you intended. Keep the browser tab open while the upload finishes. Separate the upload from later background processing of thumbnails or other enrichment; those are different observations.
Use the original file as evidence when a count looks unexpected. Ask whether a repeated URL was skipped, an unsupported record was excluded, or the source export omitted the item. Avoid rerunning the entire library immediately: a second upload can make the situation harder to interpret without answering which assumption was wrong.
| Sample item | Expected observation | Result to record |
|---|---|---|
| Unique reference URL | A reachable bookmark with the intended title | Imported item and source-row match |
| Nested source folder | An understandable collection path | Actual collection placement |
| Two topic labels | Both labels remain useful for retrieval | Actual tags and spelling |
| Repeated saved URL | Skipped item is explained rather than overwritten | Import summary and retained metadata |
| Exported sample | The chosen format preserves the required fields | Actual export contents |
Organize with collections and tags deliberately
Raindrop.io describes a bookmark as belonging to one collection, while tags can give it several labels. Collections can be nested. For the fictional library, a collection might identify the Research project while tags identify onboarding and pricing as subjects. Keep one convention for each purpose so that the import does not reproduce an unclear filing system.
After the trial, find a reference by its project and then by a subject tag. Check whether a teammate would understand why it appears in each place. If a bookmark needs several retrieval paths, multiple labels may be clearer than saving several copies merely to put it under different folders.
Verify an export before retiring the old library
Export the reviewed collection in the format the next destination requires. Raindrop.io offers HTML, CSV, and TXT exports; its backup documentation treats uploaded files separately from the ordinary bookmark backup. A list of URLs, a structured bookmark file, and a copy of original uploaded documents serve different recovery needs.
Inspect the actual export for the fields you care about, then keep it beside the untouched source file. For a larger migration, record the accepted differences before abandoning the old system. The useful milestone is being able to retrieve and interpret the references, not simply seeing an import-complete message.
Does importing the file again update existing bookmarks?
The import documentation says existing bookmarks are skipped rather than overwritten. Treat an import as a transfer of new items, not a bulk editing mechanism. Review the retained item's metadata and choose a deliberate editing process for corrections. Preserve the source before considering any replacement workflow.
Why do two similar links count as duplicates?
Raindrop.io's duplicate documentation describes URL normalization, including differences such as protocol, tracking parameters, and fragments. Two differently written source links may identify the same saved page. Inspect the retained URL and its context before removing anything; a duplicate count is a prompt to understand the library, not an instruction to delete references blindly.
Sources and editorial method
Official sources linked throughout this guide were checked on October 29, 2026. Product editions, interfaces, plans, and limits can change. The examples and evaluation exercises are editorial proposals, not reports of hands-on product testing or customer results. Confirm the current documentation for your account before implementing a workflow.