Quick answer
An OJS upgrade is a controlled data and software change, not simply a new-file upload. Cost and duration depend on the starting release, required upgrade path, server compatibility, database health, journal count, storage, themes, plugins, custom code, testing, and recovery planning.
Why OJS upgrade planning matters in 2026
PKP currently lists OJS 3.5 as a long-term-support release and also publishes supported 3.4 and 3.3 packages. That does not mean every older installation should jump directly to the same target in the same way. The correct path depends on the exact current version, PHP and database environment, installed extensions, plugins, themes, custom changes, and the release documentation available at the time of work.
Before requesting a price, record the full version number rather than writing only “OJS 3.” Also record the PHP version, database type and version, operating environment, number of hosted journals, storage size, and any previous failed upgrade attempts.
What affects OJS upgrade cost?
- Starting and target versions: longer or staged paths require more compatibility work and testing.
- Database condition: inconsistent records, encoding problems, failed migrations, or manual database edits can block the upgrade.
- Server compatibility: the target release may require changes to PHP, database, extensions, memory, execution limits, permissions, or web-server configuration.
- Themes and plugins: every non-core component needs a compatibility decision: update, replace, disable, repair, or rebuild.
- Custom code: core-file modifications and undocumented integrations are harder to carry forward safely.
- Scale and testing: multiple journals, large files, many roles, active submissions, multilingual content, DOI workflows, and external integrations increase validation effort.
Typical phases in an OJS upgrade timeline
| Phase | Purpose | Deliverable |
|---|---|---|
| Audit | Record versions, infrastructure, plugins, theme, customizations, data size and known faults | Readiness and risk list |
| Backup verification | Confirm database, files directory, public assets, code and configuration can be restored | Recovery set and rollback instructions |
| Staging upgrade | Run the planned upgrade away from production and capture errors | Repeatable upgrade procedure |
| Compatibility work | Correct theme, plugin, server, email, metadata and workflow problems | Acceptance-ready staging site |
| Production upgrade | Freeze changes, take fresh backups, repeat the tested process and verify | Upgraded live site |
| Monitoring | Watch logs, scheduled tasks, email, user reports and crawl behaviour | Closed issue list and handover |
What should an OJS upgrade quotation include?
The proposal should state the current and target versions, number of journals, environments, version path, backups, staging, server work, plugin and theme scope, custom-code treatment, production downtime, testing, rollback, training, and support period. It should also identify work that is priced separately, such as a new custom theme, a replacement plugin, data repair, hosting migration, or ongoing maintenance.
Ask whether the price is fixed after an audit or provisional until the staging run. A provider cannot responsibly promise that an unknown legacy database and undocumented customizations will behave like a clean standard installation.
The tests that make an OJS upgrade complete
- Open the homepage, current issue, archives, article landing pages, PDFs, supplementary files, search, registration, login, and password reset.
- Test author submission, editor assignment, reviewer invitation, review upload, decision, copyediting, production, scheduling, and publication on staging.
- Check roles, privacy, file access, CAPTCHA or spam controls, scheduled tasks, logs, backups, and restore instructions.
- Verify SMTP delivery, sender identity, reply behaviour, email templates, queues, reminders, and bounced-message monitoring.
- Review themes, language packs, plugins, DOI settings, OAI-PMH, metadata exports, ORCID, analytics, payment, authentication, and custom reports.
- Confirm canonical URLs, robots directives, sitemap behaviour, article metadata, DOI links, and redirects if any URL changed.
How much downtime should an OJS upgrade require?
Downtime depends on database size, file handling, upgrade execution, cache rebuilding, verification, and rollback requirements. Most analysis and correction should happen on staging while production remains available. The final maintenance window should cover a fresh backup, the tested upgrade procedure, essential smoke tests, and a decision point for rollback.
Do not promise zero downtime if editors can continue changing the production database while the final copy is being upgraded. A short announced freeze is safer than silently losing submissions, decisions, uploaded files, or user changes.
Why previous failed upgrades increase cost and risk
A failed attempt may leave the database partly changed while the code or version marker tells a different story. Repeatedly running upgrade commands without understanding the failure can make recovery harder. Preserve the original pre-upgrade database, files, public directory, code, and configuration before attempting repairs.
The provider should examine logs, version state, database history, plugins, encoding, permissions, and server limits before choosing whether to repair, restore, or restart from a clean backup. This diagnostic work is separate from an ordinary clean upgrade and should be visible in the quote.
How to keep an OJS upgrade within budget
Maintain an inventory of plugins and custom code, remove abandoned components before they become critical, keep reliable backups, follow supported releases, and budget for regular maintenance instead of waiting through many major changes. Use a staging environment and document every production-specific setting.
When requesting a quote, provide current access and accurate system information. The fastest way to increase cost is to discover late that the journal has several hidden installations, a very large private files directory, a modified database, or a custom theme tied to removed templates.
Frequently asked questions
How much does an OJS upgrade cost?
There is no single price. The starting version, target version, version path, database condition, server stack, journal count, plugins, theme, custom code, data volume, testing, and previous failures determine the scope.
How long does an OJS upgrade take?
The calendar timeline includes audit, backup verification, staging, corrections, acceptance testing, production work, and monitoring. A clean standard installation is different from a legacy multi-journal portal.
Can I upgrade OJS without a staging site?
It may be technically possible, but it is risky for a production journal. Staging reveals database, plugin, theme, server, and workflow problems before they affect authors, reviewers, editors, and readers.
Will my OJS theme and plugins work after an upgrade?
Compatibility must be checked for the specific target release. Some components can be updated, while others may need replacement, correction, disabling, or redevelopment.
Does upgrading OJS improve Google Scholar indexing?
Not automatically. An upgrade can change metadata, templates, URLs, access, and plugins. Search discovery depends on the post-upgrade output and independent crawler decisions, so metadata and access should be tested.
Official sources and further reading
Product versions, support timelines, technical requirements, and third-party policies can change. Verify current details with the responsible organization before making a production decision.
Need a scoped OJS quotation?
GetOJS can review your journal, explain the work and provide a written scope without promising third-party indexing or ranking outcomes.