The Dr. Enrique G. León López library of the Universidad Tecnológica de Puebla operated inside the SADBIBF consortium system, on Janium, thanks to an agreement with the Dirección General de Universidades Tecnológicas y Politécnicas. In early 2025 the university learned that the agreement would expire in the first four-month term of the year. Continuing the service meant subscribing to it on its own, and at a state public university that goes first through the budget and the authorization of the state government. In July 2026 the library began operating on its own instance of JaniumNet, Janium’s cloud service.
Before the migration, the paperwork
Lic. Salomón Domínguez Contreras, head of the university’s Departamento de Servicios Bibliotecarios, described how it started:
…the institutional authorities ask us to investigate and get in touch directly with Janium so that we can subscribe to the service individually as a university, in order to be able to budget this library service within the budget of the institutional Dirección de Administración y Finanzas…
The 2026 budget included the service. With the quote and the contract information in hand, one requirement specific to public spending in Puebla remained: a technology standardization letter (oficio de estandarización tecnológica), which the Secretaría de Administración y Finanzas del Gobierno del Estado requires in order to authorize the funds. Janium helped the library fill it out. After that, the university’s Departamento de Recursos Materiales handled the signing of the contract.
The technical team does not handle that path. For a university that depends on a shared service, the real timeline for leaving is set by the budget cycle and the documents that the authorization of the spending requires, and it is best to start as early as UT Puebla did.
Thirteen days, from contract to production
The contract was signed on June 26, 2026 and the system went into production on July 8. In between, the instance was activated, customized with the university’s identity, the information was migrated and the access accounts were delivered to the staff. Since the source and the destination were both Janium, the catalog did not have to change format nor did circulation have to be translated from another model: the work was to separate UT Puebla’s data from the shared database and load it into its instance.
On the support during this stage, Lic. Domínguez wrote:
…it has been a very enriching experience, since they have given us support and willingness at all times for the migration of the information, guidance, timely follow-up, the look of the platform and the necessary customization and training…
What was moved
| Component | Figure |
|---|---|
| Bibliographic records | 9,290 |
| Copies | 28,603 |
| Users | 7,213 |
| Active loans at the time of cutover | 109 |
| Returns (history) | 37,864 |
| Fines | 3,774 (3,324 paid and 450 pending) |
The 109 loans in progress remained open, and those books are returned in the new instance with no additional steps. The 450 pending fines keep their debt, and the returns history maintains the collection’s usage statistics.
What it runs now
The university subscribes to Janium as an annual service on JaniumNet: Janium hosts the system on a high-availability server, administers it and delivers the new versions released during the year. Staff work from the browser with eight concurrent licenses, on these modules:
- Cataloging, with label and barcode printing.
- Public catalog at utpuebla.janium.net/opac, with unlimited searches.
- Circulation, with user services and chat: loans, returns and fines.
- Inventory, which makes it possible to take the physical inventory without suspending lending.
- Digital objects, for images, text, audio and video, with a full-text index and a progressive zoom viewer.
The service includes security, administration and reports, remote technical support Monday through Friday during office hours and access to Janium Academy for six members of the team.
What this case shows
The UT de la Riviera Maya left the SADBIBF when the network shut down and did it in six days. UT Puebla shows the other half of that exit, the one that happens before the technical part: including the service in the budget, gathering the documentation that the authorization of the spending requires and signing the contract. With that settled, the migration from Janium to Janium fit in thirteen days. As Lic. Domínguez summed it up, the result was an
Institutionally strengthened platform with many opportunities for growth