HCP Terraform Legacy Free Plan Reaches End of Life March 31: What Teams Need to Know

HashiCorp published an end-of-life notice on January 6, 2026, announcing that the HCP Terraform legacy free plan will be discontinued on March 31, 2026. Organizations still on the legacy plan after that date will be automatically migrated to the enhanced free tier — a one-way migration that cannot be reverted.

What Changes

The legacy free plan offered unlimited users with a maximum of five active members, 500 managed resources, one concurrent run, and basic policy enforcement via Sentinel and OPA. The enhanced free tier, introduced in 2023, provides a usage-based model that covers 500 managed resources, unlimited users, one concurrent run, plus SSO, policy-as-code (Sentinel + OPA), run tasks, and HCP Terraform agents.

On paper, the enhanced tier is more capable — SSO on a free plan is genuinely unusual and valuable for small teams. However, the one-way migration and the broader trajectory of HashiCorp's pricing under IBM ownership have generated significant community discussion about whether this is the right time to switch toolchains entirely rather than migrating to a new HashiCorp plan.

The OpenTofu Migration Question

Hacker News threads and infrastructure engineering forums show active discussion about switching from HCP Terraform to OpenTofu with self-hosted state management, or to Pulumi with its recently announced Terraform state backend. For teams whose primary attachment to HCP Terraform was the convenience of managed state and the zero-cost entry point, the plan discontinuation removes one of the key reasons to stay on the HashiCorp platform.

OpenTofu, the community fork of Terraform that maintains API compatibility while operating under an open-source license, provides a direct migration path: teams can switch their execution engine from Terraform CLI to OpenTofu without rewriting their HCL code. Combined with free or self-hosted state backends like S3 + DynamoDB or PostgreSQL, OpenTofu can replace both the CLI and the state management that HCP Terraform provides — at no licensing cost.

What Affected Teams Should Do

Organizations on the legacy free plan should evaluate their options before the March 31 deadline. Three paths are available: accept the automatic migration to the enhanced free tier and continue on HCP Terraform; proactively migrate to the enhanced tier and evaluate whether the SSO and run tasks features justify remaining on the platform; or use the forced migration as a trigger to evaluate OpenTofu, Pulumi, or self-hosted Terraform as alternatives.

For teams managing fewer than 500 resources with simple workflows, the enhanced free tier may be sufficient. For teams that view the migration as a signal of continued pricing pressure under IBM ownership, the March 31 deadline provides a natural decision point to evaluate alternatives while the migration friction is already being incurred.