Preparation
Pre-migration checklist for moving from Mylar3 to Comicarr.
Before migrating, complete every step below. The migration reads directly from your Mylar3 database file, so it must be accessible from the Comicarr container.
Always backup first
The migration tool does not modify your Mylar3 database, but you should always keep a backup of mylar.db and config.ini before proceeding.
Backup your Mylar3 database
Copy mylar.db to a safe location. The default path is your Mylar3 config directory.
cp /path/to/mylar/config/mylar.db /path/to/mylar/config/mylar.db.bakNote your Mylar3 config.ini location
The migration also reads settings from Mylar3's config.ini. It is typically in the same directory as mylar.db. Record the full path -- you will need it in the next step.
Mount mylar.db into the Comicarr container
Add a volume mount to your docker-compose.yml that makes the Mylar3 config directory available inside the container:
volumes:
- ./config:/config
- /path/to/comics:/comics
- /path/to/mylar/config:/mylar3 # Temporary: for migrationRecreate the container to pick up the new mount:
docker compose up -dThe Mylar3 database will be accessible at /mylar3/mylar.db inside the container.
Verify Comicarr is running
Open http://localhost:8090 and confirm the Comicarr UI loads. The migration tool is accessed through the UI or via the API.
Stop active downloads
Pause or complete any active downloads in Mylar3 before migrating. In-flight downloads will not transfer cleanly because their state may change during the migration.