Skip to Content

Four eramba versions behind, brought up to date in one afternoon

A publicly owned company's installation had fallen behind. We went through every intermediate version, with the backup to roll back ready before we started.
17 November 2026 by
Four eramba versions behind, brought up to date in one afternoon
OdooBot
Sector
Public sector
Company size
Publicly owned company
Business lines
GRC and ESG
Solutions
GRC platforms, Managed cloud
The challenge

The longer you wait, the bigger the jump

A risk and compliance platform gets new versions from the vendor, and some of them bring fixes that are best not left for another day.

This publicly owned company runs its eramba on a server we manage. It holds its anti-fraud plan there, with its risks and controls. On the day the vendor released a patch version, the other installations we look after were one step away. This one was four.

  • Four intermediate versions to go through
  • Database changes piled up in each one
  • Risk and compliance data that could not be lost
  • A vendor fix that had to be applied straight away
The solution

Version by version, with the rollback ready

Backup before starting

A full database dump and a separate one of eramba alone, which can be restored on its own. A copy of the attachments and of the previous configuration.

Tested rollback

A procedure to undo the upgrade, tested and with written instructions.

One jump at a time

Four upgrades in a row, each with its own version's database changes. The web application was off during the intermediate steps: nobody worked on a half-finished version.

Checked from outside

Once finished, we logged in to the application from outside, the way a user does.

The rest, the same day

That same afternoon we brought the other installations we host, which were one step behind, to the same version.

How we did it

One afternoon and four upgrades in a row

The vendor released a patch version and we decided to apply it that same day to every eramba installation we host. For the others it was one step. For this one, four.

The alternative was to jump straight to the latest version. We chose to go through the intermediate ones one by one: each version brings its own database changes, and that way, if something failed, we knew which step it had failed at.

Before the first jump, the server had its full backup and the procedure to roll back. Then came the four upgrades, with the web application off between each one. Together they applied more than 150 changes to the database structure, and none of them gave an error. At the end, the application was back online and could be reached from outside as normal.

The previous versions were kept until the new one had been running for a few days. For the people who use the platform, the change is barely visible: they log in at the same address as always. The work is in what you don't see, and in having it ready before you start.

An installation one step behind is upgraded in a short while. One four steps behind needs an afternoon and the backup prepared in advance. That is why version upgrades are part of what we do with eramba, each with its date and its backup. How we choose a platform with each client, in GRC platforms; hosting, in managed cloud.

The result

Up to date, without a single database error

4 versions gone through one after another, in one afternoon
150+ database changes applied without a single error

Has your eramba gone a while without an upgrade?

Tell us which version you're on and where it's hosted. We'll tell you how many steps there are to the latest one and how we would take them.