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.
Integrations · ACF
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.
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.
Still reference the source site's attachment IDs — the destination has no idea those IDs mean anything, so the field renders empty.
Point at a post ID that may not even exist on the destination, or that now belongs to a completely different piece of content.
Naive migration tools only check top-level fields — references buried inside a Repeater, Flexible Content, or Group sub-field get skipped entirely.
A Taxonomy field's term ID, or a User field's account ID, rarely matches between two separate WordPress installs.
Taxonomy fields resolve by slug, matching or creating the equivalent term on the destination. User fields match against the destination site's own accounts.
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.
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.
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.
Start free, or get Pro for ACF, Elementor, WPML, Divi, rollback, and automation.
PostDeploy Pro — stop copy-pasting content between WordPress sites.
Get Pro