This file serves as the single source of truth for Gemini Enterprise migrations. Administrators can fully configure source-to-target resource pairings by updating the YAML metadata frontmatter above.
Administrative Setup Guide
1. Environments Configuration
Set your official canonical source and target project definitions under environments:
project_number: The numeric Google Cloud Project Number (e.g.,404109417257).engine_id: The fully qualified Discovery Engine app/engine ID.
2. DataStore Grounding Mappings (datastores_mapping)
Map underlying knowledge search collections and grounding data stores (assigned under dataStoreSpecs) using their exact resource ID suffix:
datastores_mapping:
# Source ID -> Target ID
example-mcp-source_12345_mcp_data: example-mcp-target_67890_mcp_data
example-drive-source_12345_google_drive: example-drive-target_67890_google_drive
Note: Always use the fully qualified ID suffix (e.g., _google_drive, _mcp_data) to prevent substring truncation.
3. Visual Connector & Tool Mappings (connectors_mapping)
Map display aliases and frontend extension tool chips (assigned under selectedTools) to ensure visual rendering parity in the Agent Designer UI canvas:
connectors_mapping:
# Source UI Badge -> Canonical Target UI Token
"Example Source Connector": custom_mcp
"example-drive": Drive
Operational Execution
Once configured, run live migrations or offline GCS imports directly:
# 1. Execute live cross-environment migration
uv run ./migrate.py migrate-agent "Quarterly Business Review Generator" --force
# 2. Import agent definition from GCS offline backup
uv run ./migrate.py import-agent-gcs quarterly_business_review_export.json --target-engine <TARGET_ENGINE_ID>