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.
Edits that only live inside TranslatePress. Those stay there until you copy the ones you still need.
After LocaleReady runs, translations live in WordPress, where you can search them, edit them, or export a file. If you cancel, those pages still work.
Step 1
Keep TranslatePress on. Install LocaleReady, add your key, and connect DeepL or Google.
Step 2
Turn on the same languages TranslatePress already serves. Use the same folders, like /es/, if you want existing links to keep working.
Step 3
LocaleReady doesn't read TranslatePress's saved translations. Visit the pages, or translate the site ahead of time from Tools, so the new copies are saved.
Step 4
Copy the important corrections from TranslatePress into LocaleReady's Translations screen. Brand names can go on the “leave these as written” list instead.
Step 5
Once the pages you care about are saved, deactivate TranslatePress. Its old translations stay in the database unless you uninstall. LocaleReady doesn't use them.
Feature-by-feature differences:LocaleReady vs TranslatePress.
Not today. Both plugins save translations on your site, but not in a way we can read across. LocaleReady translates the live page again and saves its own copy.
Only if you copy them. The automatic first pass is usually close, but names, slogans, and legal lines are worth moving by hand.
Uninstalling can remove its saved translations. That doesn't affect LocaleReady. Don't uninstall until you're sure you no longer need those old lines as a reference.
LocaleReady translates new copy as it appears. You only open the Translations screen when a line needs a human.