Connection profiles capture identifiers for your data sources and
destination databases. Each connection profile contains the
minimum required amount of information Database Migration Service needs to facilitate
data movement between the data source and destination.

> [!NOTE]
> **Note:** If you plan to prepare your conversion workspace using schema files stored in Cloud Storage, you don't need to create a source connection profile for the schema conversion phase. A source connection profile is only required when connecting directly to your source database over a network connection or when starting continuous data migration. For more information, see [Conversion workspaces overview](https://docs.cloud.google.com/database-migration/docs/oracle-to-postgresql/about-conversion-workspaces.md.txt).

That information includes:

- **Connection profile name**: A human-readable name for your
  connection profile. This value is displayed in Database Migration Service in
  the Google Cloud console.

- **Connection profile ID**: A machine-readable identifier for your connection
  profile. This value is used when you work with connection profiles by using
  Database Migration Service Google Cloud CLI commands or API.

- **Region** : The region where your connection profile is saved.
  Database Migration Service is a fully-regional product, meaning all entities
  related to your migration (source and destination connection profiles,
  migration jobs, destination databases, conversion workspaces) must be saved in a single region.
  For more information on region requirements in Database Migration Service,
  see
  [Product overview](https://docs.cloud.google.com/database-migration/docs/overview.md.txt) in the main
  Database Migration Service documentation set.

- **Username** and **password** for the dedicated migration user in the source
  or destination database.

- **Connectivity information**: IP or hostname, port, migration
  user account name and password.

  Connection details differ depending on what connectivity method you use.
  Source and destination connection profiles can use different connectivity
  methods. See
  [Networking overview](https://docs.cloud.google.com/database-migration/docs/oracle-to-postgresql/networking-overview.md.txt).

## What's next

Learn more about how to:

- [Create a source connection profile](https://docs.cloud.google.com/database-migration/docs/oracle-to-postgresql/create-source-connection-profile.md.txt)
- [Create a destination connection profile](https://docs.cloud.google.com/database-migration/docs/oracle-to-postgresql/create-destination-connection-profile.md.txt)
- [Manage connection profiles](https://docs.cloud.google.com/database-migration/docs/oracle-to-postgresql/manage_connection-profiles)