Back up multilingual data before maintenance
Create a full database backup before cleanup, import with overrides, language retirement, migration, or storage reset. The POM Translate JSON export is useful additional protection, but it is not a complete backup.
Minimum backup set
Preserve:
- the WordPress database for the affected site;
- a fresh POM Translate JSON export;
- the site's uploads and any deployment-managed files;
- the current language, content-type, selector, and machine-translation settings;
- a list of published localized routes that must continue working.
In multisite, make sure the database backup includes the tables and options for the exact subsite. POM Translate uses the current site's table prefix for its translation storage.
Before a destructive tool
- Pause editorial and machine-translation work.
- Record the current date, environment, site URL, and active plugin version.
- Create and verify the database backup.
- Download a new translation export.
- Store both artifacts outside the WordPress installation.
- Confirm you know how to restore the database before continuing.
Do not put exports containing customer or unpublished content in a public media library or support ticket.
Understand restoration coverage
The JSON file can restore matching translated text and statuses only. A database restore is required to recover localized slugs, custom URL translations, skeletons, exclusions, settings, and other plugin data removed by a reset.
Restoring the database also rolls back unrelated site changes made after the backup. Prefer staging and schedule a maintenance window when a production restore could affect orders, submissions, or editorial changes.
Verify recovery readiness
Open the JSON file to confirm it is valid and non-empty. Verify the database archive exists, is readable, and belongs to the intended site and time. A backup that has not been identified and checked should not be treated as a rollback plan.