Migrate from PostgreSQL

For migration from an existing PostgreSQL instance to SPG99, it is useful to choose the scenario right away based on two criteria:

• the data size;
• the acceptable downtime window.

The main and simplest path

For most users, the most straightforward and supported scenario is:

• create the target database in SPG99;
• move the data using pg_dump / pg_restore;
• validate the result;
• switch the application to the new DSN.

This path is the easiest to control and works well for dev, stage, and many production scenarios with an acceptable cutover window.

When a more complex path is needed

If minimal downtime matters, the next step is logical replication. But this is already an advanced scenario: in the basic managed configuration, it should be confirmed and tested separately in advance.

How to choose the scenario

Small or medium database, maintenance window available

Choose pg_dump / pg_restore.

Minimal downtime required

Consider logical replication only after a separate requirement check and a test run.

What to do before starting the migration

• check extensions and special schema features;
• estimate the data volume and load time;
• prepare the target tenant and database;
• agree on the cutover and rollback path;
• test the application against the new DSN in a test environment beforehand.

For most users, this is enough: first the simple and reliable dump/restore path, and more complex zero-downtime scenarios only after separate validation.