Migrating an Old Material Library: Move Computers, Migrate the Database, and Re-check Source Paths
For new computers, new drives, or old material libraries, back up the database, migrate the database location, handle missing paths, confirm statistics, refresh source paths, and repair database.db only when damaged.

For new computers, new drives, or old material libraries, back up the database, migrate the database location, handle missing paths, confirm statistics, refresh source paths, and repair database.db only when damaged.
When changing computers or drives, distinguish between the database and the source material folders.
1. Understand Database vs Material
The database stores records, labels, notes, collections, and search data. The material folders store original source files. Both matter.
2. Back Up Before Migration
Back up the database folder and important source material before moving anything.
3. Change Location on the Same Computer
If you are moving the database on the same computer, use the database migration or path selection workflow so settings point to the new location.
4. Load an Existing Database on a New Computer
Copy the database folder to the new computer, then choose it as the database location. Make sure source material paths are also available.
5. Check Statistics
After loading, open database statistics to confirm file, image, pose, and other feature counts.
6. Verify Source Paths
If folders moved or drive letters changed, update folder paths or use folder transfer workflows.
7. Refresh After Migration
Refresh the database to re-check files and update metadata after paths are corrected.
8. Repair Only When database.db Is Damaged
Use repair when the database file is corrupt or cannot be opened, not for ordinary path migration.
Common Cases
- Old paths are missing: reconnect folders to their new locations.
- Counts exist but thumbnails fail: check source file paths and refresh.
- Database file cannot open: try the repair tool with a backup copy.