WPML All Import

Importing multilingual content is usually more involved than loading a single set of posts into WordPress. WPML All Import is built for that job, combining CSV and XML imports with WPML so translated content and language relationships can be handled during the import process. It targets site owners, developers and agencies managing more than one language, especially where posts, products or custom content already exists in structured files.

Multilingual imports

The main appeal is the connection between bulk importing and translation management. Instead of treating each language as an unrelated batch of records, the plugin is intended to keep multilingual content organised through WPML. That gives an import workflow a clearer place for translated posts, pages and products, while content synchronisation remains part of the wider WordPress setup.

This is useful for migrations and recurring catalogue work. A site moving content from structured files does not have to limit the process to standard blog posts. The feature list covers pages, custom post types and taxonomies, so the same general approach applies to sites whose content model extends beyond the default WordPress fields.

Flexible field mapping

Import files rarely mirror a WordPress installation perfectly. WPML All Import addresses that mismatch with custom mapping options, allowing values from the source file to be matched with WordPress fields. That matters when an import contains custom fields, different column names or a content structure designed for another system.

• Import posts, pages and custom post types in multiple languages.
• Bring in taxonomies alongside the content that uses them.
• Read source data from CSV and XML files.
• Map file values to WordPress fields.
• Schedule imports for recurring updates.
• Handle multilingual WooCommerce products.
• Use detailed logs and error reporting when an import needs investigation.

The logging and error reporting are particularly relevant to larger or repeated imports. They provide a way to inspect problems rather than relying only on the final visible result in the site.

Stores and site builders

WooCommerce support extends the plugin beyond editorial migrations. Multilingual product imports are aimed at stores that need product information managed across languages, rather than importing products once and translating them manually afterwards. Scheduled imports also suit catalogues or content sets that receive regular updates from an external CSV or XML source.

The vendor also lists compatibility with popular page builders and themes. That broadens the range of sites the plugin is intended to serve, although the copy does not identify particular builders, themes or field configurations. The practical value therefore rests on how closely a site’s content structure matches the available mapping options.

What to weigh

The flexibility comes with preparation work. CSV and XML imports still require a well-structured source file, and custom mapping means someone must understand both that file and the destination fields. WPML adds another layer to the process: language relationships and translation records need to be represented correctly rather than treated as ordinary standalone posts.

Scheduled imports are useful for automation, but they also make source-file accuracy an ongoing concern. A recurring job repeats the rules it has been given, so an incorrect mapping or incomplete source can be repeated across updates. The logging tools help locate import errors, but they do not remove the need to review the imported content. Compatibility with popular builders and themes is encouraging, though the lack of named integrations leaves some project-specific questions unanswered.

Who it suits

WPML All Import fits multilingual WordPress projects with content already held in CSV or XML files, particularly sites managing custom post types, taxonomies or WooCommerce products. It is a practical candidate for developers and agencies handling migrations, as well as editors responsible for recurring multilingual updates.

It is less compelling for a small site with a handful of pages and no structured source data. The plugin’s value appears when there is enough content to justify field mapping, language-aware imports, scheduled updates and import logs. For those projects, it brings the import task and WPML’s multilingual organisation into the same workflow.