Primo Release Schedule and Rollout Policy
Release Schedule
| Release | MT Sandbox | Total Care (TC) | MT Production | Local |
|---|---|---|---|---|
| November 2025 | October 19, 2025 | October 26, 2025 | November 2, 2025 | November 16, 2025 |
| May 2026 | April 19, 2026 | April 26, 2026 | May 3, 2026 | May 17, 2026 |
Key:
-
MT - Cloud environment consisting of multiple tenants who perform their own configuration at the institution level in the Primo Back Office
-
TC - Cloud customers who have limited access to the Primo Back Office
-
Local - Customers who own and maintain their own Primo servers
Release Timeline and Rollout
Beginning in 2026, updates to Primo Back Office (BO) will be delivered once annually. These updates will focus primarily on maintaining security and overall system stability.
Ex Libris upgrades cloud environments as soon as a new release of Primo is available, following an extensive QA process. We make certain that our hosted customers are the first to benefit from the latest enhancements and bug fixes.
The rollout of a new version is gradual and begins with institutions that are using Primo in the Ex Libris cloud environment. Prior to the upgrades, a message notifying cloud customers of the date of the upgrade is sent out by the cloud team.
The upgrade process consists of two steps: first, the new release is installed on the sandbox environment where applicable. We trust that you will try out the new version at this time. Two weeks later, the new release is installed on the production environment. Consortia environments have a four- week test period.
Five days in advance, dedicated customers receive a message containing the exact install dates for both sandbox and production, which occurs within five weeks of the MT sandbox installation date.
Release Rollout Flow
