cloudflare_record -> cloudflare_dns_record v5

[barapz]

Confirmation

• This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
• I have searched the issue tracker and my issue isn't already found.
• I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

• OpenTofu version: (1.11.6)
• Cloudflare provider: v4.52.5 → v5.19.0

Affected resource(s)

cloudflare_dns_record

Terraform configuration files

resource "cloudflare_dns_record" "xyz" {
  zone_id = var.cf_zone_id
  name    = ""
  content = ""
  type    = "CNAME"
  proxied = true
  ttl     = 1
}

Link to debug output

---

Panic output

no schema available for cloudflare_record.xyz while reading state; this is a bug in OpenTofu and should be reported

Expected output

Automatic migration should be sucessfull.

Actual output

see Panic

Steps to reproduce

Steps to Reproduce

1. Have a resource of type cloudflare_record managed in state (Cloudflare provider v4)
2. Upgrade to Cloudflare provider v5 (which renames it to cloudflare_dns_record)
3. Add a moved{ from = cloudflare_record.xyz}
4. Run terraform plan

Additional factoids

Only known workaround that I've found is removing from the tfstate completely and re-importing by ID - which is quite the hassle.

References

No response

[KaydeeDee]

Thank you for submitting an issue! This issue has been flagged for an internal Cloudflare team to take a look. If this is urgently blocking your development or deployment, please open a support case so we can serve you faster.

[vaishakdinesh]

Hi @barapz the bug report says

this is a bug in OpenTofu and should be reported

The issue is on the OpenTofu side, not the provider side. OpenTofu forked from Terraform 1.6, and the MoveResourceState RPC was added in Terraform 1.8. When OpenTofu encounters a moved block where the source resource type (cloudflare_record) no longer exists in the current provider, it tries to look up the schema for that type, fails, and errors out — before it ever calls the provider's MoveState handler.

Workarounds for OpenTofu Users
2. Use terraform state mv — Instead of the moved {} block, manually run:
tofu state mv cloudflare_record.xyz cloudflare_dns_record.xyz
This should trigger the UpgradeFromLegacyV3 state upgrader (schema_version=3 path in migrations.go:44-47).
3. Remove and re-import (user's current workaround, most tedious).

@KaydeeDee