Use Gluesync Automator

Start Automator and open http://localhost:8080 in your browser;

In CoreHub URL, type the address of Core Hub, for example https://corehub.example.com. Include the port when it is not 443;

Enter Username and Password;

Under Security, leave Enable TLS selected when Core Hub answers on HTTPS. Clear it when Core Hub answers on plain HTTP. Leave Skip certificate verification selected for a self-signed certificate;

Select Sign in.

Select the Core hub tab;

Read Environment: the address, TLS, Skip verification and Chronos;

Read Totals: Pipelines, Agents, Entities, Schedules available and Running containers;

Select Refresh under Pipelines when you changed something in Core Hub.

Select the Bulk tab;

In Pipeline, select the pipeline;

Select Load source schemas. Automator asks the SOURCE agent of the pipeline for its schemas;

In Source schema, select the schema, for example shop. The system schemas of the database are in the list too;

In Target schema, type the name of the schema on the target;

Read the table list. Every table is selected, and the line above it says how many tables are available and how many are selected. Clear the tables you do not want, or select Toggle/untoggle all and tick only the ones you want;

Select Create all entities (N), where N is the number of selected tables.

Select the Import & clone tab. The first card is Create entities from YAML (single pipeline);

In Pipeline, select the pipeline;

Under YAML configuration or pipeline backup (ZIP with UDFs), choose the file;

Read the line 1 entities loaded from the export file. and the table under it. The Status column shows new table when the target table does not exist, and table exists when it does. ⚠︎ mismatch means that the existing table differs from the plan;

Change the Target schema or table of a row when you need to;

Under Customize entity creation, set If the entity is already in the pipeline when the entity may exist: keep current behaviour, skip (leave as-is), update in place or fail if it already exists. Clear Parts to apply you do not need (UDFs, Function collection, Schedules, Groups, Create missing tables);

Select Preview. It only reads from Core Hub. A table shows each entity, its target and its Action, for example create if missing or use existing (no create);

Select Start import.

Select the Backup & export tab;

Decide on Include secrets under Export options. Leave it cleared to write ******* in place of every agent password. Select it to write the real passwords into the archive;

Under Export a single pipeline, select the pipeline;

Select Export entities for one YAML file with the entities of that pipeline, or Pipeline backup for a ZIP archive with the pipeline, its agents and its UDFs;

To export every pipeline of the Core Hub, select Full backup under Export all.

On the Import & clone tab, find the card Import a full backup;

Under Backup archive (ZIP) containing pipeline(s), agents, entities, schedules and UDFs, choose the archive;

Open Advanced: Validate / Import All without Customize;

Select Validate.

In Import a full backup, choose the archive and open Advanced: Validate / Import All without Customize;

Select Import All.

Select Sign out, and sign in to the second Core Hub as in the first step;

On Import & clone, choose the archive in Import a full backup, and select Customize…;

Read the four steps of the panel: Analyze, Customize, Preview and Import;

Under Global settings, read what the archive does not hold: Notifications (SMTP), Users, OIDC and user groups and Data access policies show (not in backup);

Under Defaults for every pipeline, set If an entity already exists and Pipeline name already taken. The default for the second is to add (restored);

For each pipeline, change Pipeline name if you want. Under Agents, change the host, port, database and username of the SOURCE and TARGET agent for the new environment. In the Password fields, type the password when the label says missing (masked in the backup). Leave them empty when it says from backup; leave empty to keep;

Under Tables, change Target schema, Target table or Entity name of a row, or clear Import to leave a table out. (as in backup) means no change;

Select Preview. Read the plan. Every agent line ends with password: override when you typed a password;

Select Import selected.

Open the second Core Hub in the Control Plane;

Open each restored pipeline. Compare the SOURCE and TARGET connections, the entities and the target tables with the original;

In Automator, open the Core hub tab and select Refresh. The totals include the new pipelines.

On Import & clone, find the card Duplicate pipeline (w/ agents);

In Source pipeline, select the pipeline;

In New pipeline name, type the name of the copy;

Type Source host password and Target host password. Both are required;

Leave Clone entities, schemas, and schedules from the original pipeline selected to copy the entities. Clear it to get only the pipeline and its connections;

To point the copy elsewhere, fill Source host address, Target host address, Source host port and Target host port, or select Override source & target schemas. Empty fields reuse the values of the original;

Select Duplicate Pipeline.

Select a level in Level (All, Debug+, Info+, Warning+ or Error) to filter the lines, and use the search box to find a table or a pipeline;

Read the summary line above the lines, for example info 11 warn 0 error 0, the duration and entities ok 1 / skip 0 / fail 0;

Select History to open an earlier run;

Select Copy or Download to attach the log to a ticket, and Collapse to hide it.