Pulumi's HCL and Terraform State Support Redefines IaC Migration Strategy for Enterprises

Pulumi has announced the general availability of HCL execution through the Pulumi engine and Terraform state hosted in Pulumi Cloud. This means that enterprises can now execute their existing HashiCorp Configuration Language (HCL) code directly within Pulumi without requiring a complete rewrite. Furthermore, the ability to migrate Terraform state directly to Pulumi Cloud significantly reduces the friction associated with transitioning between these two prominent IaC platforms. This release, which became generally available in August 2026, marks a pivotal moment for organizations navigating the evolving IaC ecosystem. This development is highly significant for cloud and DevOps practitioners, particularly those in large enterprises with substantial investments in Terraform. Historically, migrating from Terraform to Pulumi, while offering the allure of real programming languages (TypeScript, Python, Go, C#, Java) for infrastructure definition, often presented a daunting challenge due to the need for extensive code rewrites. Pulumi's core value proposition has always been about bringing the full power of programming languages, including native testing and IDE tooling, to infrastructure. By enabling direct HCL execution and state migration, Pulumi has effectively lowered the barrier to entry for organizations looking to leverage these benefits without a disruptive, all-at-once migration. This affects platform teams, cloud architects, and DevOps engineers who are constantly evaluating and optimizing their IaC strategies. This move by Pulumi fits into a broader trend in the IaC space where flexibility, interoperability, and reducing vendor lock-in are becoming paramount. The IaC market has seen considerable shifts, notably with HashiCorp's license change in 2023 and IBM's acquisition of HashiCorp in 2025, which led to the emergence of OpenTofu as a community-driven alternative. These events have forced enterprises to reconsider their IaC tool choices, moving beyond a single-vendor default to a more strategic, nuanced decision-making process. Pulumi's new capabilities directly address this need for strategic flexibility, allowing organizations to adopt a multi-faceted IaC approach that can incorporate different tools based on specific use cases and team skill sets. In practice, this means that practitioners can now embark on a more incremental adoption of Pulumi. Teams can continue to manage their existing HCL-based infrastructure while gradually introducing new infrastructure definitions using real programming languages within Pulumi. This hybrid approach allows for skill development and process refinement over time, mitigating the risks associated with a large-scale migration. Organizations should consider evaluating how this new capability can be integrated into their existing CI/CD pipelines and governance frameworks. It also opens up possibilities for leveraging Pulumi's advanced features, such as policy-as-code and comprehensive testing frameworks, across their entire infrastructure, regardless of whether it's defined in HCL or a general-purpose language. This strategic shift could lead to more robust, auditable, and maintainable infrastructure deployments in the long run.