Google Migration Center API
Browse all Google APIs✓ Official Vendor SpecCloud InfrastructureComputeoauth234 EndpointsREST
For Agents
Discover, group, and plan workload migrations to Google Cloud: import asset inventory, manage groups and preferences, run reports, and track collector heartbeats.
Use for: Import an RVTools export of our VMware estate into Migration Center, Add a list of assets to a migration group for wave planning, Run a report estimating the Google Cloud cost of a migration group, List all assets currently in our Migration Center inventory
Not supported: Does not perform actual VM, database, or container migrations — use for asset discovery, grouping, preference sets, and migration reports only.
Migration Center is Google Cloud's unified workload-discovery and migration-planning service that catalogs on-premises and cloud assets, groups them, and produces reports for migrations to Google Cloud. The API exposes assets, groups, import jobs, preference sets, sources, and reports, plus heartbeat endpoints used by data collectors. Many state changes are long-running operations and the API is scoped to project locations.
Install Jentic One Beta
Connect the Migration Center API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Migration Center API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Migration Center API.
Import asset inventory from CSV, RVTools, or supported scanners via import jobs
Group assets by tag, attribute, or query for migration wave planning
Run reports that estimate cost, sizing, and Google Cloud target shape per group
Manage preference sets that drive sizing assumptions and target product choices
Send and inspect collector heartbeats so on-premises agents stay healthy
Validate import payloads before committing them to the asset catalog
Manage sources representing the upstream systems that feed asset data
Use Cases
Patterns agents use Migration Center API for, with concrete tasks.
★ Asset discovery and inventory
Import asset inventory from RVTools, CSV exports, or running collectors so that Migration Center has a complete view of on-premises VMs, machines, and applications. Assets are scoped to a project location and can be queried, grouped, and reported on as a single inventory across data centres.
Create an import job in projects/acme/locations/us-central1 with an RVTools payload, call validate, and run the job once validation succeeds
Migration wave planning
Group assets into migration waves based on application boundaries or business criticality so that each wave can be sized, costed, and migrated independently. The addAssets and removeAssets operations let teams iterate on group membership as discovery refines what belongs together.
Create a group named wave-1-mission-critical in projects/acme/locations/us-central1, then call addAssets with the asset names produced by an internal CMDB query
Migration cost and sizing reports
Run reports that estimate the Google Cloud target shape and monthly cost for a migration group under a chosen preference set. Reports surface compute, storage, and network estimates so finance and architecture teams can sign off on each wave before the migration executes.
Run a report on group wave-1-mission-critical with preferenceSet projects/acme/locations/us-central1/preferenceSets/balanced and store the report name once the operation completes
Agent integration via Jentic
AI agents acting as cloud migration assistants can use Migration Center through Jentic to keep inventory current, regroup assets as discovery progresses, and generate fresh cost reports without holding the underlying OAuth refresh token in their prompt.
List assets in projects/acme/locations/us-central1 missing from any migration group and create a group named unassigned-wave to hold them
Key Endpoints
34 endpoints — migration center is google cloud's unified workload-discovery and migration-planning service that catalogs on-premises and cloud assets, groups them, and produces reports for migrations to google cloud.
METHOD
PATH
DESCRIPTION
GET
/v1/{+parent}/assets
List discovered assets in a location
POST
/v1/{+group}:addAssets
Add assets to a migration group
POST
/v1/{+group}:removeAssets
Remove assets from a migration group
POST
/v1/{+name}:run
Run an import job
POST
/v1/{+name}:validate
Validate an import job before running
POST
/v1/{+name}:sendHeartbeat
Send a collector heartbeat
DELETE
/v1/{+name}
Delete a Migration Center resource
POST
/v1/{+name}:cancel
Cancel a long-running operation
GET
/v1/{+parent}/assets
List discovered assets in a location
POST
/v1/{+group}:addAssets
Add assets to a migration group
POST
/v1/{+group}:removeAssets
Remove assets from a migration group
POST
/v1/{+name}:run
Run an import job
POST
/v1/{+name}:validate
Validate an import job before running
POST
/v1/{+name}:sendHeartbeat
Send a collector heartbeat
DELETE
/v1/{+name}
Delete a Migration Center resource
POST
/v1/{+name}:cancel
Cancel a long-running operation
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google Cloud OAuth 2.0 client credentials and refresh tokens are stored encrypted in the Jentic vault. Agents receive short-lived bearer tokens scoped to cloud-platform; the refresh token and client secret never enter the agent's context.
Intent-based discovery
Agents search Jentic by intent such as import migration assets or run migration center report and Jentic returns the matching operations with input schemas, so the agent does not have to navigate Google Cloud's discovery documents.
Time to first call
Direct integration takes 1-2 days for OAuth setup, long-running operation polling, and import payload handling. Through Jentic the same workflows are under an hour: search, load schema, execute, poll the returned operation.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Migration Center API through Jentic.
What authentication does the Migration Center API use?
The API uses Google OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic, the OAuth credentials are held in the encrypted vault and the agent receives only a short-lived scoped bearer token.
Can I import an RVTools export of our VMware estate?
Yes. Create an import job, attach the RVTools payload, and call validate to surface schema issues before invoking run. The job processes assets asynchronously and reports per-asset success or rejection in the operation result.
What are the rate limits for the Migration Center API?
Per-project quotas are managed in the Google Cloud Console under the Migration Center service. Bulk import and group manipulation calls have concurrency caps in addition to per-minute request quotas, so large estate imports should batch addAssets calls and back off on 429 responses.
How do I run a migration cost report through Jentic?
Search Jentic for run migration center report, load the reports create operation, and execute with the group resource path and a preferenceSet name. Jentic returns the long-running operation; poll it until done, then read the report resource for sizing and cost output.
Is the Migration Center API free?
Migration Center is offered free for eligible workloads to encourage migration to Google Cloud. The API itself is not separately billed; consult the Migration Center pricing page for any premium discovery features.
Does this API actually move workloads to Google Cloud?
No, it covers discovery, grouping, sizing, and reporting only. The actual migration is performed by tools such as Migrate to Virtual Machines, Database Migration Service, or your own runbooks once a wave plan has been signed off.
GET STARTED