Running the Migration
Execute and monitor the Mylar3 to Comicarr migration.
The migration supports Preview (validate without changes) and Execute (full migration). Prefer the first-run onboarding wizard in the UI when your database is empty. The same operations are available over the REST API with a session cookie.
UI (recommended)
- Complete first-run admin setup.
- When the database is empty, open the migration/onboarding dialog.
- Point Comicarr at your Mylar3 data directory (Docker: mount at
/mylar3). - Run preview, then start, and watch progress in the wizard.
REST API
All of these require a valid comicarr_session cookie and the CSRF header on mutating methods.
# Login first
curl -c cookies.txt -X POST http://localhost:8090/api/auth/login \
-H "Content-Type: application/json" \
-H "X-Requested-With: ComicarrFrontend" \
-d '{"username": "admin", "password": "your_password"}'curl -b cookies.txt -X POST http://localhost:8090/api/system/migration/preview \
-H "Content-Type: application/json" \
-H "X-Requested-With: ComicarrFrontend" \
-d '{"path": "/mylar3"}'Preview reads the Mylar3 database and reports what will transfer without writing Comicarr data.
curl -b cookies.txt -X POST http://localhost:8090/api/system/migration/start \
-H "Content-Type: application/json" \
-H "X-Requested-With: ComicarrFrontend" \
-d '{"path": "/mylar3"}'Do not interrupt
Once started, avoid restarting the container until progress reports completion or failure.
curl -b cookies.txt http://localhost:8090/api/system/migration/progressPoll until the migration reports a terminal status.
Step-by-Step
Run a preview
Validate the Mylar3 path and review row counts / warnings before committing.
Execute the migration
If the preview is clean, start the full migration from the UI or REST endpoint.
Monitor progress
Use the wizard UI or GET /api/system/migration/progress until finished.
Verify completion
Confirm series counts, credentials, and client connectivity (see Post-Migration).
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 migration fails, Comicarr aims to leave a consistent state — still keep your own Mylar3 backup.