Stay organized with collections
Save and categorize content based on your preferences.
From a networking point of view, Database Migration Service and Cloud SQL are
service producers that reside in their own dedicated networks
(known as service networks), outside the Virtual Private Cloud (VPC)
networks that you use in your Google Cloud project.
The goal of configuring network connectivity for a migration process is to
ensure that Database Migration Service can reach your source
SQL Server database and the destination Cloud SQL for PostgreSQL
instance.
Before you configure the source or destination database instances, we recommend
that you consider what networking methods you can use to establish the
necessary network connections. See the following pages:
Networking overview describes the high-level, end-to-end
migration networking landscape.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThis document outlines the process of migrating from a heterogeneous SQL Server to Cloud SQL for PostgreSQL using the Database Migration Service.\u003c/p\u003e\n"],["\u003cp\u003eDatabase Migration Service and Cloud SQL operate within dedicated service networks, separate from your project's Virtual Private Cloud (VPC) networks.\u003c/p\u003e\n"],["\u003cp\u003eEstablishing network connectivity is crucial to enable Database Migration Service to communicate with both the source SQL Server and the destination Cloud SQL for PostgreSQL instance.\u003c/p\u003e\n"],["\u003cp\u003eThe document provides links to further documentation covering a high level overview of the network, and specific details on the source and destination database connectivity.\u003c/p\u003e\n"],["\u003cp\u003eThe Database Migration service is currently in a pre-GA stage, which means that it is provided "as is", with potentially limited support.\u003c/p\u003e\n"]]],[],null,["# Plan your networking configuration\n\nFrom a networking point of view, Database Migration Service and Cloud SQL are\n*service producers* that reside in their own dedicated networks\n(known as *service networks*), outside the Virtual Private Cloud (VPC)\nnetworks that you use in your Google Cloud project.\nThe goal of configuring network connectivity for a migration process is to\nensure that Database Migration Service can reach your source\nSQL Server database and the destination Cloud SQL for PostgreSQL\ninstance.\n\nBefore you configure the source or destination database instances, we recommend\nthat you consider what networking methods you can use to establish the\nnecessary network connections. See the following pages:\n\n- [Networking overview](/database-migration/docs/sqlserver-to-csql-pgsql/networking-overview) describes the high-level, end-to-end\n migration networking landscape.\n\n- [Source networking methods](/database-migration/docs/sqlserver-to-csql-pgsql/networking-methods-source) focuses on the source database connectivity.\n\n- [Destination networking methods](/database-migration/docs/sqlserver-to-csql-pgsql/networking-methods-destination) focuses on the destination\n database connectivity.\n\nFor a complete, step-by-step migration walkthrough, see\n[SQL Server to Cloud SQL for PostgreSQL migration guide](/database-migration/docs/sqlserver-to-csql-pgsql/guide)."]]
