VM Migration API

Name: VM Migration API API
Brand: VM Migration API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureComputeoauth234 EndpointsREST

For Agents

Drive VM migrations from VMware, AWS, or Azure into Compute Engine so an agent can script source registration, replication, clone tests, and cutover without console clicks.

Quickstart

Get started with VM Migration API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"finalize a VM migration to Compute Engine"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with VM Migration API API.

Provision and upgrade datacenter connector appliances that stream replication data

List migrating VMs in a source and filter by replication state

Trigger clone jobs to validate workload behavior in Compute Engine before cutover

GET STARTED

Start building with VM Migration API API

Explore with Jentic

View OpenAPI Document

The VM Migration API (Migrate to Virtual Machines) programmatically migrates VMware, AWS, and Azure virtual machine workloads to Google Compute Engine. It exposes sources, datacenter connectors, migrating VMs, clone and cutover jobs, replication cycles, groups, and target projects so platform teams can script migration waves, observe replication health, and finalize cutovers. It replaces a console-driven workflow with end-to-end automation suitable for large fleet migrations.

Use Cases

Patterns agents use VM Migration API API for, with concrete tasks.

★ Wave-Based VMware to Compute Engine Migration

Platform teams migrate hundreds of VMware VMs to Compute Engine in coordinated waves by registering a vCenter source, attaching VMs to migration groups, and scripting clone-test, cutover, and finalize steps per wave. The VM Migration API exposes group operations like addGroupMigration and removeGroupMigration so the wave orchestration code can be checked into version control instead of executed by hand. Replication health is queryable per cycle to spot stalls early.

Add 12 migrating VMs to a wave group and trigger finalizeMigration on each in sequence after replication completes

Cross-Cloud Lift and Shift

Engineering teams moving workloads off AWS or Azure register the public cloud as a source, let replication stream changes into Google Cloud, run clone jobs to validate, and then cut over with finalizeMigration. The API tracks each migrating VM through cycles and exposes pause and resume controls that the orchestration system uses to coordinate downtime windows. This compresses a multi-quarter datacenter exit into a sequence of automated waves.

Migration Cutover Validation

Before finalizing a production cutover, SREs run clone jobs that bring up the migrating VM in Compute Engine for smoke testing. The VM Migration API exposes clone job lifecycle endpoints so the validation pipeline can spin up the clone, run automated checks, and tear it down without affecting replication. Once the validation passes, the same API issues the finalize call.

Trigger a clone job for a database VM, run health checks against the clone, then delete the clone job

AI Agent Migration Operator

An AI agent integrated through Jentic responds to platform-team prompts like 'finalize all completed migrations for the payments group' by listing migrating VMs in a group, filtering for replication state, and chaining finalizeMigration calls. Because the API uses OAuth 2.0 with the cloud-platform scope, Jentic isolates the token in the MAXsystem vault and exposes only a scoped reference to the agent.

Search Jentic for finalize VM migration, load the schema, and call it for each ready VM in the payments group

Key Endpoints

34 endpoints — the vm migration api (migrate to virtual machines) programmatically migrates vmware, aws, and azure virtual machine workloads to google compute engine.

METHOD

PATH

DESCRIPTION

POST

/v1/{+migratingVm}:finalizeMigration

Finalize the cutover for a migrating VM

POST

/v1/{+migratingVm}:pauseMigration

Pause replication for a migrating VM

POST

/v1/{+group}:addGroupMigration

Add a migrating VM to a wave group

POST

/v1/{+group}:removeGroupMigration

Remove a migrating VM from a wave group

POST

/v1/{+datacenterConnector}:upgradeAppliance

Upgrade the datacenter connector appliance

POST

/v1/{+migratingVm}:finalizeMigration

Finalize the cutover for a migrating VM

POST

/v1/{+migratingVm}:pauseMigration

Pause replication for a migrating VM

POST

/v1/{+group}:addGroupMigration

Add a migrating VM to a wave group

POST

/v1/{+group}:removeGroupMigration

Remove a migrating VM from a wave group

POST

/v1/{+datacenterConnector}:upgradeAppliance

Upgrade the datacenter connector appliance

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

VM Migration OAuth tokens with the cloud-platform scope are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw OAuth tokens never enter the agent's context, which matters because the cloud-platform scope grants broad project-level access including the ability to start cutovers.

Intent-based discovery

Agents search Jentic with intents like 'finalize a vm migration' or 'add VM to a wave group' and Jentic returns the matching operation with its full input schema, so the agent can construct a valid request without reading Google's discovery doc.

Time to first call

Direct VM Migration integration: 5-7 days for OAuth setup, source registration, connector deployment, and orchestration code. Through Jentic: under 1 day for the API side — search, load schema, execute (datacenter connector deployment still required separately).

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Compute Engine API

Manage the target VMs that VM Migration delivers into Compute Engine

Choose Compute Engine after migration completes when an agent needs to manage the running VMs, networks, and disks that VM Migration created.

Alternative

VMware Engine API

Run native VMware in Google Cloud rather than migrating off VMware

Choose VMware Engine when the goal is to keep workloads on VMware in Google Cloud; choose VM Migration when the goal is to convert them to native Compute Engine VMs.

Complementary

Cloud IAM API

Grant the service accounts that VM Migration uses access to source and target projects

Choose IAM when an agent needs to provision the roles that the VM Migration service account requires before any migration call will succeed.

Complementary

Cloud Monitoring API

Track replication progress and alert on stalled migrations

Choose Monitoring when an agent needs to fan out alerts on migration replication health into existing dashboards.

FAQs

Specific to using VM Migration API API through Jentic.

What authentication does the VM Migration API use?

The VM Migration API uses OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic, the OAuth token is stored encrypted in the MAXsystem vault and only a scoped reference is exposed to the agent at execution time.

Can I migrate VMs from AWS and Azure with the VM Migration API, not just VMware?

Yes. The sources resource accepts AWS, Azure, and VMware source types. After registering a source you list migrating VMs and drive their lifecycle through the same set of endpoints regardless of source type, including clone, finalize, pause, and resume.

What are the rate limits for the VM Migration API?

Default project quotas allow 600 requests per minute on control-plane operations and a smaller limit on long-running migration operations like clone and finalize. Higher quotas can be requested in the Google Cloud Console for fleet-scale migrations.

How do I finalize a VM cutover through Jentic with the VM Migration API?

Install Jentic with pip install jentic, search for finalize VM migration, load the schema for POST /v1/{+migratingVm}:finalizeMigration, then call it with the migratingVm resource name. Confirm the migrating VM is in READY_TO_PROMOTE state first by reading the VM resource.

Does the VM Migration API support migration groups for coordinated cutovers?

Yes. Use POST /v1/{+group}:addGroupMigration to attach VMs to a group and POST /v1/{+group}:removeGroupMigration to detach them. Groups are useful for wave orchestration where related VMs must cut over together.

Why does my upgradeAppliance call fail on the datacenter connector?

Appliance upgrade requires the datacenter connector to be in OFFLINE or ACTIVE state with a network path to Google's update endpoints. Verify the appliance health from a Get request and confirm outbound connectivity from the on-prem environment before retrying.