How to migrate from Weglot without losing a word
Everything you have paid Weglot to translate is recoverable while your subscription is still active. Here is the exact process, the order of operations that protects your rankings, and what our autopilot does at every step.
Why the order of operations is everything
Weglot stores your translations on its servers and deletes the project 3 months after cancellation. Cancel first and everything is gone. Migrate first and everything is yours. The entire playbook exists to keep you on the right side of that order.
Keep Weglot running, for now
Do not cancel yet. Your translated pages are only reachable while your subscription is active, and they are the source we migrate from. You will cancel at the end, not the beginning.
Install JurisLingo alongside Weglot
The plugin installs like any other and stays passive while Weglot serves your Spanish pages. A conflict guard makes sure the two never fight over the same URLs.
Run the import while both are live
The Migration Autopilot walks your site, fetches each English page and its live Weglot counterpart, aligns the two structurally, and writes every translation pair into your own WordPress database. Human edits your team made in Weglot ride along, because they are part of the served pages. Our pilot firm imported 139,990 segments in an afternoon.
Fill the gaps Weglot left
Pages Weglot silently skipped at your word cap are detected automatically and machine translated with the legal glossary, so your new Spanish site launches more complete than the one it replaces.
Verify before you switch
Every page is checked against a snapshot of your live Weglot site, with a coverage gate before cutover is allowed. You see the pass and fail numbers for every URL. No leap of faith.
Cut over with one click
One button deactivates Weglot and starts serving your own translations at the same /es/ URLs. The switch is instant; our pilot had zero downtime. A second verification pass then compares the live site against the snapshots again.
Cancel Weglot and submit your sitemap
With your translations safe in your own database, cancel your Weglot subscription, submit the new Spanish sitemap in Search Console, and stop paying rent on content you now own.
The autopilot does this for you, visibly
Every step above runs from one screen in your WordPress admin. You watch the import count climb, see verification pass page by page, and the cutover button stays locked until the coverage gate is met. With the $99 professional setup, our team drives it and you just review the numbers.
- Live progress with per page pass and fail detail
- Human edits imported with their edit status preserved
- English leak checks against pre cutover snapshots
- Instant rollback: reactivate Weglot any time before cancelling
After the migration: what changes day to day
Nothing about your team's workflow changes. They keep publishing English content in WordPress exactly as before, and every new page or edit is translated automatically within seconds, with legal instructions and your glossary. The word counter anxiety is gone because there is no word counter. The bill stops growing because the price is flat. And if you ever cancel JurisLingo, the translations stay in your database and keep serving, which is the whole point of leaving a proxy in the first place.
Deciding between platforms first? Read the full JurisLingo vs Weglot comparison, see what Weglot really costs, or browse the full ranking of translation plugins for law firms.
Weglot migration questions
How long does a Weglot migration take?
For most firm sites, one day. The import runs in parallel and processed roughly 140,000 segments in an afternoon for our 1,400 page pilot firm. Verification adds a few hours. Most firms keep the Weglot overlap under a week, purely for safety margin.
Will my Google rankings drop when I leave Weglot?
The migration is designed so Google sees continuity, not a change: identical /es/ URL structure, the same translations you serve today, correct hreflang and canonicals, and zero downtime at cutover. Our pilot firm's Spanish pages stayed indexed straight through the switch. What does hurt rankings is cancelling Weglot without a replacement: your Spanish pages go dark and Google deindexes them within weeks.
Does Weglot allow this? It is my content, right?
You are reading your own website. The importer fetches pages your own domain publicly serves, exactly like a browser or Googlebot does. The English content is yours, and the migration harvests the translated pages your firm paid to have created and served on your own URLs.
What about my translated URL slugs from Weglot?
If you used Weglot's translated slugs, the importer captures the mapping and JurisLingo serves the same Spanish URLs, so nothing 404s. If you never had translated slugs, you can generate them after migration; old URLs redirect automatically.
Can I migrate to WPML or TranslatePress instead?
You can, but you will be doing it by hand: neither has a Weglot importer, so the usual path is re machine translating your whole site from scratch and losing every human edit your team made in Weglot. If you are below Weglot's Advanced tier, their export is not available to you. The automated, verified import is unique to JurisLingo.
What does the migration cost?
It is included. Early access firms pay $19.99 per month plus a one time $99 professional setup, and the setup includes the full migration, verification and cutover, done by our team.
We migrate you for $99, verified
The one time professional setup includes the entire migration: import, gap filling, verification and cutover, run by the team that has done it in production. Early access is $19.99 per month for the first 5 firms.
Start my migration