Velostrata requirements

This page describes the requirements for migrations with Velostrata.

Requirements for all migrations


The minimum bandwidth between your source environment and GCP nodes should be the larger of:

  • 20 Mbit/sec symmetric.
  • The total number of VMs migrated concurrently, multiplied by 0.5 Mbit/sec per VM.

For example, Velostrata 4.2 by Google recommends a minimum of 50 Mbit/sec for production use of up to 100 VMs running in the cloud.

VM operating system requirements

VMs you want to migrate need to run a Supported operating system version.

Network Connectivity

Ports and connectivity required for using Velostrata are described at Network access requirements

GCP Permissions

Velostrata components require a specific set of GCP Service Accounts and Roles.

On-premises VMware to GCP migrations

VMware Versions

Velostrata supports migrations from VMware vCenter and ESXi.

The latest Velostrata release is compatible with VMware versions:

  • vCenter: 5.5U1, 6.0U1, 6.5, 6.5U1, 6.7
  • ESXi: 5.5U1, 6.0 U1, 6.5, 6.7

VMware Permissions

A VMware administrator needs to:

  • Deploy the Velostrata On-Premises Backend virtual appliance OVA.
  • Create and assign vCenter roles for Velostrata to manage migrations.

Velostrata On-Premises Backend virtual appliance

The Velostrata Backend runs on a VM in your VWware environment. For more information, see Deploying the Velostrata Backend.

AWS to GCP migrations

AWS permissions

Configuring AWS to GCP migrations requires privileges to:

  • Set up a VPN or Interconnect between AWS and GCP.
  • Create an IAM account and assign privileges to it.
Was this page helpful? Let us know how we did:

Send feedback about...

Migrate for Compute Engine (formerly Velostrata)