Migration guides

Step by step, off the SaaS you are leaving and onto an open-source or source-available app you run. Follow them yourself, or let us run the move.

Talk to our team

Before you start a migration

Each guide covers one move: from a SaaS your organisation pays for to an open-source or source-available app it runs itself. They are written for the engineer who will do the work, in the order the work happens: what the service lets you export, what does not survive the export, how to rebuild it on the other side, and how to cut over without losing the people who use it.

Read the whole guide before the first export. The steps that decide whether a migration succeeds are rarely the technical ones. They are finding which automations still run, deciding who owns each shared folder, and agreeing a parallel run long enough to catch what the export missed. Every guide says what to plan for, not only what to click.

You can follow any of them yourself. If you would rather not, our migration service runs the same steps at a fixed scope and hands over a running app that we then operate for you. To see what replaces a subscription before you plan the move, start from the SaaS you are leaving.

Tell us what you need to run.

Thirty minutes with an engineer, a written plan and a fixed price for the first workload.