Migrate translations across sites

When migrating translations between sites, it’s important to ensure that the content remains identical across both sites, including maintaining the same post IDs. The translations in the main tables are independent of the post ID, but there are still some associations, particularly with search results in translated languages and user-related data.

When migrating, it’s recommended to copy the standard WordPress tables. This ensures that the content and structure are preserved correctly, minimizing potential issues with custom data or configurations.

Translations can only be used if the same default and additional languages are retained, as TranslatePress stores translations directionally in the database—from the default language to each additional language.

Since TranslatePress does not duplicate content for independent migration, translations remain linked to the default language content in the database. To migrate them, export the translations in .sql format and import them directly into the new database.

How to migrate translations manually between websites

If you’re looking to migrate all translations and plugin data, you’ll need to access your database using a management tool like phpMyAdmin and manually export the relevant tables, options, and metakeys.

Below are the steps required to transfer all plugin data (including translations) to your new database:

1. Migrating the tables

Here is a list of all the tables which are created by TranslatePress:

• wp_trp_dictionary* – the dictionary tables contain manually or automatically translated strings
• wp_trp_gettext* – the gettext tables contain theme/plugin strings that already have a translation
• wp_trp_gettext_original_meta – the gettext tables contain theme/plugin strings
• wp_trp_gettext_original_strings – the gettext tables contain theme/plugin strings
• wp_trp_original_strings – the original strings table contains strings in the default language, without any translation
• wp_trp_original_meta – the original meta table contains meta information which refers to the post parent’s id
• wp_trp_slug_originals – the original slug table contains slugs in the default language, without any translation (This table is added starting with TranslatePress Multilingual 2.8.4, TranslatePress Personal 1.2.9, and TranslatePress Business/Developer 1.4.2)
• wp_trp_slug_translations – the slug translation table contains manually or automatically translated strings (This table is added starting with TranslatePress Multilingual 2.8.4, TranslatePress Personal 1.2.9, and TranslatePress Business/Developer 1.4.2)

2. Migrating the options and meta keys

Here is a list of all the options and meta keys created by TranslatePress, along with the tables in which they are inserted:

• _postmeta table – meta keys inserted into the _postmeta table have the trp_ prefix (We no longer store information in this table starting from TranslatePress Multilingual 2.8.4, TranslatePress Personal 1.2.9, and TranslatePress Business/Developer 1.4.2.)
• _termmeta table – meta keys inserted into the _termmeta table have the trp_ prefix (We no longer store information in this table starting from TranslatePress Multilingual 2.8.4, TranslatePress Personal 1.2.9, and TranslatePress Business/Developer 1.4.2.)
• _options table – options inserted into the _options table have the trp_ prefix
• _usermeta table – meta keys inserted into the _usermeta table have the _trp_ prefix