To migrate your databases to AlloyDB for PostgreSQL with minimal downtime, you can use
Database Migration Service. Database Migration Service streamlines networking, manages
the initial database snapshot and ongoing replication, and provides status
updates throughout the migration process.

Database Migration Service offers multiple migration paths to serve a wide variety of
use cases:

- [Homogeneous migrations](https://docs.cloud.google.com/database-migration/docs/homogeneous-migrations.md.txt) let you move
  data without changing your database SQL engine from self-managed
  or managed offerings (such as Cloud SQL for PostgreSQL, Amazon RDS, or
  Amazon Aurora). Database Migration Service can help you migrate from
  backup files (physical or logical), or take the snapshot for you.

- [Heterogeneous migrations](https://docs.cloud.google.com/database-migration/docs/heterogeneous-migrations.md.txt) from Oracle
  and SQL Server sources to AlloyDB for PostgreSQL let you convert your
  database objects to PostgreSQL with the assistance of
  Gemini-powered conversion features. These features help ensure
  your database objects' consistency and quality in the converted PostgreSQL
  schemas.

[![Architecture diagram showing data flow from on-premises or other clouds
to Google Cloud using Database Migration Service, highlighting key features like
homogeneous and heterogeneous migrations, minimal downtime,
and Gemini-powered conversion.](https://docs.cloud.google.com/static/database-migration/docs/images/overview_dms_data_flow.svg)](https://docs.cloud.google.com/alloydb/docs/migrate-with-dms#lightbox-trigger) **Figure 1.** Database Migration Service architecture and data flow (click to enlarge). ![](https://docs.cloud.google.com/static/database-migration/docs/images/overview_dms_data_flow.svg)

## Database Migration Service in AlloyDB for PostgreSQL

A special, lightweight migration flow called *quick-start migrations*
is integrated directly into AlloyDB for PostgreSQL to help expedite
homogeneous migrations from sources that have a private IP address in your Google Cloud
Virtual Private Cloud (such as self-managed databases on Compute Engine, or
Cloud SQL for PostgreSQL instances enabled for private networking).

In this flow, Database Migration Service can automatically manage all
the networking requirements to connect to your source database.
[![This diagram shows network connectivity facilitated by Database Migration Service
for quick-start migrations from self-hosted databases on Compute Engine.](https://docs.cloud.google.com/static/database-migration/docs/images/quick-start-migrations/gce-src-quick-start-migration-network.svg)](https://docs.cloud.google.com/alloydb/docs/migrate-with-dms#lightbox-trigger) **Figure 2.** Network connectivity facilitated by Database Migration Service for quick-start migrations from self-hosted databases on Compute Engine. (click to enlarge) ![This diagram shows network connectivity facilitated by Database Migration Service
for quick-start migrations from self-hosted databases on Compute Engine.](https://docs.cloud.google.com/static/database-migration/docs/images/quick-start-migrations/gce-src-quick-start-migration-network.svg)

For more information on quick-start migrations in AlloyDB for PostgreSQL,
see
[Quick-start migrations](https://docs.cloud.google.com/alloydb/docs/quick-start-migrations-guide.md.txt).

## What's next

- [Learn more about Database Migration Service features and available scenarios](https://docs.cloud.google.com/database-migration/docs/overview.md.txt).