Terraback vs terraform import
terraform import command brings a single resource into state, but it never writes the configuration - you still author every resource block by hand and run the command once per resource. Terraback generates the HCL and the Terraform 1.5+ import blocks for your whole account in a single bulk pass.The manual workflow
With native Terraform, importing existing infrastructure is a two-part chore for every resource: first write a matching resource block, then run an import command with the right ID.
# 1. Hand-write the resource block
resource "aws_s3_bucket" "assets" {
bucket = "my-app-assets"
}
# 2. Run import, once per resource, looking up each ID
terraform import aws_s3_bucket.assets my-app-assetsRepeat that for every bucket, instance, role, and queue in the account. For hundreds of resources it becomes a long, error-prone slog, and the imports themselves are not captured in your configuration.
The Terraback workflow
Terraback scans the account, generates the resource blocks from the live attributes, and emits Terraform 1.5+ import blocks - then imports everything at once.
# 1. Scan and generate Terraform for the whole account
terraback scan all aws --region us-east-1
# 2. Bulk import using generated import blocks
terraback aws import --method bulkThe import blocks live in your configuration, so the whole operation is reviewable in a pull request and repeatable across environments.
Terraback vs terraform import comparison
| Feature | Terraback | terraform import |
|---|---|---|
| Generates HCL | Yes, writes the resource blocks for you | No, you author every block by hand |
| Import style | Bulk Terraform 1.5+ import blocks | One CLI command per resource |
| Effort for 500 resources | One scan + one import command | 500 hand-written blocks + 500 commands |
| Reviewable in a pull request | Yes, import blocks live in config | Partly - CLI imports are not in config |
| Finds the import IDs | Discovers them during the scan | You look up each ID manually |
| Repeatable across environments | Yes, re-runnable workflow | Manual and error-prone |
| Cost | $499 one-time | Free (built into Terraform) |
The honest tradeoff
The native terraform import command is free and built into Terraform, and it is perfectly fine for a handful of resources. Terraback costs $499 once, and what you buy back is time: it writes the HCL you would otherwise hand-author and turns hundreds of one-by-one imports into a single bulk operation.
Stop hand-writing import commands
Generate Terraform and import blocks for your whole AWS, Azure, or GCP account in one pass - locally, with read-only credentials.