---
title: Which option rows are affected
description: "PolyFields manages autoload on three categories of option rows. Understanding which rows are affected helps you interpret database state after import or migration. ## PolyFields stores **PolyFields stores** always saved with `autoload = off` when field values are written (save,…"
url: "https://www.wp-polyfields.com/docs/performance-storage/which-option-rows-are-affected/"
updated: "2026-07-05"
category: "Performance & Storage"
---

# Which option rows are affected

PolyFields manages autoload on three categories of option rows. Understanding which rows are affected helps you interpret database state after import or migration.

## PolyFields stores

**PolyFields stores** always saved with `autoload = off` when field values are written (save, import, migration). The ACF options page autoload setting is not applied to per-language stores. This avoids loading every language's field rows into `alloptions` on every request.

## Import legacy

**Import legacy** unsuffixed source ids from each ACF options page (for example `options_headline`, `_options_headline`, and sub-keys for repeaters or groups). Autoload is disabled while the plugin is active.

## Migration legacy

**Migration legacy** language-suffixed ids from ACF Options for Polylang (for example `options_fr_FR_headline`). Autoload is disabled while the plugin is active.

See [Legacy options autoload](https://www.wp-polyfields.com/docs/performance-storage/legacy-options-autoload/) for the overview and [Autoload snapshot and revert](https://www.wp-polyfields.com/docs/performance-storage/autoload-snapshot-revert-on-deactivation/) for when autoload changes are applied automatically.