What transfers
The original pages. You keep writing one version. LocaleReady translates that same HTML.
Migration
Both plugins keep work on your WordPress site. LocaleReady just starts from automatic translation instead of a visual editor.
The original pages. You keep writing one version. LocaleReady translates that same HTML.
TranslatePress string tables and visual-editor history. Those stay in their own plugin until you uninstall it.
After LocaleReady runs, translations live in its tables, searchable and exportable as JSONL, CSV, or XLIFF. Disable the license later and stored pages still work.
Step 1
Keep TranslatePress active. Install LocaleReady, activate the license, and connect DeepL or Google Cloud Translation.
Step 2
Turn on the same languages TranslatePress already serves. Use the same subdirectory prefixes if you want existing links to keep working.
Step 3
LocaleReady does not read TranslatePress tables. Visit pages or pretranslate from Tools so new strings are stored in LocaleReady's own tables.
Step 4
Copy the important corrections from the TranslatePress editor into LocaleReady's Translations screen. Brand terms can go on the protected-terms list instead.
Step 5
Once the pages you care about are stored, deactivate TranslatePress. Its tables stay in the database unless you uninstall; LocaleReady does not use them.
Feature-by-feature differences:LocaleReady vs TranslatePress.
Not today. Both plugins store translations on your site, but in different tables. LocaleReady translates the live page again and saves its own copy.
Only if you copy them. Automatic first-pass quality is usually close, but names, slogans, and legal lines are worth moving by hand.
Uninstalling can drop its tables. That does not affect LocaleReady. Do not uninstall until you are sure you no longer need those old strings as a reference.
LocaleReady translates new copy as it appears. You only open the Translations screen when a line needs a human.