Import & Export
Bring bookmarks, feeds, documents, transcripts, calendars, and backups into Arivu, then export portable knowledge or restore a full account backup.
Imports enter the same Library as ordinary captures. Documents and transcripts become notes, while full JSON backups preserve durable account knowledge for restore.
Bookmark and Feed Imports
Settings accepts browser bookmark HTML, an Arivu JSON backup, one URL per line, OPML, RSS or Atom, and URL-bearing CSV or TSV files. Common Pocket, Raindrop, Linkwarden, Readwise, and Kindle-style exports work when their fields can be mapped.
Import jobs run in the background and report fetched, processed, skipped, and failed items. Arivu records source provenance, deduplicates normalized URLs, and rejects unsafe URLs before creating bookmarks.
OPML and RSS or Atom imports are one-time capture sources. For ongoing intake, add a private RSS or Atom subscription in Settings Automation, then pause, resume, inspect, or delete it. Accepted entries use the normal Inbox and capture pipeline.
Documents and Transcripts
Supported sources include EPUB, extractable PDF text, plain text, Markdown, HTML, pasted transcript text, and pasted OCR text. Optional provider-backed image OCR is available when configured. Imported material becomes a searchable note that can be linked, graphed, reviewed, and exported.
Calendar ICS imports create meeting objects that can sit beside notes, decisions, reminders, and sources.
Export Formats
| Format | Best for |
|---|---|
| JSON | Full Arivu backup and restore |
| Obsidian ZIP | Vault-ready Markdown files |
| Markdown | Portable notes and links |
| CSV | Spreadsheets and data tooling |
| Browser HTML | Browsers and bookmark managers |
Full JSON includes durable bookmarks, summaries, notes, daily notes, objects, explicit links, annotations, tasks, reminders, review state, collection hierarchy and membership, result and knowledge feedback, import provenance, and X metadata. Derived graph relationships and Insights can be rebuilt; their durable feedback is restored separately.
Restore remaps owned identifiers under the importing account while preserving supported relationships and provenance.
Audit and Repair Derived Knowledge
Before repair, complete any pending X sync, create a verified backup, and then run a quality audit. Keep the backup until you have reviewed the repaired account.
arivu quality audit --db arivu.sqlite3 --format json
arivu reprocess --db arivu.sqlite3 --stale-version --dry-run --user-id USER_ID
arivu reprocess --db arivu.sqlite3 --status RUN_ID
The dry run previews stale derived work for one user. Repair preserves user-authored notes, annotations, and explicit links. It rebuilds only eligible derived material, and incomplete evidence can correctly result in no generated output.
Legacy Migration
Validate a legacy JSON export first:
./arivu migrate --json-export legacy-export.json --dry-run=true
Apply it after review:
./arivu migrate \
--json-export legacy-export.json \
--sqlite-db arivu.sqlite3 \
--old-secret-key "$OLD_SECRET_KEY" \
--new-secret-key "$SECRET_KEY" \
--dry-run=false
API Routes
| Method | Endpoint | Purpose |
|---|---|---|
POST |
/api/bookmarks/import |
Import bookmarks or restore JSON |
GET |
/api/bookmarks/export |
Export supported formats |
POST |
/api/bookmarks/backup |
Create a full JSON backup |
POST |
/api/media/import |
Import documents, transcripts, or OCR text as notes |
POST |
/api/calendar/import |
Import calendar events as meeting objects |
GET |
/api/import-jobs |
List import jobs |
GET |
/api/import-jobs/{id} |
Inspect import progress |
For host-level recovery, keep installer-managed backups and the secrets needed to run the instance. Installer backups pair a SQLite-consistent snapshot with the adjacent asset store except staging and write a versioned size/hash manifest that restore verifies. Full JSON remains the portable account-level format and does not replace that asset-aware host backup.