Preserve a Pocket or Omnivore export by keeping the raw file unchanged, making a working copy, auditing URLs and duplicates, verifying a manual sample, and mapping only current material into a new workflow. Do not let the new app become the only copy of your archive.
Pocket shut down on July 8, 2025. Omnivore joined ElevenLabs in 2024 and is no longer an active read-later destination. These exports are records from closed systems, so preservation comes before migration convenience.
Create a raw archive package
Put the original export in a clearly named folder that includes the product and export date. Keep at least two copies in different locations. If the export arrived as a compressed file, preserve both the original archive and the extracted folder.
Do not edit the raw HTML, CSV, JSON, Markdown, or media files. If documentation explains the export fields, save that page or text beside the package. Future tools may understand metadata that a current importer ignores.
Create a separate working copy for cleanup. This protects against accidental data loss and makes it possible to retry with a better parser later.
Audit URLs and obvious duplicates
Use SauceTab's local bookmark export auditor for a quick count of detected URLs, unique URLs, duplicates, and dominant domains. The file is processed in the browser and is not uploaded to SauceTab.
The tool is intentionally simple. It does not guarantee complete support for every historical export shape, annotation, or attachment. Compare its count with any totals in the source product and manually inspect the file when the numbers differ.
Duplicate URLs may still carry different notes, tags, or highlights. Deduplicate only after checking metadata. Normalize tracking parameters in a working copy, never in the raw archive.
Verify a representative sample
Select at least twenty entries across different years, domains, tags, and content types. Open the source URL, confirm the title, and check whether highlights or notes survive in the export. Include a page that has moved, a deleted page, a PDF, a newsletter, and a saved video if those formats appear in the archive.
For dead links, record the original URL before trying an archive service. The source address is evidence even when the page no longer loads.
Separate archive value from project value
A read-later archive often contains three groups: active sources, durable references, and abandoned intentions. They should not all enter the same destination.
Move active sources into a project research system, durable references into a bookmark library, and keep low-value historical items in the preserved export. This reduces migration work and prevents a new knowledge system from starting with years of retrieval noise.
The Pocket alternatives and Omnivore alternatives guides explain which products fit reading, bookmarking, highlighting, summary review, and project research.
Test the destination with one project
Choose one current project and move ten verified sources. Ask a broad question, find a specific passage, export a sample, and confirm that the original URL remains available. Repeat the same test in a second candidate before committing.
SauceTab does not currently bulk import Pocket, Omnivore, HTML, or CSV archives. If SauceTab fits the active project, capture the relevant sources deliberately through the browser and keep the complete raw export elsewhere.
Keep a migration log
Record the source export date, backup locations, tools used, cleanup steps, destination, number of moved items, and any known losses. Include screenshots or small samples when a format does not transfer correctly.
The log turns a one-time migration into a recoverable process. If a destination changes its export format or shuts down later, you will know which copy is authoritative and what was transformed.
The goal is not to force every old save into a new product. It is to preserve the evidence, protect future options, and move only the material that supports work you still intend to do.