Migration Guides
Move to InfraDots without the drama
Your code stays plain Terraform/OpenTofu/Terragrunt and your state comes with you. Pick where you’re coming from — each guide is a per-workspace cutover you can run in parallel until you’re sure.
From Terraform Cloud
Step-by-step guide to migrating from Terraform Cloud / HCP Terraform to InfraDots. A native importer brings your state, non-sensitive variables, and team access — no code changes, one workspace at a time.
From Spacelift
How to migrate from Spacelift to InfraDots. Your code and state stay put; stacks become workspaces and contexts become variables. A per-stack cutover with no lock-in on either side.
From env0
How to migrate from env0 to InfraDots. Your code is unchanged; environments become workspaces and env0 variables move over. A per-environment cutover with no lock-in.
From Atlantis
How to migrate from Atlantis to InfraDots. Atlantis never stored your state, so this is the lowest-risk migration: connect the same repo, map atlantis.yaml to workspaces, and retire the daemon.
From a DIY pipeline
How to move Terraform off a homegrown CI pipeline (GitHub Actions, GitLab CI) to InfraDots. Your state and code stay put; pipeline stages become workspaces and the glue code goes away.