Migration Guide
Migrating from Terraform Cloud to InfraDots
Terraform Cloud (now HCP Terraform) has a native path out. InfraDots imports your workspaces directly — configuration, state, non-sensitive variables, and team access — so you’re not rebuilding anything by hand.
Your Terraform code doesn’t change. It’s a per-workspace cutover you can do one at a time, with your existing Terraform Cloud setup running untouched until you switch.
What moves, and what you re-enter
Terraform / OpenTofu code
Unchanged — same repo, same modules
Terraform state
Latest state version imported automatically
Non-sensitive variables
Imported with the workspace
Team access
Mapped to InfraDots permissions
Sensitive variables / secrets
Can’t be read from TFC’s API — re-enter once
VCS connection
Reconnect the repo and branch (a few clicks)
✓ moves automatically · ↻ you re-enter or re-map once
The migration, step by step
This is the one migration that’s genuinely one-click. InfraDots has a native Import from Terraform Cloud flow — you don’t rebuild workspaces by hand.
- 1
Connect Terraform Cloud
In your InfraDots organization, choose “Import from Terraform Cloud” and enter your Terraform Cloud API token and organization name.
- 2
Select workspaces
Pick the workspaces to bring over. InfraDots imports each workspace’s configuration, its latest Terraform state version, non-sensitive variables, and team access (mapped to InfraDots permissions).
- 3
Re-enter sensitive variables
Sensitive values can’t be read from Terraform Cloud’s API, so they’re flagged as required after import. Re-enter your secrets before the first run — everything else is already in place.
- 4
Connect VCS and run a plan
Point each workspace at its repo and branch, then run a plan. Because the state came over, the plan should show no changes — confirming you’re in sync — before you apply from InfraDots.
Cut over one workspace at a time. Until you apply from InfraDots, your existing Terraform Cloud setup keeps running untouched — there’s no in-flight run to interrupt.
Ready to move off Terraform Cloud?
Start with one workspace — your code and state stay put, and you can run both in parallel until you’re sure.
Frequently asked questions
Is there an automated importer, or do I rebuild workspaces by hand?
Automated. InfraDots has a native “Import from Terraform Cloud” flow: enter your Terraform Cloud API token and organization, pick the workspaces, and it imports each one’s configuration, latest state version, non-sensitive variables, and team access.
Will my Terraform state survive the migration?
Yes. The latest state version is imported per workspace. After import, your first plan should show no changes — confirming you’re in sync — before you apply anything from InfraDots.
Do I have to change my Terraform code?
No. Your .tf files, modules, and repository stay exactly as they are. You reconnect the same VCS repo and branch to the imported workspace.
What happens to my secrets?
Sensitive variables can’t be read out of Terraform Cloud’s API, so they’re flagged as required after import. You re-enter them once before the first run; everything non-sensitive comes over automatically.
Can I migrate gradually instead of all at once?
Yes. Cut over one workspace at a time. Until you apply from InfraDots, your Terraform Cloud setup keeps running untouched — there’s no in-flight run to interrupt.
Still deciding? See the full InfraDots vs. HCP Terraform comparison →