Skip to main content

Data migration

SecondLoop includes a dedicated Migration archive flow for moving your data between devices.

What gets exported​

The exported archive is a portable zip file with this structure:

  • Markdown files for readable item content
  • attachments/ for exported files
  • export-manifest.json for lossless restore metadata

This format keeps the archive human-readable while still preserving stable IDs, timestamps, attachments, and internal references.

Where to find it​

Open Settings → Migration archive in the app.

From there you can:

  • export the current vault as a migration archive
  • inspect an archive before import
  • import an archive onto another device

How import works​

Import is intentionally destructive and is designed for migration, not merge.

The app will:

  1. create a local rollback snapshot
  2. clear the current vault
  3. restore items, attachments, and relations from the archive
  4. rebuild derived indexes

If restore fails after clearing, SecondLoop automatically rolls back to the local snapshot instead of leaving a partially migrated vault.

Safety notes​

  • Import is overwrite-only in the current version.
  • The UI shows an archive summary before import starts.
  • The UI requires explicit confirmation before clearing existing data.
  • Import progress is shown step by step during the migration.