Google Migration Center

Google CloudOAuth 2.0Connection test available

A unified platform that helps you accelerate your end-to-end cloud journey from your current on-premises or cloud environments to Google Cloud (Google OAuth2).

OCNORA ships 10 typed Google Migration Center operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Before you connect Google Migration Center

Authentication
OAuth 2.0
Credential
{"client_id", "client_secret", "refresh_token"}
Connection test
Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with Google Migration Center

Operations, grouped by what they do to your data.

Create and send 1

Read and search 4

Update 2

Delete and cancel 2

Other operations 1

A sample Google Migration Center workflow

  1. 1
    A core trigger
    Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Migration Center trigger is needed.
  2. 2
    Get Assetmigration_center.get_asset
    Gets the details of an asset.
  3. 3
    Aggregate Valuesmigration_center.aggregate_values
    Aggregates the requested fields based on provided function.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Google Migration Center questions

How does OCNORA authenticate with Google Migration Center?
With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
What can I automate with Google Migration Center?
10 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Google Migration Center operation I need is not listed?
Where Google Migration Center has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Google Migration Center?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Google Migration Center calls controlled?
Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Google Migration Center workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.