Update and migrate: DiscVault 26 migration

Goal and result

Import an existing SQLite collection into DiscVault 26 through the guarded migration assistant.

Applies to

This page is only for importing existing legacy data. In both DiscVault v26 channels, /data/discvault.db is a read-only migration source, never the current runtime database; imported records are written to PostgreSQL.

DiscVault v26 stable

DiscVault v26 stable · ghcr.io/helmerznl/discvault:latest
DiscVault 26 migration assistant
read-only existing-data source; never the current runtime database · SQLite → PostgreSQL

DiscVault v26 beta

DiscVault v26 beta · ghcr.io/helmerznl/discvault:beta
DiscVault 26 migration assistant
read-only existing-data source; never the current runtime database · SQLite → PostgreSQL

Prerequisites

read-only existing-data source; never the current runtime database · /data/discvault.db · source backup
PostgreSQL dump and filesystem archive from the same stopped-writer window
owner access

Procedure

Back up: read-only existing-data source; never the current runtime database · PostgreSQL dump and filesystem archive from the same stopped-writer window · before import
Inspect: /api/next/migration/readiness · ready_for_confirmation
Run: one migration job · POST /api/next/migration/start
Compare: readiness is confirmed, migration has zero failed records, and counts and sampled media match

Commands and settings

Both channels

curl --fail http://localhost:6080/api/next/migration/readiness
curl --fail http://localhost:6080/api/next/migration/status
curl --fail -X POST http://localhost:6080/api/next/migration/start \
  -H 'Content-Type: application/json' -d '{}'
curl --fail http://localhost:6080/api/next/migration/status

Expected result

Readiness is confirmed, migration finishes without failed records, and collection counts and sampled media match.

readiness is confirmed, migration has zero failed records, and counts and sampled media match