About the tools

About the tools#

FOLIO Migration tools enable you to migrate libraries with the most common ILS:s over to FOLIO without data losses or any major data transformation tasks. The tools transform and load the data providing you and the library with good actionable logs and data-cleaning task lists together with the migrated data.

What data does it cover?#

FOLIO Migration Tools currently covers the following data sets:

  • Catalog (Inventory and SRS in FOLIO terminology)

  • Circulation transactions (Open loans and requests)

  • Users/Patrons (In FOLIO, these share the same app/database)

  • Courses and Reserves (Course reserves)

  • Organizations (Used in ERM and Aquisitions)

Can I use the tools for ongoing imports and integrations?#

The tools are primarily maintained for performing initial data migrations. We recommend that you use native FOLIO functionality for ongoing loads where possible. In theory, these tools can be used for ongoing patron loads from systems like Banner, Workday, or PeopleSoft. But we recommend you weigh your options carefully before going down this path.

Contributing#

Want to contribute? Read the CONTRIBUTING.MD

Found an issue?#

If you have come across an issue, reach out on our #fse_folio_migration_tools on the FOLIO Slack, or create an issue in the GitHub Issue tracker

Tests#

There is a test suite for Bibs-to-Instance mapping. You need to add arguments in order to run it against a FOLIO environment. The tests are run against the latest FOLIO Bugfest environment as part of the commit process in this repo.

IMPORTANT! the tests and the tools rely on many calls to GitHub, and you need to create a GitHub personal Access token and add a .env file in the root of the folder with the following contents:
GITHUB_TOKEN=ghp_.....
Then, either restart your shell or run
source .env
from the command line

Running the tests for the Rules mapper#

Using uv#

  • Install the packages from the pyproject.toml:

uv sync --all-groups --all-extras

  • Run the tests:

uv run pytest -v --log-level=DEBUG --password PASSWORD --tenant_id TENANT_ID --okapi_url OKAPI_URL --username USERNAME

  • With coverage:

uv run pytest --cov=./ --cov-report=xml

Apr 03, 2026 | 303 words | 2 min read

Contents