Importing from Koha

A library moving from Koha brings its whole history across by replaying a Koha database dump (mariadb-dump koha_library) into the platform's library tables. This is run by a developer with database access, not from the dashboard.

Command	What it does
npm run library:import-koha -- --dump <file>	Dry run. Wipes and reloads the library in one transaction, verifies, rolls back, and writes a report
npm run library:import-koha -- --dump <file> --commit	The same, committed, but only if every check passes
npm run library:export	Exports every library table (CSV + JSON + manifest). Read-only

What is carried over

Bibliographic records (from MARCXML) become titles; items become copies with their barcodes and accession numbers; issues and returns become loans. Koha borrowers are matched to the platform's students and teachers. Settings, rules, languages, custom DDC classes and print configuration are marked as configuration and are never wiped.

Safety

• The import runs under REPEATABLE READ. It counts every table outside the library before and after, and scans each for rows written by its own transaction. Any difference fails the run, and nothing is committed.
• Dumps, reports and exports live under resource/, which is git-ignored, because they hold students' names and Koha password hashes.

The full developer reference is docs/library-koha-import.md in the repository.