Koha System

How MARCReady Fits Into a Koha Migration

Learn where MARCReady fits in the Koha migration process and how it helps prepare catalogue records before import.

May 12, 2026 3 min read

MARCReady is used before importing records into Koha. It helps libraries review catalogue exports, identify common MARC problems, and prepare MARC21 or MARCXML files for Koha’s import tools.

It does not replace the full migration process. Instead, it helps with one of the most important parts of that process: preparing catalogue records so they can be reviewed, staged, and imported with fewer surprises.

Where MARCReady fits

A typical Koha migration includes several steps:

Export records from your current library system.
Review the export format and data quality.
Upload a sample to MARCReady.
Review field mappings and repair suggestions.
Export reviewed MARC21 or MARCXML records.
Stage the exported file in Koha.
Review matching rules, item handling, and staged records.
Import the records into the Koha catalogue.
Check the imported records in Koha before going live.

MARCReady fits mainly between steps 2 and 5. It helps you understand what is in your export and gives you a structured way to prepare the data before it reaches Koha.

What MARCReady helps with

MARCReady can help with:

Reviewing MARC21 and MARCXML files before import.
Mapping CSV, Excel, TSV, or JSON fields to MARC.
Identifying invalid indicators.
Reviewing ISBN formatting.
Detecting empty subfields.
Flagging duplicate or unexpected fields.
Reviewing incomplete Leader and 008 fields.
Detecting common character encoding issues.
Exporting reviewed records for Koha import.

These checks are especially useful when your records come from an older system, a spreadsheet, a vendor export, or a custom database.

What still needs librarian review

MARCReady can assist with technical preparation, but libraries still need to review decisions that depend on local practice.

Examples include:

Which subject vocabulary your library uses.
Whether local call numbers are correct.
Whether local notes should be kept, changed, or removed.
How item records should map to branches, shelving locations, and item types.
Whether duplicate records should be merged or kept separate.
Whether local 9XX fields should be preserved.
Whether authority control work is needed after import.

This is why MARCReady is designed around preview and review. It suggests changes, but the library remains in control of the final export.

When to use MARCReady

Use MARCReady:

Before a first Koha test import.
Before requesting a migration quote.
When checking whether a legacy export is usable.
When converting spreadsheet data into MARC.
When cleaning existing records before a re-import.
When comparing different export options from your current system.

Why a sample preview matters

Many migration problems become visible only after you inspect real data. A sample preview can show:

Whether your export contains useful bibliographic data.
Whether item information is present and consistent.
Whether ISBNs, authors, subjects, and publication dates are in predictable fields.
Whether character encoding problems are likely.
Whether major manual cleanup is needed before a full migration.

Starting with a sample is safer than processing a full catalogue immediately.

After MARCReady: import into Koha

After exporting from MARCReady, import should still be tested in Koha using the staged MARC import workflow. During staging, review matching rules, item handling, and any records that Koha reports as problematic.

For production migrations, do a test import first. Review the results with staff before importing the full catalogue.