Agentic Migration Enablement

Service Overview

The EDB Agentic Migration Enablement engagement activates EDB's AI-powered migration capabilities across your organization's database modernization program. Rather than EDB performing migration activities on your behalf, this engagement configures and enables the agentic tooling — EDB Postgres AI agent, DMS agent, Migration Copilot, and IDE integrations — and guides your DBA and application development teams through using them to drive database migrations from Oracle and existing Postgres environments to EDB Postgres.

EDB works with your team to assess your database portfolio using HM Bulk Assessment, generate a Migration Health Scorecard to prioritize targets, execute agentic migration workflows for databases in scope, and enable your developers to use AI-assisted schema conversion and SQL analysis directly in their IDEs. At engagement close, your team has the skills, configured tooling, and documented runbooks to continue migrating independently at scale.

This engagement assumes EDB Hybrid Manager is deployed and operational. For source database schema conversion and data migration execution, the EDB Migration Basics and EDB Data Migration packages remain available as complementary offerings.

Scope of Service

Onboard

• Kickoff to confirm database inventory, migration priorities, and team participants
• Review source database estate and confirm targets in scope 
• Create HM Machine User with Estate Ingester role for migration project operations
• Confirm Beacon Agent and DMS agent (cdcagent) network access to source databases
• Confirm migration type: Snapshot only, or Snapshot + Streaming (CDC)  
• Determines DMS agent configuration and downtime requirements
• Align on migration goals: timeline, downtime tolerance, performance parity requirements

Assessment & Portfolio Planning

• Install and configure Beacon Agent on source systems 
• Install and configure DMS agent (cdcagent) 
• Run HM Bulk Assessment to generate automated complexity and compatibility analysis for all databases in scope
• Generate Migration Health Scorecard — portfolio view of migration readiness, complexity tiers, and recommended sequencing
• Identify quick-win databases (high compatibility, low effort) for accelerated migration

Agentic Migration Configuration & Enablement

• Configure and enable Migration Copilot in Hybrid Manager
• Validate Migration API connectivity and schema assessment endpoints for databases in scope
• Configure MCP connection for IDE Integration
• Run SQL Assess on target application codebases (embedded SQL, ORM queries) and Oracle trace files to identify Oracle-specific SQL requiring rewrite
• Configure Migration Portal AI Copilot for Oracle 19c sources
• Configure Unified Schema Migration through HM (2026.4.1+) 

Guided Migration Execution

• Use Migration Copilot and Migration API to execute agentic migration workflow for each database in scope:
  • Automated schema assessment and DDL compatibility review
  • Migration Portal AI Copilot 
  • AI-assisted schema conversion with EDB consultant review and validation
  • Data migration setup and execution using DMS agent (cdcagent) 
  • Schema and data validation using EDB LiveCompare
  • SQL Assess results reviewed and remediation recommendations provided to App Dev team

Team Enablement

• Conduct working sessions with DBA team on Migration Copilot workflows and HM Migration Dashboard
• Conduct working sessions with App Dev team on IDE integration and SQL Assess tooling
• Train teams to run additional migrations independently using the configured tooling and runbooks

Closure

• Deliver Migration Runbook documenting agent configuration, workflow steps, and validation procedures
• Provide Migration Health Scorecard with recommended next migration targets
• Formal sign-off and recommended roadmap for continuing the migration program

Deliverables

• Configured Beacon Agent for source database registration and assessment, and DMS agent (cdcagent) for data migration, for all source databases in scope
• Migration Health Scorecard: portfolio complexity assessment with prioritized migration targets
• Agentic migration workflow completed for databases in scope (schema converted, data migrated, validated with LiveCompare)
• IDE integration configured (expose EDB Migration API to customer IDE of choice)
• Migration Runbook: repeatable, step-by-step playbook for ongoing migrations
• Engagement summary with recommended next migration targets and sequencing

Roles and Responsibilities

EDB Project Manager: Responsible for engagement planning, stakeholder coordination, schedule management, and closeout.

EDB Solution Architect: Leads portfolio assessment strategy, Migration Copilot and API configuration, and IDE integration design. Ensures alignment with EDB Agentic Migration platform capabilities.

EDB Senior Consultant: Technical lead for agent configuration, migration execution, SQL Assess analysis, team enablement sessions, and runbook documentation.

Customer Team: Active participants throughout. Key roles:

• DBA or Database Administrator (primary migration execution partner)
• Application Developer (for IDE integration and SQL Assess sessions, Medium+)
• Infrastructure / Platform Engineer (for agent network access)
• Project or Program Manager (for migration planning and scheduling)

Assumptions

• EDB Hybrid Manager (version 1.3 or later) is deployed and operational prior to this engagement.
• A kickoff call will confirm scope, database inventory, and schedule before work begins.
• Engagement is delivered remotely unless otherwise agreed.
• Beacon Agent and DMS agent (cdcagent) can establish network connectivity to all source databases in scope.
• Source database credentials with read access are available for assessment and schema extraction.
• For Oracle sources: archive log mode and supplemental logging (ALL COLUMNS) must be enabled before migration activities begin. Customer is responsible for enabling these prerequisites.
• Migration Portal AI Copilot is available for Oracle 12c and 19c sources only, targeting EPAS 16 or 17. Oracle 21c/23ai sources and non-Oracle sources require manual schema migration.
• For Postgres-to-Postgres migrations: DMS supports simple table structures via schema auto-creation. Complex database objects (views, functions, stored procedures, triggers, sequences) require manual migration and are not in scope unless explicitly listed.
• The following Oracle data types are not supported by DMS and will be flagged during assessment: BFILE, LONG, LONG RAW, RAW, UROWID, user-defined types, ANYDATA, XMLTYPE, and Spatial/geometry types.
• Customer is responsible for application regression testing. EDB will provide SQL Assess recommendations only.
• Data migration targets non-production environments unless otherwise agreed in writing.
• Customer will provide timely feedback on deliverables. Items without commentary within 5 business days are deemed accepted.
• Customer will not provide Personal Data as defined by applicable law.
• Schema and object counts are consistent with those assessed during the engagement; changes during migration are out of scope.

Prerequisites

• EDB Hybrid Manager (version 1.3 or later) is deployed and accessible.
• Customer will migrate from supported sources: Oracle 12c, 19c (full support including Migration Portal); Oracle 21c/23ai (DMS data migration only; manual schema migration required); self-managed PostgreSQL/EPAS 12–18; AWS RDS PostgreSQL 13–17; AWS Aurora PostgreSQL-compatible 13–17
• HM Machine User with Estate Ingester role has been created in the migration project prior to engagement start.
• Beacon Agent for source DB registration/assessment and DMS agent (cdcagent) for data migration can establish network connectivity to all source databases; credentials are available.
• Source databases targeted for migration have been inventoried (database name, size, source platform, application owner).
• For Oracle sources: TNSNAMES.ora or equivalent TNS configuration is available for bulk PDB registration; archive log mode and supplemental logging (ALL COLUMNS) are enabled on all Oracle source databases.
• Migration type has been determined: Snapshot only, or Snapshot + Streaming (CDC). CDC requires ongoing network connectivity between DMS agent and source database throughout the streaming phase.
• Customer DBA team has been identified and is available for the duration of the engagement.
• Application development team is available for IDE integration and SQL Assess enablement sessions.
• VS Code or JetBrains IDE is deployed on developer machines for EDB extension installation.

Engagement Activities