What transfers
The pages you still write. Themes, products, and forms stay as they are.
Migration
WPML gives each language its own page. LocalePro translates the page you already edit, and saves the result.
The pages you still write. Themes, products, and forms stay as they are.
WPML's extra pages, translation jobs, and leftover credits. LocalePro doesn't read those.
One page. Translations are saved beside it. Edit the original, and the other languages catch up without a second round of editing.
Step 1
WPML's extra language pages can stay for now. Install LocalePro on the content you write in.
Step 2
Add a DeepL or Google key. Turn on the languages WPML already publishes. LocalePro uses an address like /es/, not a second page per language.
Step 3
LocalePro does not copy WPML's extra pages. It translates the original and saves the result in WordPress.
Step 4
Keep them as a reference, redirect them to LocalePro's language addresses, or leave them unpublished. Don't delete them until you've checked incoming links.
Step 5
Deactivate WPML after LocalePro's addresses are live and the redirects are in place. Those extra pages don't keep the site translated once WPML is gone.
Day-to-day differences:LocalePro vs WPML.
There isn't an automatic import. WPML stores a separate WordPress page per language. LocalePro keeps one page and saves translations beside it. Those two setups don't line up one for one.
Those linked pages stop being served as translations. If you still want those addresses, add redirects to LocalePro's language folders before you deactivate WPML.
Yes, as a correction or a choice on that page, not as a second copy of the whole site. If every market needs wholly different pages, WPML's approach may still fit better.
A yearly price for your sites. Translation goes to DeepL or Google, not a pack of credits.