Resolving 409 Conflict on genesyscloud_auth_division during Terraform Apply

What is the standard approach to handle immutable attributes when terraform apply fails with a 409 Conflict on genesyscloud_auth_division? I am migrating flows and need stable IDs.

resource "genesyscloud_auth_division" "prod" {
 name = "Main"
}

Error: 409 Conflict: Name already exists. The REST API supports PATCH updates, yet the provider blocks this. How do I force an update without destroying the resource and breaking my Data Actions?