How to Migrate a K-12 Library System Without Losing Data or Disrupting Service
Library Resource
What Migrating a K-12 Library System Without Losing Data or Disrupting Service Includes
A K-12 library system migration is the planned transfer of library data, workflows, user records, and configuration from one system to another. In a school district, migration may include multiple campuses, circulation histories, catalog records, item records, barcodes, patron data, holds, fines, digital resources, and reporting requirements.
Migration planning is owned jointly by the district library leader, school librarians, district technology staff, and the implementation team for the new system. The goal is not simply to move records. It is to preserve the information staff need, remove inaccurate or duplicate data, confirm that daily workflows work as expected, and give every school a clear transition plan.
At a glance
- A successful migration begins with an inventory of data, workflows, integrations, and district requirements.
- Data cleanup should occur before conversion, especially for duplicate records, inactive users, item status, and barcode assignments.
- Test migrated data with representative schools, grade levels, formats, and circulation scenarios.
- Staff training, communication, and a defined cutover plan reduce disruption when the new system goes live.
- Post-launch verification is part of migration, not an optional follow-up task.
A K-12 library system migration should follow six stages: scope the migration, audit and clean the data, map fields and workflows, test the conversion, prepare staff and schools, and verify the system after launch.
Start by documenting what the district uses today. List each school, collection type, patron group, circulation rule, barcode format, integration, report, and local process that must continue. Identify records that should not move, such as obsolete users, duplicate items, inactive holds, or outdated configuration.
Next, create a data-cleanup plan. Review catalog records, item records, patron records, loan status, fines, barcodes, and location codes. Resolve inconsistencies before extraction where possible. Keep a record of decisions so librarians can explain what changed and why.
During mapping and conversion, define how each source field will appear in the new system. Confirm how the district will handle missing values, local notes, digital resources, circulation history, and records that require manual review. Do not assume that a technically complete transfer is operationally complete.
Test with representative data from elementary, middle, and high school settings. Validate searching, check-in, check-out, holds, renewals, inventory, reports, permissions, and integrations. Then run a controlled cutover with named owners, communication dates, backup procedures, and a process for correcting issues.
After launch, compare expected and actual records, monitor circulation workflows, confirm reports, and collect questions from each school. The migration is complete when staff can perform daily work accurately and district leaders can trust the resulting data.
K-12 Use Cases
District Library Director
A district library director coordinating 18 schools needs one migration plan that accounts for different barcode practices, circulation rules, and collection locations. Each school librarian validates a sample of records before the district approves cutover.
School Librarian
An elementary school librarian is moving from a locally maintained catalog and needs to verify picture books, classroom collections, student accounts, and checkout rules before the first day of school.
District Technology Coordinator
A district technology coordinator is responsible for identity, integrations, permissions, and data transfer timing while the library director validates catalog accuracy and staff workflows. Both roles use the same issue log and acceptance checklist.
Decision Points
Common Questions
What data must move?
Separate required records from historical or optional data, then document retention decisions.
What should be cleaned before extraction?
Prioritize duplicate records, inactive patrons, inaccurate item status, inconsistent locations, and barcode conflicts.
Who accepts the migrated data?
Name district and school-level reviewers, and define what constitutes an acceptable test result.
When should cutover occur?
Choose a period that gives staff time to test and train while avoiding peak circulation, enrollment, or reporting deadlines.
Students were very excited in the elementary level to see the library being reorganized. I thought it was an insurmountable project, but Follett guided us through the process.
District Library Coordinator, Everett Public Schools
Supporting Data and Evidence
Rebuilding a Broken Library System
It was the perfect storm in Everett, Massachusetts, in the year of 2019. Just five miles from Boston, Everett Public Schools serves more than 7,200 students in 10 school buildings. Like many school districts, the school is overcrowded, and the libraries operated simultaneously as classrooms to fill the need for additional space. Follett Destiny® Library Manager was in use for the high school and five elementary schools. The district chose to self-host the product, keeping all data on their own server. Mary Puleo, District Library Coordinator, was focused mainly on the high school library collection.
Practical Guidance
Build a migration inventory.
Record schools, collections, users, integrations, reports, barcodes, workflows, and district requirements before selecting what to transfer.
Clean and document source data.
Resolve duplicates, inactive records, location inconsistencies, barcode conflicts, and unclear statuses. Keep an exception log for items requiring review.
Test representative workflows.
Use samples from different school levels and validate search, circulation, holds, renewals, inventory, reports, permissions, and integrations.
Plan cutover and verification together.
Assign owners, publish staff communications, define backup procedures, and schedule post-launch checks against agreed acceptance criteria.
Run A K–12 Library Without Spending the Day on Manual Work
For the broader operational practices that help districts reduce manual library work before, during, and after a system change, see Simplify library operations.
FAQ
-
Begin planning early enough to complete data cleanup, field mapping, testing, training, and communications before the intended cutover. The schedule should reflect the number of schools, integrations, data quality issues, and district calendar constraints.
-
Not necessarily. Districts should define which history is needed for reporting, accountability, or daily operations and which records can be archived. The decision should be documented and reviewed by library leadership and district technology staff.
-
Inventory existing barcode formats, identify duplicates or unreadable labels, and confirm how item identifiers will map to the new system. Test scanning with representative items before staff rely on the migrated records.
-
Librarians should test searching, item availability, check-in, check-out, holds, renewals, patron access, inventory functions, reports, and local workflows. Testing should include common exceptions, not only successful transactions.
-
Training should cover the workflows staff perform every day and explain what changed from the previous system. Provide a way to report issues and identify who resolves data, configuration, access, and workflow questions.
Summary
A K-12 library migration is a data and operations project, not only a technical conversion. Districts should clean the source data, test representative workflows, prepare every role, and verify results after launch.
