Yes, you are right. I checked the database again, and the post counts you mentioned match what I am also seeing there.
However, I am noticing a difference when checking from the WordPress backend and frontend. In the admin panel, there are a total of 8,837 posts. When I randomly edit or view posts in the backend, most of them appear to have both English and Khmer content. From what I can see, only around 300–400 posts seem to exist in English only.
Additionally, on the frontend, the majority of posts are displaying correctly in both languages. This is why I am a bit unsure about the discrepancy: although the database query shows 145 posts with only [:km:], in practice the backend and frontend appear to show both languages for most content.
Because of this uncertainty, I wanted to ask if it would be possible to proceed with the migration in batches. For example, we could migrate the first 500 posts, verify that both languages are handled correctly, and then continue with the next batch. This would help us validate the process step by step and avoid further delays, as this issue has already been pending for quite some time.
Please let me know if this approach would work from your side or if you recommend a different solution.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
From our analysis, the main issue isn’t the migration tool itself but the state of the original qTranslate content. Many posts are missing explicit language markers ([:en], [:km], etc.), which WPML relies on to correctly split and link translations.
qTranslate sometimes “shows” bilingual content in the backend/frontend by falling back to the default language, so it looks fine in the UI even though the database doesn’t have proper markers.
If we migrate without fixing this, WPML will treat those posts as monolingual and they won’t link correctly, creating thousands of orphaned entries.
To avoid that, the best path forward is to normalize the content inside qTranslate first — either by editing and re‑saving posts so markers are added, or by running a bulk script to wrap orphaned content in default language markers. Once the content is clean, the migration will be much smoother and more reliable.
The topic ‘[Closed] qTranslate to WPML migration issue – translations not linked and importer stuck’ is closed to new replies.
