Supported migration paths, with the current boundary stated up front.
The Migration Agent does not imply support for every source and destination. Each path needs an implemented template, valid inputs, credentials, an approved plan where required, and a validation step.
Four implemented migration types.
A path not listed here requires implementation and validation before it should be sold or scheduled as supported work.
REST API to MCP server
Analyze a supported OpenAPI specification, map endpoints to tools, and generate an integration package for review and deployment.
Amazon Redshift to Google BigQuery
Plan and run the implemented warehouse migration path with source, destination, and validation context.
MySQL to Google Cloud SQL
Use the implemented relational database template to prepare, execute, and validate the supported migration work.
MongoDB to Google Firestore
Use the implemented document-database path to map, execute, and validate the supported migration work.
Approval is explicit; pause and resume are not available.
A qualifying run can stop for an authorized approval or rejection before execution. Once an active run starts, it can be observed or cancelled, but it cannot currently be paused and resumed from a checkpoint.
Describe the actual source, destination, and decision timeline.
MigrateForce will confirm whether the path is implemented before discussing scope. No generic migration page is proof of compatibility.