Improve Service

OJS Upgrade Services

OJS upgrade services move a journal from an older or unsupported version of Open Journal Systems to a current, supported release — starting with a compatibility audit of themes and plugins, then a staged upgrade on a test copy before anything touches the live journal, so published content and metadata stay intact.

Request a Quote Book a Consultation
OJS 3.5.0-5 LTS OJS 3.4.0-10 OJS 3.3.0-22 LTS Verified 2026-07-23

Who This Is For

  • Journals running an unsupported or end-of-life OJS version
  • Publishers who've delayed upgrading for fear of breaking a customized theme or plugin
  • Institutions standardizing multiple journals on the same current OJS branch
  • Journals wanting current-version security patches without losing existing content

Common Problems This Solves

  • Running an OJS version that no longer receives security patches
  • Uncertainty about whether a custom theme or plugin will survive an upgrade
  • Fear of data loss or broken URLs from a previous bad upgrade experience
  • No staging environment to safely test an upgrade before it touches production

What's Included

Pre-upgrade compatibility audit of installed themes and plugins
Full backup of the current installation before any upgrade action
Staged upgrade performed on a test copy first, not directly on production
Post-upgrade validation: submission flow, review workflow, DOI/Crossref, and theme rendering
A documented rollback plan in case validation fails
A summary report of what changed and what was tested

How the Process Works

Compatibility audit

We check your current themes, plugins, and OJS version against the target version's requirements.

Backup

A full backup is taken and verified before any upgrade action begins.

Staging upgrade

The upgrade is performed on a staging copy first, where issues can be found and fixed safely.

Validation

We test submission, review, publishing, and integration workflows on the staging copy.

Production upgrade

Once validated, the same upgrade steps are applied to production during a planned window.

Post-upgrade check

We re-verify the live journal and monitor for any issues in the days following.

Access & Requirements

  • Full admin and server/hosting access to the current installation
  • A staging environment (we can provision one if you don't have one)
  • A recent, verified backup — or time to take one before starting

Realistic Benefits

  • Current security patches and OJS feature improvements
  • Upgrade risk caught on a staging copy instead of discovered in production
  • A documented rollback plan instead of hoping nothing goes wrong

Limitations & Exclusions

  • Some themes or plugins may need rebuilding rather than simple carry-over if they were built against very old OJS APIs
  • Very large journals with extensive historical data may need a longer validation window
  • We can't guarantee zero visual difference after an upgrade if the current theme predates the target OJS version's theming system

Documented, Not Improvised

Every engagement follows a written scope, a staging environment before production changes, and a validation checklist before anything is marked complete. Project write-ups are published as case studies once a client approves sharing them.

View case studies

Pricing for this service

Upgrades are quoted after a compatibility audit, since cost depends heavily on how many custom themes/plugins need review — not a flat rate.

View Pricing Guidance

Frequently Asked Questions

Usually the current LTS release (OJS 3.5.0-5 LTS as of our last verification), unless a specific compatibility reason points elsewhere. See our OJS Versions page for current status across branches.

It depends on how the theme was built. A properly built child theme usually carries over with review; a theme that edited core files directly is more likely to need rework. The compatibility audit tells us which case applies before we quote.

Very old versions sometimes require an intermediate step rather than a single jump. We'll assess your starting version and recommend the safest path during the audit.

That's exactly why we upgrade on staging first and keep a documented rollback plan — production isn't touched until the staging upgrade has been validated.

It depends on the audit findings — a straightforward upgrade with few customizations can take days; one requiring theme or plugin rework takes longer. You'll get a timeline after the audit.

Yes — see our Request Upgrade Assessment page to get a compatibility read before deciding.

Related Services

Related Resources

Written by the CyberDairy OJS Engineering Team

Technically reviewed by: Senior OJS Developer

Last updated 2026-07-23

Improve Service

Ready to talk about OJS Upgrade?

Tell us about your journal and current setup — we'll respond with a scoped recommendation.

Request a Quote Book a Consultation
Contact Us Request a Quote