Koha implementation cost: what libraries really pay, component by component

What is free and what you pay for

The most common confusion is thinking that "free software" means "free project". It does not, and it is worth saying plainly.

• Free: the software, the updates published by the community, the official documentation, the number of users, the number of catalog records and the number of branches. Koha does not charge per module or per item.
• Paid: human work and infrastructure. Installing, configuring, migrating data, training, hosting, backing up, upgrading and responding when something fails.

The underlying difference from a proprietary system is not that one costs money and the other does not, but what the money turns into. With a licensed ILS, part of the annual budget pays for the right to keep using the software. With Koha, that same money pays for services the institution can contract, move to another provider or bring in-house. The broader comparison of both models is in our guide to the integrated library system.

Koha implementation cost by component

The ranges below are orders of magnitude from BiblioLabTech's university projects, not a price list. Use them to build a preliminary budget and to spot a quote that is out of line; the real figure depends on the variables in the last column. All amounts are in US dollars.

The components are not all added together. Most universities contract implementation, migration, training and support, and decide separately whether to take hosting. That is why almost every quote BiblioLabTech prepares comes in two versions, with and without hosting. Hosting options are compared in Koha hosting: managed cloud or your own server.

How much does Koha cost in year one and after?

The USD 3,000 to 4,000 first-year reference corresponds to a single-campus university migrating 15,000 to 25,000 records, with implementation, migration, training, support and hosting included. From the second year, the one-off lines disappear and only hosting and the support contract remain. Using the reference ranges above, those two recurring lines add up to roughly USD 900 to 3,500 a year, depending on server size and service level, or only the support line if your institution hosts Koha on its own servers.

Upgrades to new Koha versions belong in a serious support contract, so they should not appear as a surprise line every year. Ask about it explicitly before signing: some providers charge separately for each upgrade, which over time can cost more than the initial project.

Migration cost by number of records

Migration is the component with the widest price spread, because it depends not only on the number of records but on the state they arrive in. A messy collection of 9,000 records can cost more than a well-maintained one of 25,000.

The technical detail of each tier is in how to migrate to Koha.

What drives the price up

• Several branches. The strongest multiplier. Three campuses mean three sets of circulation rules, three calendars, three patron groups and three validations.
• Poor source data. Duplicates, mixed fields, legacy encoding, items without barcodes. All cleanup is manual or semi-automatic work that has to be reviewed.
• A source system without standard export. With no ISO 2709 or MARCXML output, data must be extracted from the database and the conversion built from scratch.
• Integrations with institutional systems. Authentication against the university directory, student sync from the student information system, SIP2 self-check, repository harvesting.
• A demanding service level. An SLA with response in hours and extended coverage costs more than one with response in business days.
• Deep OPAC customization. Applying the visual identity is inexpensive; redesigning the search experience is a development project.
• Physical work on the collection. Inventory, labeling and barcode application are quoted per item and are independent of the software.

What brings the price down

• Providing a clean MARC21 export from the current system.
• Having configuration decisions made: item types, patron categories and loan rules defined before the project starts.
• Assigning a responsible counterpart in the library who validates test batches without delay.
• Starting with one branch and scaling afterward, instead of migrating three campuses in the same semester.
• Accepting the standard OPAC with your visual identity, and leaving a redesign for a second phase.
• Not migrating the full circulation history if nobody will consult it.

Total cost of ownership vs a proprietary ILS

An honest comparison is made over five years, not over the first year, because that is where the curves separate. The structure looks like this:

BiblioLabTech does not claim Koha is always cheaper. A university with no technical support of its own that contracts a demanding SLA can spend on services an amount comparable to a license. The structural difference lies elsewhere: with Koha, that spending is contestable. It can be renegotiated, split between providers or brought in-house, and it does not buy the right to keep using the software; it buys work.

Costs that do not appear in the quote

Three items rarely appear in a proposal yet consume real budget. Account for them from the start so they do not surprise you halfway through the project.

• Library staff hours. Someone has to validate test batches, decide on configuration, review migrated records and attend training. In a 20,000-record project, that can mean several weeks of part-time dedication from one or two people. It is not a provider cost, but it is an institutional one.
• Physical work on the collection. If items must be labeled, barcodes printed and applied or an inventory taken, that effort is quoted per item and is independent of the software. In collections that never had barcodes, it is often the largest line in the whole project.
• Accumulated data debt. A catalog with duplicates and incomplete descriptions will still have those problems after migration. Cleaning it is a separate decision: it can be postponed, but it does not disappear by changing systems.

The upside is that these three costs are paid once and leave the collection in better shape than before. If they are going to be taken on, the migration is the cheapest moment to do it, because all the material is already being handled.

How to request comparable quotes

Quotes from different providers are often impossible to compare because each one assumes different things. To receive proposals you can put side by side, specify these eight points:

1. Number of bibliographic records, items and active patrons.
2. Source system and exact version, and whether you already have a MARC21 export.
3. Number of branches and whether each has its own circulation rules.
4. A proposal with and without hosting, as two separate lines.
5. Expected support level: hours of coverage, response time for an OPAC outage and annual bank of hours.
6. Required integrations: institutional authentication, student information system, self-check, repository.
7. Training: how many people, how many sessions, remote or on-site.
8. What is delivered at the end: manuals, a migration report with verified counts and administrator credentials.

Always ask for the proposal to separate what is paid once from what is paid every year. It is the only way to project the cost over five years and compare it with the renewal of a proprietary system. What ongoing support covers is detailed in what Koha support includes.

When you have your collection numbers, request a quote through our Koha service. BiblioLabTech works remotely with libraries in any country and includes BiblioScan AI at no extra cost in every Koha implementation. You can also send us your numbers directly.