Migrate Polylang to WPML

Import multilingual data from Polylang to WPML

Installation and usage

• Backup your database! There is a reason why this plugin has the version number 0.1
• Deactivate Polylang.
• Activate both WPML Multilingual Blog/CMS and the (Migrate Polylang to WPML) plugins. If you also want to migrate string translations, activate WPML String Translation plugin.
• Finish the WPML Wizard (you will see it right after activation)
• If you have custom post types, go to WPML > Translation options (or WPML > Translation Management > Multilingual Content Setup) and set those types to be translatable.
• Go to Tools > Migrate from Polylang to WPML
• Click button "Migrate" and wait until the migration process is completed (it might take longer based on the size of the content you are migrating)
• Done. You can uninstall the (Migrate Polylang to WPML) plugin.

What this plugin does

• Configures WPML to have the same languages as they were in Polylang.
• Migrates all your posts, pages and custom post types and their translations.
• Migrates all your taxonomies (categories, tags and custom taxonomies) and their translations.
• Migrates your strings (only those which has been translated in Polylang and WPMl String Translation recognized and registered as correct string)
• Migrate widgets: You will need to activate WPML Widgets plugin.

What this plugin doesn't (yet)

• Migrate menus: Use the menu synchronization between languages option in WPML.
• Migrate other settings: This will be implemented progressively. For the time being, you are free to adjust them manually after the migration process is completed.

Support and feedback

• please report any issue or feature request at WPML forum
• please check Wiki page for known issues

Development

The development tools require PHP 7.4 or newer and Composer 2. Install the locked dependencies with:

composer install --no-plugins --no-scripts

Run all local checks with:

composer check

The individual commands are composer test, composer phpcs, and composer phpstan. PHPUnit uses WordPress function mocks, so it does not require a WordPress installation or database. PHPStan analyzes the production plugin at level 3 with WordPress and WPML stubs. PHPCS initially covers the new test and analysis support code; the legacy production files will be introduced separately after their existing violations are addressed.

CI runs the unit tests on the supported endpoints, PHP 7.4 and 8.5. Coding standards and static analysis run on PHP 8.5.

Changelog

0.5.2

• Fixed taxonomy migration for languages whose Polylang slugs differ from their WPML language codes, including Portuguese and Chinese.
• Fixed language-code handling for post translation groups, including groups without a translation in the site's default language.
• Prevented orphaned Polylang taxonomy translation groups from overwriting valid WPML relationships.
• Improved PHP 8 compatibility when migrating incomplete or corrupt Polylang data.

0.5.1

• Added capability and nonce checks to all migration and data-deletion AJAX actions.
• Escaped admin output and sanitized the .htaccess notice dismissal cookie.
• Prevented direct access to the plugin's PHP files.

0.5.0

• Automatically set the translation preference to "translate" for translated custom post types.
• Added the support for duplicated (synced) posts.
• Fixed a fatal error "Uncaught TypeError: Cannot access offset of type string on string".
• Fixed several PHP warnings.

0.4

• Fixed an issue with not terminating import when importing terms.

0.3

• Resolved an issue with migration stopping on nginx server.

0.2

• Fixed the migration of Chinese languages and Portuguese (pt-pt and pt-br) languages.
• Fixed a case when the user has set synchronisation options (comp-3271).

0.1

• Initial release.