Post-Migration

Verify migrated data, test connections, and clean up after migration.

After the migration completes, verify everything transferred correctly before removing the Mylar3 volume mount.

Verify row counts

Compare the number of records in each table between Mylar3 and Comicarr. The migration preview output includes expected counts — confirm they match the final result.

Key tables to check:

TableWhat to verify
comicsAll monitored series appear in the library
issuesIssue counts match per series
storyarcsStory arcs and their issue mappings are intact
snatchedDownload history is present

Check config.ini settings

Mylar3 settings are mapped to their Comicarr equivalents in config.ini (Docker: /config/comicarr/config.ini). Verify:

  • Library paths (DESTINATION_DIR, related comic/manga dirs)
  • Download client settings (host, port, category) in config.ini
  • ComicVine API key under Settings → API & providers
  • Search provider configuration in config.ini

Verify credential re-encryption

Mylar3 encrypted credentials are decrypted during migration and re-encrypted with Comicarr's master key under .secure/. Confirm that sensitive settings work:

  • Download client connections (verify connectivity from the container)
  • Search provider API keys (run a test search)
  • Notification provider tokens (send a test notification from Settings → Notifications)

Encryption change

Mylar3 and Comicarr use different encryption keys. The migration handles re-encryption. Your credentials are never stored in plaintext on disk.

Verify library paths

Ensure comic (and manga) library paths are accessible from the Comicarr container. If Mylar3 paths differ from your volume mounts, update the path settings in config.ini (paths are shown read-only in Settings → General).

Test download client connections

Confirm each configured client is reachable. The Settings → Download clients tab shows configured client labels (read-only); edit hosts/credentials in config.ini if needed.

Clean up

Once you have verified everything works:

  1. Remove the temporary Mylar3 volume mount from docker-compose.yml:

    docker-compose.yml
    volumes:
      - ./config:/config
      - /path/to/comics:/comics
      # Remove or comment out the mylar3 mount:
      # - /path/to/mylar/config:/mylar3:ro
  2. Recreate the container:

    docker compose up -d
  3. Keep your Mylar3 backup until you are fully confident in the migration.

On this page