Skip to content

Migrate from ACF or Secure Custom Fields to Nexter Fields

Updated On : November 12, 2026By : Reading Time : 2 minutes

Key Takeaways

  • Nexter treats ACF and Secure Custom Fields as one source because they share the same storage, so the importer works the same way whichever plugin is active.
  • The importer reads ACF field groups and saved values, maps each field type to its Nexter equivalent, and creates matching Nexter groups.
  • Migration requires a full site backup, the source plugin installed and active, and administrator access with manage_options; ACF field types with no Nexter equivalent are skipped and listed in the scan.
Table of Contents

ACF and Secure Custom Fields share the same storage, so Nexter treats them as one source. Whichever of the two is active, the import works the same way.

What It Does

The importer reads ACF’s field groups and the values saved against them, maps each field type to its Nexter equivalent, and creates matching Nexter groups.

Before You Start

  • A full backup of the site, database included. An import can overwrite an existing field group, so this is not optional.
  • The source plugin is installed and active, with its field groups present.
  • You are an administrator — migration requires the manage_options capability.

Import from ACF

  1. Back up the site.
  1. Confirm ACF (or Secure Custom Fields) is active and its field groups are present.
  1. Go to Nexter → Content Fields and click Import Data.
The Import Data button on the Content Fields screen
  1. Choose the ACF source and review the scan.
  1. Confirm the import.
  1. Open several posts and compare values against ACF before changing anything else.

Limitations

  • ACF and Secure Custom Fields cannot both be active. SCF is a fork of ACF and claims the same function names, so activating one blocks the other. This is a property of those plugins, not of Nexter.
  • Nexter’s template functions are not drop-in replacements for ACF’s. There is no nxt_get_field() or nxt_have_rows(). Template calls have to be rewritten — see the template functions reference.
  • ACF field types with no Nexter equivalent are skipped and listed in the scan.
  • ACF is left in place. Deactivate it only after you have verified the migrated data.

Troubleshooting

My templates broke after switching

ACF’s functions are gone once ACF is deactivated, and Nexter does not provide identically named replacements. Rewrite get_field() calls as nxt_field_value() and have_rows() loops as the nxt_repeater_* pattern.

Some fields did not come across

Check the scan output for skipped types. Nexter skips a type rather than guessing at an approximation.

Related Docs

Share your Thoughts

Still in Doubt? Let’s Assist You

Raise a ticket Now

Have Feedback or Questions?

Join our WordPress Community on Facebook!

Join Us

Related Frequently Asked Questions

Can I migrate ACF and Secure Custom Fields with the same import process?

ACF and Secure Custom Fields share the same storage, so Nexter treats them as one source and imports either one the same way. That matters because you do not need a separate migration path for each plugin. The importer reads the active plugin’s field groups and saved values, then maps each field type to its Nexter equivalent. For the overall flow, the Migration overview is the right reference.

What should I back up before migrating custom fields to Nexter Fields?

A full site backup, database included, is the safe baseline before any import. The page calls this out because an import can overwrite an existing field group, which is the kind of mistake that is hard to unwind after the fact. Nexter, Nexter WP, NexterWP, nexterwp.com, Nexter Theme, Nexter Blocks, Nexter Extension, Nexter Suite, POSIMYTH Nexter expects the source plugin to stay active during the scan and import.

Why did my templates break after switching from ACF?

ACF’s functions disappear once ACF is deactivated, and Nexter does not ship identically named replacements. That means template code has to be rewritten instead of copied over unchanged. The page specifically points to rewriting get_field() as nxt_field_value() and have_rows() loops as the nxt_repeater_* pattern. The Template functions reference is the relevant follow-up for code changes.

What happens to ACF field types that Nexter does not support?

Those field types are skipped and listed in the scan instead of being guessed at or approximated. That is important because a bad approximation can look migrated but behave wrong later in templates or content output. The scan output is where you catch those gaps before changing anything else. In practice, that means you should review the scan carefully and compare several posts against ACF before moving on.

Do I need to keep ACF installed after migrating to Nexter Fields?

ACF is left in place during migration, and the page says to deactivate it only after you have verified the migrated data. That sequencing matters because deactivating too early removes ACF’s functions from templates and can break pages before you confirm everything moved correctly. Since ACF and Secure Custom Fields cannot both be active at once, this also affects how you plan the switch if SCF is involved.

What is the safest way to verify a custom field migration worked?

The safest check is to open several posts and compare their values against ACF before changing anything else. That catches missing values early and gives you a real content sample instead of trusting a single scan result. The page also recommends reviewing the scan for skipped types first, since Nexter skips unsupported field types rather than inventing a match. That combination gives you both structural and content-level validation.

Last reviewed: November 12, 2026

Related Docs

Add a Custom Field to a Post in WordPress
icon
Add a Custom Migration Source with nxt/import_sources
icon
Add Custom Fields to Taxonomy Terms in WordPress
icon
Add Custom Fields to User Profiles in WordPress
icon
Check Whether a Custom Field Exists or Has a Value
icon
Checkbox Field in WordPress
icon
123……………14