Upgrading OJS requires reviewing the installation that exists, not just choosing a target version. The journal may depend on a custom theme, plugins, transactional email, DOI deposits and editorial processes that must keep working after the change.
This guide supports the planning of an upgrade to OJS 3.5 LTS. It includes a section for OJS 2 installations, but it does not propose the same sequence for every case. The route and the maintenance window must be confirmed with the technical inventory and a test on a copy of the platform.
Which versions are supported and why it matters
PKP's table, consulted on October 18, 2026, lists OJS 3.5 as a supported LTS release, with end of life expected in the second quarter of 2029. OJS 3.3 and 3.4 also appear as supported, until the second quarter of 2027.4
It is therefore not correct to say that every 3.3 or 3.4 installation is already out of support. It is worth planning the transition and checking which maintenance release each journal has installed: belonging to a supported branch does not show that its fixes have been applied.
PKP allows direct upgrades between LTS versions, such as 3.3 and 3.5. That possibility does not remove the need to review the configuration changes, dependencies and compatibility described in the release notebooks.34
PHP 8.2 is a minimum, not a complete diagnosis
The official OJS 3.5 release notebook sets PHP 8.2.0 as the minimum version. It also states that a transition from 3.3 must take into account the changes documented for both 3.4 and 3.5.3
Meeting that minimum is not enough to approve the server. We recommend reviewing the full target version, its database and extension requirements, the web server, scheduled tasks, storage and available resources. The PHP version used on the command line must be consistent with the one chosen to run the upgrade; it should not be inferred from the web configuration.
Nor is it advisable to copy requirements from an old OJS 2 or 3.0 guide and apply them to 3.5. Each stage must run in an environment compatible with the corresponding version.
Take inventory before quoting or intervening
The initial assessment should record:
- The exact version and build of OJS, PHP and the database.
- The hosted journals and the volume of files and data.
- The active plugins, their functions and their compatibility with the target.
- The visual theme, customizations and code changes.
- The file paths, web configuration and email service.
- The DOI integrations, identifiers and other external services the journal uses.
- The available backups and the evidence that they can be restored.
Hypothetical example: if a journal depends on a plugin with no compatible version, the project must decide whether to wait, replace its function or adapt the process. Discovering this after the change in production hands a pending decision to the editorial team.
Back up the complete installation and test its recovery
PKP describes the components to consider when backing up, restoring or upgrading: software, configuration, the private files directory, public files and the database.17
We recommend taking inventory of them and obtaining a consistent copy before rehearsing the upgrade, and another before the final intervention. A database backup without the manuscripts and galleys is not a complete recovery.
The restore test should confirm that the copy opens, allows access to the files and preserves the relationships needed to work. Recording that a compressed archive exists is weaker evidence than showing its recovery in a separate environment.
Rehearse the upgrade in an isolated environment
The official guide recommends doing the upgrade first in a test environment, even when moving from one build to another.17
The rehearsal copy must protect the manuscripts and personal data it contains. We recommend restricting access, preventing indexing, and disabling real email delivery and external deposits. A rehearsal must not notify authors or register identifiers by accident.
On that copy you review the route, the errors, the dependencies and the functional tests. The times observed are useful for planning the intervention; they are not a guarantee of duration for any installation.
What to test before approving the upgrade
We recommend that IT and the journal agree on an acceptance list. As a starting point:
- Access for readers, authors, reviewers and editorial profiles.
- Submission and file retrieval through controlled tests.
- Review assignment, decisions, copyediting and production.
- Display of existing articles, issues, PDFs and HTML.
- Integrity of metadata, characters and references.
- Editorial email and scheduled tasks, with test recipients.
- DOI status and configuration, and exports, without unauthorized real deposits.
- OAI-PMH responses and the functions of the plugins actually in use.
The acceptance should identify who verifies each result. A home page that loads does not show that the editorial process is operational.
Going live and rolling back
Before intervening, define how editorial changes will be paused, who authorizes the window, which copy will be kept and what evidence requires cancelling or rolling back.
If the upgrade modifies the database, replacing only the code with the previous version is not a complete rollback. We recommend recovering a coherent set of code, configuration, files and data. If new actions took place after the platform was opened, those differences must be assessed before restoring, to avoid losing work.
After reopening, repeat the critical tests and watch for errors and communications. Document pending incidents and their owner.
If the journal still uses OJS 2
The official guide warns that direct upgrades from OJS 2 to the latest versions are no longer supported. It describes intermediate stages: first reaching 2.4.8-x where applicable, moving to 3.2.1-x and continuing to later versions along a route that must be verified for the target.17
This section preserves the historical context of the guide. It does not authorize running that sequence without reviewing the builds, data and environments of each stage. A very old installation may require additional recovery and compatibility work; the diagnosis must come before any commitment on timing and price.
Request an upgrade with a clear scope
When requesting an assessment, state the current version, the number of journals, the theme, the plugins and any known problems. The review makes it possible to separate the migration project from the technical administration that follows.
OJS ONE offers operation and upgrade of OJS platforms, with a scope that must be defined for each installation.11 Request a technical assessment before choosing the upgrade route or committing to an intervention date. If you'd rather never improvise an upgrade again, the managed OJS plans include upgrades with tested backups, and the OJS 360 Assessment can build the inventory before anyone touches the installation.
Frequently asked questions
Which OJS versions are supported according to PKP?
According to PKP's table, consulted on October 18, 2026, OJS 3.5 is an LTS release with end of life expected in the second quarter of 2029, and OJS 3.3 and 3.4 remain supported until the second quarter of 2027. Check the current table before deciding.
Which PHP version does OJS 3.5 require?
The official release notebook sets PHP 8.2.0 as the minimum. It is a minimum, not a complete diagnosis: you also need to review the database, extensions, web server, scheduled tasks and plugins.
Can you upgrade directly from OJS 2 to OJS 3.5?
No. The official guide states that direct upgrades from OJS 2 to the latest versions are no longer supported and describes intermediate stages that must be verified for each target. The diagnosis must come before any commitment on timing and price.
What should be backed up before upgrading OJS?
The software, the configuration, the private files directory, the public files and the database, and you should confirm that the copy can be restored in a separate environment.
References
OJS ONE · managed operation
Your OJS, operated end to end
Hosting, upgrades with tested backups, editorial email that arrives, monitoring and support with defined response times. Your team edits; we run the platform.
- Upgrades and migrations without improvising
- Tested backups and monitoring
- Support with defined response times
OJS ONE · managed operation
Your OJS, operated end to end
Hosting, upgrades with tested backups, editorial email that arrives, monitoring and support with defined response times. Your team edits; we run the platform.
See plans