You can use one or more command arguments to set the execution parameters of the migrate command.

You can add a space-separated list of arguments to the CLI upgrade command.
vcsa-deploy migrate list_of_arguments path_to_the_json_file

The required template argument provides the path of a JSON file that describes the vCenter Server appliance deployment procedure. You can place multiple JASON files in a directory, and the CLI will migrate all of the deployments in batch mode. For more information on performing concurrent migrations, see Prepare JSON Configuration Files for CLI Migration.

Important: The string values, including the passwords, must contain only ASCII characters. Extended ASCII and non-ASCII characters are unsupported.

To set a value that contains the backslash (\) or quotation mark (") character, you must precede the character with the backslash (\) character. For example, "password":"my\"password" sets the password my"password, "image":"C:\\vmware\\vcsa" sets the path C:\vmware\vcsa.

The boolean values must contain only lowercase characters. Can be either true or false. For example, "ssh.enable":false.

Optional Argument Description
--accept-eula Accepts the end-user license agreement.

Required for executing the deployment command.

-h, --help Displays the help message for the command.
--template-help Displays the help message for the configuration parameters in the JSON deployment file. You can use vcsa-deploy [subcommand] --help for a list of subcommand-specific arguments.
-v, --verbose Adds debug information to the console output.
-t, --terse Hides the console output. Displays only warning and error messages.
--log-dir, LOG_DIR Specifies the location of the log and other output files that the installer generates.

Performs basic verification of the configuration parameters and deploys the vCenter Server appliance, but does not validate the OVF Tool parameters in the ovftool_arguments subsection of the JSON template. If you set arguments that the OVF Tool does not recognize, the deployment might fail.


Prohibits SSL verification of ESXi connections.

The CLI verifies that a server's security certificate is signed by a Certificate Authority (CA), and establishes a secure connection. If the certificate is self-signed, the CLI will stop the upgrade unless you specify that the CLI ignore the self-signed certificate using the --no-ssl-certificate-validation command parameter.

If you are connecting to a server with a self-signed certificate, and fail to specify that the CLI accept it, the CLI displays the server's self-signed certificate thumbprint, and prompts you to accept or reject the it.

You can also specify that the CLI ignore self-signed certificates using the ssl_certificate_verification configuration parameter in the JSON template. See Upgrade Configuration Parameters for CLI Upgrade of vCenter Server Appliance.

Important: Avoid using this option as it may cause problems during or after upgrade due to an un-validated identity of the target host.
--operation-id Lets you provide an identifier to track the concurrent installation, migration, or upgrade of multiple vCenter Server instances. If do not provide an operation ID, the CLI generates a universally unique identifier (UUID) which you can use to identify the different instances of vCenter Server and their installation or upgrade status.
--verify-template-only Performs basic template verification without installing Upgrade Runner, running prechecks, and upgrading or migrating the vCenter Server appliance.
--precheck-only Installs Migration Assistant on the source vCenter Server virtual machine, and runs a complete set of prechecks without performing the migration.
--acknowledge-ceip Confirms acknowledgement of your VMware Customer Experience Improvement Program (CEIP) participation. This argument is required if ceip.enabled is set to true in the upgrade template.
Exit Code Description
0 Command ran successfully
1 Runtime error
2 Validation error
3 Template error