PostgreSQL single server migration to PostgreSQL flexible server fails due to error

Question

On 02.05.2025 our PostgreSQL single server instance stopped working (our assumption it was disabled due to scheduled retirement of PostgreSQL single server service).
It is no longer possible to connect to DB using PostgreSQL clients.
We created PostgreSQL flexible server to perform migration, but migration to PostgreSQL flexible server fails when testing connection to source database (Step 3 of migration) with error:

S0004: Failed to fetch source server details. Please make sure source server is in available state and is accepting connections, before retrying the migration

We want to migrate to PostgreSQL flexible server.
What options are available to perform the migration? Are there any means available of temporary enabling PostgreSQL single server instance to perform migration.

Answer 1

Hi @ Apply IT

Azure Database for PostgreSQL - Single Server was officially retired on March 28, 2025 instances that missed migration deadlines have been disabled. Periodic notifications were sent since the announcement on March 28, 2023, at intervals of 2 years, 18 months, 15 months, 1 year, 6 months, 3 months, 1 month, and 1 week.

Notifications were sent via email to the subscription owner as well as with service health alert in the portal. Also there was a notification on the portal page of Single Server as a popup acknowledgement for migration enablement.

I would like to inform you that, we have enabled the PostgreSQL single server for the next 30 days to migrate it to the Flexible Server, this is not extendable.

Use our migration service in Azure Database for PostgreSQL to simplify the migration experience. It provides both offline and online migration options.  https://learn.microsoft.com/en-us/azure/postgresql/migrate/migration-service/tutorial-migration-service-single-to-flexible

Auto-migration option (offline mode only) can keep server name and DNS the same, so the application won’t need any connection string changes.

Note: Public Access needs to be enabled for the Single Server, and CMK server can’t be created using auto-migration.

I hope this information helps. Please do let us know if you have any further queries.