Migrate from Zeabur

Zenavo reads Zeabur's template format, so most projects move in a few steps.

1. Add your server

If your Zeabur project runs on a dedicated server, you can add the same server to Zenavo, or a new one. Zenavo installs its own K3s; remove Zeabur's agent from a server before reusing it.

2. Import the project

1. In Zeabur, export the project as a template (YAML).
2. In Zenavo, open New Project and expand Import a Zeabur template or a Zenavo export at the bottom.
3. Upload or paste the YAML, add template variables as JSON if it asks for them (for example {"PUBLIC_DOMAIN": "app.example.com"}), and click Check template.
4. Review the services and any issues listed, then import it to the selected server.

What carries over: services, images and Git sources, environment variables, ports, volumes, configuration files, health checks, initialization commands and dependencies. Zeabur's names are translated: <service>.zeabur.internal becomes <service>.zenavo.internal, and ZEABUR_* built-in variables become ZENAVO_*.

3. Move your data

Zeabur and Zenavo volumes are separate. For databases, take a dump in Zeabur and restore it in Zenavo under the service's Backup & Restore tab (.sql for PostgreSQL and MySQL). For files, restore a volume archive. See Backup & Restore.

4. Switch DNS

Bind your domains under each service's Networking tab, then point their DNS records at the new server. HTTPS is issued once the records resolve.