Skip to Content

eramba, from the vendor's cloud to one of our servers in a weekend

The vendor's cloud subscription ended on a Saturday. By Monday morning, the client was already logging in to its new installation.
17 November 2026 by
eramba, from the vendor's cloud to one of our servers in a weekend
OdooBot
Sector
Food and drink
Company size
Large company
Business lines
GRC and ESG, Business solutions
Solutions
Managed cloud, GRC platforms
The challenge

A date nobody in the company had chosen

The company uses eramba for its compliance and ethics committee: controls with their comments and evidence, and email reminders to each owner with the date their item falls due.

It had decided to leave the vendor's cloud and move to a server managed by us. The subscription ended on a Saturday, and the vendor's automatic notices announced that on that day it would be cancelled and the data deleted.

  • A fixed date: the end of the subscription
  • Controls and evidence that could not be lost
  • A licence the vendor had to issue for the new installation
  • Users who had to log in at a new address on Monday
The solution

Moving the entire installation, on a fixed date

A server of its own

An eramba installation on a server we manage, dedicated to this company.

Licence arranged

The licence key for the new installation, arranged with the vendor that same week.

Its data, in the new installation

Controls, evidence, users and configuration move from the vendor's service to the new server.

Checked with the client

The client logs in with their own account at the new address and confirms to us that it works.

Then, the day-to-day

The installation moves to our service: version upgrades, backups, monitoring and support.

How we did it

Two keys that weren't ours

The migration was planned for the week before the subscription ended. Two things were missing that didn't depend on us: an access the client held, and the licence key for the new installation, which the vendor had to provide. Both were requested that week.

On the Friday, with the last cancellation notice already in the client's inbox, we committed to having them log in at the new address on Monday.

The subscription was cancelled on the Saturday. By Monday morning the new installation was up and running, and the client confirmed they could log in within minutes of receiving their access.

Since then the installation has stayed with us, and it gets its version upgrades along with all the others we host.

What we learned

The date is set by the vendor's contract, not by the project

When a cloud subscription ends, the date doesn't move. Anything that depends on third parties is requested with days to spare, starting with the vendor's licence and any key the client holds.

The vendor's automatic notices keep reaching the client even while the migration is under way, and they talk about cancellation and deletion. For the person receiving them, that's alarming. You have to tell them beforehand what they're going to receive and on which day they'll see the new address.

A move like this is also the moment to make clear who runs the platform from that day on: versions, backups, access and who to call if something isn't working.

If your eramba is in the vendor's cloud and you're thinking of moving it to a managed server, see managed cloud or the product details at eramba.

Is your eramba in the vendor's cloud?

Tell us when your subscription ends and what you use the platform for. We'll tell you how we would move it and what we need from you beforehand.