You can programmatically export content from one vRealize Automation environment to another by using the vRealize Automation REST API or by using the vRealize CloudClient.

For example, you can create and test your blueprints in a development environment and then import them into your production environment, or you could import a property definition from a community forum. You can programmatically import and export any of the following vRealize Automation content:

  • Application blueprints and all their components

  • IaaS machine blueprints

  • Software components

  • XaaS blueprints

  • Property definitions

  • Property groups

Table 1. Choosing Your Import and Export Tool


More information

vRealize CloudClient


vRealize Automation REST API

See Programming Guide and REST API Reference in the vRealize Automation documentation at


When exporting and importing blueprints programmatically across vRealize Automation deployments, for example from a test to a production environment or from one organization to another, it is important to recognize that clone template data is included in the package. When you import the blueprint package, default settings are populated based on information in the package. For example, if you export and then import a blueprint that was created using a clone-style workflow, and the template from which that clone data was derived does not exist in an endpoint within the vRealize Automation deployment in which you import the blueprint, some blueprint settings will not be applicable for that deployment.