Integrations · ACF

ACF Fields That Still Work After the Push

ACF doesn't store an image, gallery, or related post inside the field — it stores an ID that points at one. Copy that ID to another WordPress site and it points at nothing, or at the wrong thing entirely. PostDeploy Pro resolves it to what it should actually point to on the destination.

What breaks when ACF fields migrate as plain data

Every one of these is the same root cause: the field stores an ID, and a plain copy or import doesn't know the ID needs to change.

Image, file & gallery fields

Still reference the source site's attachment IDs — the destination has no idea those IDs mean anything, so the field renders empty.

Relationship & post object fields

Point at a post ID that may not even exist on the destination, or that now belongs to a completely different piece of content.

Repeater & Flexible Content

Naive migration tools only check top-level fields — references buried inside a Repeater, Flexible Content, or Group sub-field get skipped entirely.

Taxonomy & User fields

A Taxonomy field's term ID, or a User field's account ID, rarely matches between two separate WordPress installs.

What Pro resolves

Every field type that actually shows up in practice

  • Image
  • File
  • Gallery
  • Relationship
  • Post object
  • Repeater
  • Flexible Content
  • Group
  • Taxonomy → by slug
  • User → matched account

Taxonomy fields resolve by slug, matching or creating the equivalent term on the destination. User fields match against the destination site's own accounts.

FAQ

Frequently asked questions

Do I need the free PostDeploy plugin too?

No. PostDeploy Pro has its own complete, independent engine built in — installing just Pro gives you everything, including Posts/Pages/CPT migration and unlimited connections, not only the ACF resolution described here.

Does this work inside Repeater and Flexible Content fields?

Yes. Image, file, gallery, relationship, and post object sub-fields are resolved wherever they appear, including nested inside Repeater, Flexible Content, and Group fields — not just at the top level of a field group.

What happens to Taxonomy and User fields?

Taxonomy fields resolve by slug, matching or creating the equivalent term on the destination. User fields match against the destination site's own user accounts.

Stop re-attaching images and relationships by hand.

Start free, or get Pro for ACF, Elementor, WPML, Divi, rollback, and automation.

PostDeploy Pro — stop copy-pasting content between WordPress sites.

Get Pro