PostgreSQL database migration
The migration workflow moves a managed deployment to replacement database servers. It uses member addition, replication, a controlled transition and retirement of the old members.
Prepare the change
Agree source and target servers, operating-system compatibility, capacity, routing, backups and a recovery plan with the database owner. Confirm sufficient licence capacity while old and new members coexist.
Keep the existing deployment healthy. A standalone may need plan conversion and additional members before migration.
Follow the UI workflow
- Open Lifecycle → DB Migration.
- Choose Register New DB Node and complete the PostgreSQL add-node form.
- Follow Activity and monitor synchronization. Continue only after the new standby is caught up and healthy.
- Choose Switchover to New DB Node, review Host Name in the switchover dialog and submit the approved switchover.
- Verify the new primary and application access.
- Choose Remove Old DB Node only after verifying the selected old host and all deletion prerequisites.
- Verify the remaining deployment and retain the change record.
Final checks
Confirm database connectivity, data consistency, healthy replication, intended roles and database availability. Check the current members and monitoring after cleanup.
Move one member at a time, preserve healthy primary/standby replication and keep the required Coordinator available. Verify the new primary before removing an old host; a submitted request alone does not establish the new role.
This procedure covers database-server replacement through the Broker. Arrange other migration requirements with DBaasNow before changing the deployment.