Running the Migration
Execute and monitor the Mylar3 to Comicarr migration.
The migration supports two modes: Preview (validate without changes) and Execute (full migration). Always run a preview first.
Migration Modes
Preview mode reads your Mylar3 database and reports what will be migrated without writing anything to Comicarr's database. Use this to verify the migration will work before committing.
curl -X POST "http://localhost:8090/api?cmd=previewMigration&apikey=YOUR_KEY"The response includes row counts per table, config settings that will transfer, and any warnings about incompatible data.
Execute mode performs the full migration. Comicarr automatically creates a backup of its own database before starting.
curl -X POST "http://localhost:8090/api?cmd=startMigration&apikey=YOUR_KEY"Non-interruptible
Once started, the migration runs to completion or rolls back entirely. Do not restart the container during migration.
Step-by-Step
Run a preview
Start with preview mode to validate your Mylar3 database. Check the output for errors or warnings before proceeding.
Execute the migration
If the preview is clean, run the full migration. Comicarr creates an automatic backup before writing any data.
Monitor progress
Track progress via the API:
curl "http://localhost:8090/api?cmd=getMigrationProgress&apikey=YOUR_KEY"The response includes:
| Field | Description |
|---|---|
MIGRATION_IN_PROGRESS | true while the migration is running |
MIGRATION_STATUS | Current status message |
MIGRATION_CURRENT_TABLE | Table being migrated right now |
MIGRATION_TABLES_COMPLETE | Number of tables completed so far |
Verify completion
When MIGRATION_IN_PROGRESS returns false, the migration is complete. Check MIGRATION_STATUS for the final result.
Migration Order
Tables are migrated in dependency order to maintain referential integrity:
comics(series must exist before issues)issuesannualssnatched,nzblog,failedstoryarcs,readlistweekly,rssdbupcoming,futureupcomingddl_info,ref32poneoffhistory,jobhistory
Atomic Transactions
Each table migration runs inside a database transaction. If any table fails, the entire migration rolls back to the pre-migration state -- including the automatic backup restore. No partial data is left behind.