Terraform Enterprise on Replicated End of Support by April 1, — when and how should I migrate?

Self-managed Terraform Enterprise operators need a migration decision card on leaving Replicated Native Scheduler before support ends on April 1, 2026 and before installations become nonfunctional on December 31, 2027.

Migrate to Docker Engine unless you already run Kubernetes or Nomad well. It's the default exit from Replicated; choose orchestration only when that expertise already exists.

Blockers

Who this is for

Candidates

Migrate to Docker Engine

Docker is a supported Flexible Deployment Options runtime for self-managed Terraform Enterprise. As of 2026-03-19, HashiCorp states the final Replicated release was in March 2025 and support for that final release ends on April 1, 2026; migration requires moving to a supported runtime on the same Terraform Enterprise version. The migration guide says you must first upgrade the Replicated installation to "v202309-1" or later, and you cannot combine an application upgrade with the migration itself. Pricing for Flexible Deployment Options is not publicly listed in the official docs as of 2026-03-19, so check official docs and your HashiCorp account team.

When to choose

Use this when you want the lowest-ceremony exit from Replicated and prefer to stay close to the existing single-host operational model. It is the fastest path when you want to reuse the current host, generate a compose file from the existing installation, and avoid taking on Kubernetes or Nomad operations.

Tradeoffs

Operationally simpler than Kubernetes or Nomad, but it gives you less built-in orchestration and scaling structure. It is a pragmatic migration target, not the strongest choice for multi-node platform standardization.

Cautions

You need a new Flexible Deployment Options license file, which is different from the existing Replicated ".rli" license. The migration guide says compose configurations generated on releases older than "v202410-1" can mis-format secrets containing special characters, so manual review is required. The target runtime must run the same Terraform Enterprise version as the Replicated source.

Sources

Migrate to Kubernetes

Kubernetes is a supported Flexible Deployment Options runtime and is the most standardized target if your platform already runs clusters. As of 2026-03-19, the official 2025 release table lists Kubernetes support for current Terraform Enterprise releases; for "v202507-1" it lists tested versions of EKS "1.33", AKS "1.33", GKE "1.32", and Helm chart "1.6.5". Replicated is already deprecated, its final release was in March 2025, and support ends on April 1, 2026. Pricing for Flexible Deployment Options is not publicly listed in official docs as of 2026-03-19, so check official docs and your HashiCorp account team.

When to choose

Use this when you already operate Kubernetes and want the longest-term alignment with existing cluster tooling, security controls, and scaling patterns. It is the better choice when platform teams already manage Helm-based workloads and externalized data services.

Tradeoffs

Best fit for teams with existing Kubernetes maturity, but it adds cluster complexity if Terraform Enterprise would be your only major workload there. Migration is more operationally involved than Docker.

Cautions

The migration guide says you cannot combine upgrade and migration, so source and target must be on the same Terraform Enterprise version. You still need a Flexible Deployment Options license, and you should validate your target cluster and Helm chart versions against the release table before scheduling cutover.

Sources

Migrate to Nomad

Nomad is a supported Flexible Deployment Options runtime for self-managed Terraform Enterprise and fits teams already standardized on HashiCorp infrastructure tooling. As of 2026-03-19, the official 2025 release table lists tested Nomad version "1.7" and minimum supported version "1.5" for current releases including "v202507-1". Replicated is deprecated, the final Replicated release was in March 2025, and support ends on April 1, 2026. Pricing for Flexible Deployment Options is not publicly listed in official docs as of 2026-03-19, so check official docs and your HashiCorp account team.

When to choose

Use this when your organization already runs Nomad and wants to keep Terraform Enterprise inside the same operational stack. It is the stronger fit when Nomad expertise already exists and Kubernetes would be net-new complexity.

Tradeoffs

Cleaner operational fit for Nomad shops, but a weaker choice if your broader platform and staffing are centered on Kubernetes. It also introduces migration caveats around service dependencies that some Replicated deployments did not manage explicitly.

Cautions

The migration guide says Replicated deployments in external operational mode need an external Redis server when moving to Nomad. As with other targets, the migration is version-matched and requires a Flexible Deployment Options license distinct from the Replicated license.

Sources

Facts updated: 2026-03-19
Published: 2026-04-03

Related questions

Try with your AI agent

$ npm install -g pocketlantern
$ pocketlantern init
# Restart Claude Code, Cursor, or your MCP client, then ask:
# "Terraform Enterprise on Replicated End of Support by April 1, — when and how should I migrate?"
Missing something? Request coverage