Migration guides

Move to SIAX Platform

Concrete steps, realistic time estimates, and an honest list of what's actually tricky. None of these migrations is a button press — we say so upfront instead of letting you find out yourself.

From Vercel

Migrate from Vercel to SIAX

How to move a Next.js app from Vercel to SIAX: containerization, what has no 1:1 equivalent, and a cutover without downtime.

Half a day for an app that's just an app. One to two weeks if you lean on ISR, Edge Middleware, Vercel Blob or KV.

From Heroku

Migrate from Heroku to SIAX

From Heroku to SIAX: containerize the app, replace add-ons one by one, and move Postgres with minimal downtime.

One day for an app with one web process and one Postgres. One to two weeks if you have five or more add-ons, background jobs and scheduled runs.

From Microsoft Azure

Migrate from Microsoft Azure to SIAX

Move App Service, VMs and Azure Database to SIAX. What transfers directly, what stays in Azure, and what the move actually costs.

Count in workloads, not hours. A single App Service app takes a day. A typical setup with a few VMs, a database and blob storage takes three to six weeks of calendar time, mostly due to data transfer and verification.

From GitHub

Migrate from GitHub to SIAX Git and CI

A practical guide to moving repos, issues and pipelines from GitHub to SIAX Git and CI — including what actually doesn't work unchanged.

Half a day for a repo with a simple pipeline. For 20-30 repos with active workflows: expect two to three working days, most of which goes to testing workflows — not moving code.

From Google Workspace

Migrate from Google Workspace to SIAX Email

How to move email, calendar and contacts from Google Workspace to SIAX Email. Docs, Drive and Meet don't come along — plan for it.

Two to four hours of active work for around ten mailboxes, plus whatever time imapsync needs in the background — often a day or more for old archives. For 50 users and up: expect a working week of calendar time, most of it wait time, client configuration and support questions rather than technical work.

From AWS S3

Migrate from AWS S3 to SIAX Object Storage

Move objects from AWS S3 to SIAX Object Storage with rclone. Copying is simple — IAM policies and presigned-URL flows have to be rewritten.

An afternoon for a bucket of a few hundred GB with a normal object count. Copying is rarely the problem — it's the rewrite of access and presigned flows that takes time, typically one to three days of development work depending on how many places in the code talk to S3. Archived objects in Glacier add days of waiting time.