Accepted in version 0.1.0
Database-owned definitions and unambiguous ACF Local JSON definitions are supported. Posts, pages, post-based custom post types, WooCommerce products, postmeta-backed product variations, revisions, and autosaves can be included when exact field-key references exist.
- Top-level value-bearing field
- Post-based field-group location rules
- Stable, unique ACF field key
- One source value row plus one _field_name reference row owned by that key
Refused before migration writes
Unsupported selections do not create a migration.
- Nested fields; Repeater, Flexible Content, Group, Clone, Tab, Accordion, and Message types
- PHP-registered definitions
- Options, users, terms, comments, widgets, menus, blocks, attachments, and ACF definition records
- WooCommerce HPOS orders and refunds
- Ambiguous or missing Local JSON source files
- Duplicate field keys, source rows, destination rows, foreign destination references, or cross-store ownership
New-name rules
A new name must begin with a lowercase letter and contain only lowercase letters, numbers, underscores, or dashes. It may be at most 191 characters, must survive WordPress sanitization unchanged, must differ from the current name, and must not collide with another active ACF field name.