Migration preferences for PostgreSQL

This page describes the available migration preferences for PostgreSQL database deployments. As your target product, you can select AlloyDB for PostgreSQL or Cloud SQL for PostgreSQL.

Cloud SQL for PostgreSQL settings

Migration Center lets you choose Cloud SQL as the target database deployment for your database.

  • From the Cloud SQL edition list, select the edition to which you want to migrate. For more information, see Cloud SQL editions features.
  • From the Sizing method list, select the sizing strategy that you want to apply during the migration. If you select Utilization based, Migration Center uses performance metrics from your database, if available, to provide sizing recommendations.
  • From the Storage type list, select the type of storage that you want to use for your database.

Availability

Specify how to distribute your database across Google Cloud zones.

  • From the Zones list, select either Single zone or Multiple zones. Choosing multiple zones for your database provides a backup zone in case the primary zone becomes unavailable.

For more information about region-specific considerations, see Geography and regions.

Automatic backup

Specify if you want to enable automatic backups.

For more information, see About Cloud SQL backup.

Pricing track

Specify your preferred pricing track for the database that you migrate to Google Cloud.

Choose between on demand pricing, or a committed use of one or three years. Committed use discounts (CUDs) apply when you choose a committed use, and appear in your total cost of ownership (TCO) report.

For more information, see Cloud SQL pricing.

AlloyDB for PostgreSQL settings

Migration Center lets you choose AlloyDB for PostgreSQL as the target database deployment for your database. Choose the settings for your database as described in the following sections.

Sizing

Specify your preferred sizing strategy for the database that you migrate to Google Cloud.

From the Sizing method list, select one of the following sizing strategies to apply in your assessment:

  • No rightsizing: choose a shape that closely matches the shape of your source machine. Sizing doesn't take performance data into account.
  • Shape based: choose a shape that is rightsized based on AlloyDB's efficient use of resources.
  • Utilization based: choose a shape that is rightsized based on AlloyDB's efficient use of resources, and on the source performance data, when available.

Primary instance availability

Specify how to distribute your database across Google Cloud zones.

From the Zones list, select either Single zone or Multiple zones. Choosing multiple zones for your database provides a backup zone in case the primary zone becomes unavailable.

Data protection

From the Continuous data protection field, specify if you plan to use automatic backups in your database, and to include them in your cost estimation.

Pricing track

Specify your preferred pricing track for the database that you migrate to Google Cloud.

Choose between on demand pricing, or a committed use of one or three years. Committed use discounts (CUDs) apply when you choose a committed use, and appear in your TCO report.

For more information, see AlloyDB for PostgreSQL pricing.

What's next