Migration
Migrate your existing Mylar3 library and configuration to Comicarr.
Comicarr includes a built-in migration tool that transfers your Mylar3 database and configuration into Comicarr. The process is non-destructive, and your original Mylar3 data is never modified.
What Transfers
The migration can copy up to 16 supported tables from mylar.db. It imports only tables present in both databases and only columns shared by the two schemas:
| Table | Contents |
|---|---|
comics | Monitored series and their metadata |
issues | Individual issue records |
annuals | Annual issue tracking |
snatched | Download grab history |
nzblog | NZB download log |
failed | Failed download records |
storyarcs | Story arc definitions and issue mappings |
readlist | Reading list entries |
weekly | Weekly pull list data |
rssdb | RSS feed cache |
upcoming | Upcoming issue schedule |
futureupcoming | Future release dates |
ddl_info | Direct download metadata |
ref32p | 32P tracker reference data |
oneoffhistory | One-off search history |
jobhistory | Background job execution log |
In addition to the database tables:
- config.ini settings are mapped to their Comicarr equivalents
- Encrypted credentials (passwords, API keys) are decrypted from Mylar3's format and re-encrypted with Comicarr's master key when they are supported by the current configuration schema
What Doesn't Transfer
- Custom post-processing scripts (these must be reconfigured manually)
- Manual file organization performed outside the Mylar3 database
- Any third-party plugins or extensions