Prepare an HM-managed database cluster to serve as the destination for your migration.
If you don't have a destination database cluster on Hybrid Manager (HM) yet, create one:
In the HM console, select the project where you want to create the database cluster.
In your project, select Create New and then Database Cluster to create a database cluster.
In the Clusters page, select your cluster, and use the Quick Connect option to access your database from your terminal.
Create an empty database to use as a destination for the migration. Alternatively, you can use the default database
edb_admin.
If you already have an HM-managed database cluster, you can use it as the destination for your migration.
Before proceeding, ensure the tables you migrate and the load generated during migration don't interfere with existing workloads on the cluster.
Preparing for large object (LO) migration
If you're migrating Postgres large objects (LO_SNAPSHOT_ENABLED=true), the destination needs a role matching each role that owns a large object on the source, so the migration can preserve ownership. This applies even though HM manages the destination for you otherwise.
On the source database, find which roles own large objects:
SELECT DISTINCT lomowner::regrole FROM pg_largeobject_metadata;
Using Quick Connect to reach your destination cluster, create a role with the same name for each one returned:
CREATE ROLE <role_name>;
This role doesn't need
LOGINprivileges or any grants — it only needs to exist so the writer can assign large object ownership.