Migrate to Plexivo

Moving to Plexivo is a few steps for each part of your stack. Start in Migrations in the sidebar and choose New migration. If you would like a hand, choose Ask for migration help on that page.

What can move, and how#

Move a PostgreSQL database#

Before you begin#

• Create an empty Plexivo Postgres database and wait until it is running. A migration never writes into a database that already has tables.
• Your source must run PostgreSQL 12 to 18 and be reachable from the internet on its port. If it accepts only listed addresses, ask support for Plexivo’s outbound address first.
• Have a connection URL for a user that can read every table, such as postgresql://user:password@host:5432/dbname?sslmode=require. Percent-encode special characters in the password.

Copy it#

1. Choose the source. In New migration, choose Plexivo Postgres and your current provider. Each provider has a Where to find it guide for its connection URL.
2. Connect. Paste the Source connection URL, choose the Plexivo Postgres database to migrate into, and choose Inventory & continue.
3. Choose when. Start as soon as possible, or set Start copying after to a quiet time within the next 30 days.
4. Follow it. The migration shows each step: the source checked, the copy taken and stored, the restore, and completion.
5. Switch over. Point your app at the new database’s connection string. Retire the source when you are satisfied.

Your source keeps running normally while it is read. The connection URL is kept in Plexivo’s secret store only until the migration ends or you cancel it, then deleted. You can cancel until copying starts. An organisation can have 5 migrations in progress at a time.

Move Kubernetes workloads#

Choose Plexivo Kubernetes in New migration and paste your manifests. Plexivo never connects to your source cluster from this form. It sorts every object into what moves as it is, such as Deployments, Services, ConfigMaps and Jobs; what needs a change, such as Ingress and storage classes; and what cannot move, such as cluster-wide roles and custom resource definitions. For each item you choose who moves it.

Then create the workloads in Plexivo Kubernetes and apply your manifests with kubectl.

Migration credits#

Moving from another provider? Plexivo can credit part of your previous provider’s bill to your wallet for your first months, never more each month than you spend on Plexivo.

1. Check the offer. In Billing → Migration credits, the console shows what your organisation can receive and until when you can apply.
2. Apply. Enter your Previous provider, your Monthly bill (US$) for the most recent full month before tax, and the Invoice number. Choose See your credit, then Apply.
3. We check it. Plexivo checks the invoice and may ask for a copy through Support. Once approved, the credit is added to your wallet for each period of 30 days, once it ends.

By default, migration credits are for paid plans from Startup up, one credit per organisation, applied for within 90 days of creating the organisation. The application needs billing access.