How to fix Error: Moved block with ambiguous destination in Terraform

First, find which moved blocks are conflicting. Search your configuration files for all moved blocks that have the same to address:

grep -r "to.*=" . --include="*.tf" | grep moved -A 2

Or manually review your moved blocks. The error message should tell you which destination is ambiguous. For example:

# These two blocks conflict
moved {
  from = aws_instance.old_name_1
  to   = aws_instance.new_name  # First source
}

moved {
  from = aws_instance.old_name_2
  to   = aws_instance.new_name  # Second source - CONFLICT!
}

List all moved blocks that point to the same destination.

Examine your Terraform state file to see which resource actually exists:

terraform state list | grep -E "old_name|new_name"

Or view more detail with:

terraform state show aws_instance.old_name_1
terraform state show aws_instance.old_name_2

This will show you which resource currently exists in your state. You need to identify:
- Which from address corresponds to an actual resource in your state
- Whether both exist (in which case you need to consolidate them first)
- Which refactoring move is the correct one

Only one of the conflicting moved blocks should be valid.

Delete the moved blocks that are not correct. Keep only the moved block that accurately reflects how your state needs to be remapped:

# KEEP THIS - if old_name_1 is the actual resource
moved {
  from = aws_instance.old_name_1
  to   = aws_instance.new_name
}

# DELETE THIS - remove the conflicting block
# moved {
#   from = aws_instance.old_name_2
#   to   = aws_instance.new_name
# }

After removing the conflicting moved block, run:

terraform plan

The error should resolve.

If both source resources actually exist in your state file and you genuinely need to consolidate them, you cannot use a single moved block. Instead:

1. Manually consolidate in state first:

# Remove the state of one resource (keeping the other)
terraform state rm aws_instance.old_name_2

2. Then apply your moved block:

moved {
  from = aws_instance.old_name_1
  to   = aws_instance.new_name
}

3. Plan and apply:

terraform plan
terraform apply

Be careful with this approach—removing state should only be done when you're certain that resource instance is no longer needed.

If you're using modules, check for conflicts across module boundaries:

# Parent module
moved {
  from = module.networking.aws_vpc.main
  to   = aws_vpc.shared
}

# Child module (networking/main.tf)
moved {
  from = aws_vpc.main
  to   = aws_vpc.consolidated  # Different destination
}

If you have moved blocks in both parent and child modules targeting overlapping resources, you need to:
- Keep moved blocks only at the appropriate scope
- Remove duplication across module boundaries
- Ensure only one moved block per resource address

Simplify to have moved blocks at just one level (either parent or child, not both).