Leaving vRA Without the Big Rewrite

Kestra presents its Migration Assistant for VMware vRealize Automation and vRealize Orchestrator as an open-source local assessment tool intended to help organizations evaluate and plan migrations away from vRA/vRO, often prompted by licensing changes and poorly documented inherited workflows. The tool analyzes exported packages to inventory workflows, triggers, dependencies, integrations, and potential Kestra plugin support, then recommends whether each workflow should be retired, merged, wrapped, converted, or rebuilt and organizes remaining work into migration waves. The proposed approach emphasizes reducing scope by consolidating duplicates, retaining existing systems such as Ansible, Terraform, ServiceNow, and vSphere, identifying unused workflows, and replacing custom integration code where plugins provide equivalent functionality. Kestra recommends running vRA and Kestra in parallel, beginning with a proof of concept, reviewing generated flow conversions, testing in a simulated VMware environment, and cutting over workflow by workflow with rollback options. It argues that moving orchestration outside the VMware stack can improve portability, support broader integrations and AI tasks, and reduce costs, while noting that organizations should validate savings, licensing implications, and design choices around catalogs and infrastructure records for their own environments.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.