Simple Migration Agent v1.4.0 (LTS)

The Simple Migration Agent is a pre-built Langflow template that automates the process of migrating a database into Hybrid Manager. It uses an LLM to orchestrate the migration steps: it creates a destination cluster in your HM project, migrates the schema, and kicks off the data migration. Once the data migration is running, the agent's job is done — you monitor progress directly in Hybrid Manager.

Prerequisites

All four prerequisites must be in place before running the agent.

1. Configure an LLM API key in Langflow. The agent requires an LLM to interpret and orchestrate migration steps. OpenAI is recommended. In Langflow, go to Profile > Settings > Model Provider and enter your OpenAI API key before creating a new project.

2. Install and register the Beacon Agent on the source database host. The Beacon Agent discovers the source database and makes it visible in the HM console as a registered resource. Confirm the source database appears under your project in the HM console before proceeding.

3. Install the DMS agent and confirm the source database appears as a migration source. The DMS (Data Migration Service) agent handles the actual data transfer. Verify the source is listed and available as a migration source in HM.

4. Verify matching resource IDs. The resource ID used for the DMS agent connection and the EDB Postgres AI Agent connection must be the same. Mismatched resource IDs will cause the agent to fail. Confirm this before running the template.

Run the Simple Migration Agent

1. Open Langflow from Launchpad in the HM console.

2. Select New Flow > All Templates.

3. Select Simple Migration Agent from the template gallery.

4. Before creating the project, confirm that the Model Provider is set to OpenAI (or your chosen provider) and that your API key is configured. The agent needs a working LLM connection to proceed.

5. Select Create to open the flow on the canvas.

6. In the Text Input component on the left side of the canvas, provide the required inputs in the following format:

   → WrapCopy

   project id: <your-project-id>
   source database resource id: <your-source-database-resource-id>

   • project id — the ID of the HM project where the destination cluster will be created.
   • source database resource id — the resource ID of the source database as registered by the Beacon Agent and DMS agent. This must match the ID used in both agent configurations (see Prerequisites).

   Optionally, add a target cluster name field to specify an existing cluster as the migration target instead of creating a new one:

   → WrapCopy

   project id: <your-project-id>
   source database resource id: <your-source-database-resource-id>
   target cluster name: <your-target-cluster-name>

7. Optionally, in the Cluster Creation Wrapper component, enter a cluster template name in the provided textbox to use as the destination cluster configuration. If left empty or if the template doesn't exist, the agent defaults to a single-node EDB PaaS Postgres 18 cluster.

8. Select Run. The agent orchestrates the following steps automatically:

   • Creates a new destination cluster in your HM project using the specified template, or a single-node EDB PaaS Postgres 18 cluster if no valid template is provided.
   • Migrates the schema from the source database to the destination cluster.
   • Kicks off the data migration.

9. Once the data migration starts, navigate to Hybrid Manager to monitor migration progress. The active migration appears in your project under the migration status view.

Limitations

Review these limitations before running the agent.

Schema compatibility is required. The agent does not validate or repair schema compatibility. If the source schema has incompatible objects (for example, unsupported data types, extensions not available in the destination, or naming conflicts), the migration will fail. Resolve all schema issues before running the agent — use Migration Portal AI or EDB Copilot to assess and fix schema compatibility first.

Creates a new destination cluster by default. The agent provisions a new single-node EDB PaaS cluster (Postgres 18) as the migration target unless a valid cluster template name is provided in the Cluster Creation Wrapper component. You can also specify an existing cluster as the target by adding a target cluster name to the Text Input component.

Destination must be within Hybrid Manager. The agent cannot migrate to external destinations outside of HM. The destination cluster must exist within your HM project.

Not for production use. The template is designed for evaluation and non-production migrations. It is best suited for straightforward Postgres-to-Postgres migrations into Hybrid Manager.