Migration from “ACF Options for Polylang”

If your site previously used ACF Options for Polylang, PolyFields can migrate already-translated option values into its deterministic stores.

Always back up your database before running migration. Migration writes to WordPress options stores; a backup lets you restore the prior state if anything goes wrong.

While migration is pending PolyFields does not route options reads and writes to its deterministic stores. Legacy ACF Options for Polylang option rows remain the authoritative source on the site. If ACF Options for Polylang is still active, it continues to handle language-aware option routing during this period.

Normal PolyFields store routing begins after migration completes or after you dismiss the first-use assistant with Skip migration. See First-use workflow.

• The migration only fills empty values and does not overwrite current PolyFields content.
• It does not apply field translation modes to the migrated values.
• The migrator does not delete source option rows. Remove or archive those rows separately if needed after verifying the migrated values.

The migration can also be run from WP-CLI. See wp polyfields migrate-bea-options for command details and the --overwrite flag.

For the first-use assistant that offers migration in the admin, see First-use workflow.