Migrate from Multilanguage (BestWebSoft)

Multilanguage keeps your translations in its own database tables. That is good news: they are easy to read back out. This page is the honest version of what moving to TranslateRocket — a free multilingual WordPress plugin — actually involves: what comes across, what does not, and how long it takes.

What this plugin does — and where it stops

It stores a translated copy of each post in a separate table, plus another table for taxonomy terms. Your content stays clean; the translations sit alongside it.

Where your translations actually live

Two tables of its own: one for post translations (title, excerpt, content, per language) and one for category and tag names.

What comes across

• Post and page titles, excerpts and content, for every language you filled in.
• Category and tag names — the part most migration guides quietly forget.
• Everything, even if the plugin is already deactivated: the tables stay in your database.

Because the data lives in ordinary tables rather than inside your posts, this is one of the cleanest migrations of the lot. Nothing has to be parsed, so nothing can be misread.

How to migrate, step by step

1. Back up your site. Nothing here modifies your content, but a migration without a backup is a bad habit whatever the tool.
2. Install TranslateRocket from wordpress.org. It is free and there is no account to create.
3. Pick your languages in TranslateRocket → Languages: the language your site is written in, and the ones you already have translations for.
4. Open TranslateRocket → Import. The screen looks at your site and tells you what it found, with a count. If it says nothing was detected, nothing is guessed at.
5. Press the import button for this plugin and let it run. Your original content is untouched.
6. Fill the gaps for free. Whatever the old plugin never covered — menus, theme strings, WooCommerce — can be translated with the translator built into Chrome and Edge: no API key, no account, nothing sent anywhere. We timed it: 464 strings in 42 seconds.
7. Check it, then remove the old plugin when you are satisfied — not before.

What life looks like afterwards

You keep the translations and gain the parts that were missing: interface strings, menus, WooCommerce, SEO meta, and a language switcher you can actually style.

You also get the things a translation plugin is judged on once the novelty wears off: /es/-style URLs with correct hreflang, translated slugs, a language switcher as a shortcode, block or widget, per-page visibility rules, and a translation memory so the same sentence is never translated twice.

Questions people ask before switching

Are my old tables deleted?

No. We only read them. If you later remove the plugin, its tables go with it — but by then your translations are safely stored in TranslateRocket.

Are category and tag names really imported?

Yes, from the second table. It is a small thing that makes a translated site look finished rather than half-done.

What if I already deactivated the plugin?

The import still works. Deactivating a plugin does not drop its tables.

Is there a paid version of TranslateRocket?

No. There is nothing to upgrade to and nothing switched off to push you towards one.

Coming from something else? WPML · Polylang · TranslatePress · Weglot · Loco Translate · Bogo · WPGlobus · WP Multilang · Multilanguage · qTranslate

Leaving a paid plugin? Read the honest comparisons: WPML alternative · TranslatePress alternative · Weglot alternative · GTranslate alternative