Repository navigation
Backups and migration
Keep an independent backup before moving an installation. A normal updater's recovery snapshot and a portable migration bundle serve different purposes.
- Create a portable Windows backup: use ALPR Migration Backup from Windows Start. Keep the entire verified output folder on a separate protected destination.
- Update an existing Windows installation: the normal UI update creates its recovery backup automatically. A manual migration export is not required for every update.
- Windows maintenance and rollback: complete real-use checks and accept the update. Rollback restores the earlier snapshot and discards newer writes.
Copy the complete verified migration folder, including image files, settings/authentication where present, and manifests. A database dump alone is not the complete Setup bundle. Do not copy PostgreSQL physical data files between operating systems. Pause source ingestion for the move and retain the source until destination checks are accepted; Setup does not switch camera traffic.
For an existing Docker installation on Windows, the native destination has its own PostgreSQL 17 database and data directory. From v0.1.54, Setup lets you choose unused application and database ports, so the original Docker application can stay on port 3000 while you verify the native application on another port such as 3001. Resume the original system only after the consistent backup is complete; changes made there afterward are not synchronized into the imported copy. Switch Blue Iris to the destination deliberately after verification. See Migration guide and Windows Setup.
Backups contain private records, images, settings and authentication information. Store them securely; do not attach them to public issues or Discussions.
Detailed guides are versioned in the Community repository. For the exact installed version, use its release tag. Public reports must exclude credentials, private plate data and imagery.