---
title: Migration from “ACF Options for Polylang”
description: "If your site previously used [ACF Options for Polylang](https://wordpress.org/plugins/acf-options-for-polylang/), PolyFields can migrate already-translated option values into its deterministic stores. ## Backup Always back up your database before running migration. Migration writes to WordPress options stores; a backup lets you restore…"
url: "https://www.wp-polyfields.com/docs/import-migration/migration-from-acf-options-for-polylang/"
updated: "2026-07-05"
category: "Import & Migration"
---

# Migration from “ACF Options for Polylang”

If your site previously used [ACF Options for Polylang](https://wordpress.org/plugins/acf-options-for-polylang/), PolyFields can migrate already-translated option values into its deterministic stores.

## Backup

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.

## Before migration

While migration is pending PolyFields does not route options reads and writes to its deterministic stores. Legacy [ACF Options for Polylang](https://wordpress.org/plugins/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](https://www.wp-polyfields.com/docs/getting-started/first-use-workflow/).

## Migration behavior

- 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.

## WP-CLI

The migration can also be run from WP-CLI. See [wp polyfields migrate-bea-options](https://www.wp-polyfields.com/docs/wp-cli-reference/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](https://www.wp-polyfields.com/docs/getting-started/first-use-workflow/).