Data migration between two Azure Database for PostgreSQL Flexible Servers

Sunayana Rambhatla 0 Reputation points
2025-10-24T05:05:10.11+00:00

I have two databases, one in each resource group. Both are of type Azure Database for PostgreSQL Flexible Server.

For example let's say RG1, RG2 are the two resource groups.
In RG1 I have Azure Database for PostgreSQL Flexible Server., let's say PSQLServer1

In RG2 I have Azure Database for PostgreSQL Flexible Server., let's say PSQLServer2

I want to migrate data between the two databases. But when I start a migrations service, I do not see the option to select the source server (PSQLServer1) from RG1. Please see the screenshot attached.

Are there any steps that I'm missing? How can I achieve it?

Azure Database for PostgreSQL
{count} votes

1 answer

Sort by: Most helpful
  1. Manoj Kumar Boyini 405 Reputation points Microsoft External Staff Moderator
    2025-10-24T12:17:21.1+00:00

    Hi Sunayana Rambhatla,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    Thanks for sharing the details I see you are trying to move data between two Azure Database for PostgreSQL Flexible Servers in different resource groups (RG1 and RG2). Let’s go through a few things that could be causing the issue with selecting your source server for migration:

    1.Same Region Check: Azure DMS doesn’t support cross-region migration for PostgreSQL Flexible Servers. So, it’s important to double-check that both PSQLServer1 (the source) and PSQLServer2 (the target) are in the same Azure region. If they ae not, you might need to create a new server in the same region as the destination server and migrate it that way.

    2.Permissions: Make sure the account you are using for DMS has the right permissions (at least Contributor or Owner) for both resource groups (RG1 and RG2). Without the correct access, the migration service won’t be able to detect the source server.

    3.Network Setup: Look over the firewall settings for both PostgreSQL servers and ensure the migration services IP ranges are allowed. If the servers are in different VNets, make sure they are properly VNet peered.

    4.Check DMS Setup: Make sure your Azure Database Migration Service is configured properly and is located in the same region as the source and destination servers. If the source server still isn’t appearing, try using Azure CLI to see if you can select it that way, or take a look at the Activity Log for any clues.

    5.Manual Migration Option: If DMS keeps giving you trouble, you can always try doing a manual migration using pg_dump to back up the data and pg_restore to load it into the new server.

    Do let us know if you have any questions and queries.

    Thanks,
    Manoj

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.