Documentation/Move & maintain
Free

Migrations & definition files

Move supported values, import field structures and check recovery.

On this page

Start with a small staging example

  1. Back up the site and confirm the database requirements below. Keep the original plugin and definitions available.
  2. Open Move data → History & migrations → Start a migration. Choose the content location, source and separately named destination.
  3. Review the exact source and proposed destination values before applying. Verify a small scope before moving more content.
  4. Use the recorded recovery only when the destination has not been changed since the operation.

Supported conversions and recovery

Workflows can copy values and convert supported ACF/Secure Custom Fields and Meta Box structures across posts, users, terms and supported options storage, including supported Clone, Link and Map values, references and registered option prefixes. Choose fields and content in two short steps, then search the exact value review. Mobile comparisons use readable cards. Review source/destination changes before applying. Source metadata is preserved; rollback stops when newer destination edits would be overwritten. Unsupported settings and storage types are refused. Source permissions and the database requirements also apply. This is not a universal automatic site migration.

Secure Custom Fields 6.9.8: ordinary field keys can appear in the source picker while conversion is refused, even for administrators, because SCF restricts generic metadata access. Keep SCF and the original definitions active. Use its supported export tools or a deliberately scoped integration; do not remove its permission checks. Test a separately named destination on staging first.

Import and export definitions

JSON schema import merges groups by key; schema files do not contain post content. Download definitions as JSON through your browser and review imports before applying them. Schema saves and imports do not write files on the server. An existing CUSTOMFIELDS_JSON_DIR setting is supported only as a read-only legacy source for customfields-schema.json; reviewed imports recheck the file and current schema before applying. Source files are never modified. CLI commands cover export, check and explicit guarded import. The administrator JSON importer merges by group key; applied CLI and legacy local-file imports replace the full registry. Content values are retained.