Migrate from Zeabur to Plexivo

Zeabur stops on 31 December 2026. Move your services, variables, PostgreSQL, MySQL and Redis data and your domains to Plexivo, step by step.

Zeabur has announced that it will cease operations on 31 December 2026, and recommends finishing your migration by 30 November 2026. This guide moves the services of a Zeabur project to Plexivo App Runner, its PostgreSQL, MySQL and Redis data to Plexivo Postgres, Plexivo Database for MySQL and Plexivo Cache, and your domain to Plexivo. Your Zeabur services keep serving until you change DNS, so you can check everything on Plexivo first.

Zeabur’s dates#

From Zeabur’s own notice of 22 October 2026: from 1 December 2026, paid plans stop renewing and running services on shared clusters are suspended; on 31 December 2026 all services stop and their data is deleted. Read the notice yourself before you plan: Zeabur: migration, refunds and security claims.

Zeabur and Plexivo, side by side#

On ZeaburOn Plexivo
ProjectA project in your Plexivo organisation.
Service from a Git repository or a container imageA Plexivo App Runner app, from Git or a container image. Plexivo detects your language, or uses your Dockerfile.
Environment variablesThe app’s Environment tab, or Plexivo Secrets for values several apps share.
A PostgreSQL servicePlexivo Postgres. Plexivo copies it for you.
A MySQL servicePlexivo Database for MySQL; see Move a MySQL database.
A Redis servicePlexivo Cache, powered by Valkey. Most apps use a cache for sessions and queues and can start empty.
A volumePlexivo App Runner keeps no local files between restarts. Keep files in your database, or use a volume on Plexivo Containers for Kubernetes, from the Startup plan.
Other databasesPlexivo runs PostgreSQL, MySQL and a Valkey cache. A database of another kind has no managed home on Plexivo; tell us what you run and we will plan it with you.
Custom domainsCustom domains, with certificates Plexivo issues and renews.

Before you begin#

  • A Plexivo account.
  • Your code on GitHub, GitLab or Bitbucket, or a public container image of it.
  • Access to your domain’s DNS settings.
  • Your Zeabur services still running. After 1 December services on shared clusters are suspended, so copy your data before then.

Move your project#

  1. Take stock. List each service in the Zeabur project: its source, its start command, its variables, its volumes and its domains. Note which services are databases, their kind and their version.
  2. Create the app. In the Plexivo console, choose Create, then Plexivo App Runner, connect your Git provider, pick the repository and branch, choose a size, and deploy. See Deploy from Git. Or ask Plexivo AI with the repository link: it plans the app and its database with the monthly price, and creates nothing until you approve.
  3. Copy your variables. Add each variable on the app’s Environment tab, then apply. Leave out the variables that point at a database: connecting the database on Plexivo sets DATABASE_URL and keeps it current. See Environment and secrets.
  4. Move the database. For PostgreSQL, create an empty Plexivo Postgres database; in Migrations, choose New migration, then Other PostgreSQL, and paste the database’s public connection URL from Zeabur. For MySQL, follow Move a MySQL database. Stop writes before the copy starts, then connect the new database on the app’s Environment tab.
  5. Add your domain. On the app’s Domains tab, add your hostname and prove you own it with the TXT record Plexivo shows. Your traffic stays on Zeabur meanwhile. See Custom domains.
  6. Switch DNS. Test the app on its plexivo.app address first. Then replace the record that points at Zeabur with the routing record Plexivo shows. Plexivo issues the certificate on the first HTTPS request once the hostname routes.
  7. Check it. On the Domains tab, Routing reads Ready on Plexivo and the certificate is valid. Open your site, run your usual checks, and watch the app’s Logs and Metrics.
  8. Keep a copy. Before Zeabur deletes its data on 31 December, keep your own export of each database, as a last way back.

With a coding agent#

Using an AI editor? Connect it to Plexivo’s MCP server and give it this page and your repository: it can plan the app and its database and show you the price, and nothing is created until you approve. See Plexivo MCP server.

Database TLS#

Plexivo Postgres accepts only TLS connections, and your app receives the CA certificate as DATABASE_CA_CERT. If your code turned off certificate checks, point it at the CA certificate instead. See TLS.

Paying from IndiaYour wallet is in US dollars; pay in rupees by UPI, card or netbanking at this month’s rate, with a GST tax invoice. Your databases, stored app data and backups are stored in India. See Paying from India and Data residency.

Free migration help#

Prefer a hand? Tell us what you run, and Plexivo support plans the move with you. Ask for free migration help.

Next steps#

Zeabur is a trademark of its owner. Plexivo is not affiliated with, endorsed or sponsored by Zeabur.

Updated 14 November 2026