No translation group on arrival
Each language is a completely separate post with its own ID — importing the content doesn't automatically register which group it belongs to on the destination.
Integrations · WPML
WPML stores each language as its own separate post, joined only by a translation group ID. Migrate the content without registering that link on the destination, and it just sits there as an ordinary, disconnected post — the language switcher won't find it.
Each language is a completely separate post with its own ID — importing the content doesn't automatically register which group it belongs to on the destination.
Without the group link, WPML has no idea the new post is related to anything — it won't show up as a translation option anywhere.
Pushing the first language of a group to a new site has to start a fresh group; pushing a second or third language later has to link into the group that's already there.
Either. Push one language on its own, or push every language in a translation group together — both are supported.
PostDeploy links the new translation into the existing group on the destination instead of starting a new one, so the language switcher correctly shows all of them together.
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 WPML resolution described here.
Why a translation is a separate post to begin with, what actually has to happen, and the part that's easy to get subtly wrong.
WPML resolution alongside ACF, Elementor, Divi, rollback, bulk & scheduled deployment, and automation.
Start free, or get Pro for WPML, ACF, Elementor, Divi, rollback, and automation.
PostDeploy Pro — stop copy-pasting content between WordPress sites.
Get Pro