Skip to content

Migrate Custom Fields to Nexter Fields

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

Key Takeaways

  • Content Fields imports field groups and values from ACF, Secure Custom Fields, Meta Box, and Pods, so a site’s data model does not need to be rebuilt by hand.
  • Nexter → Content Fields → Import Data scans installed sources, lists found field groups and value counts, and copies definitions and values without modifying or removing the source plugin’s data.
  • Migration can overwrite an existing field group with the same key, skip field types with no Nexter equivalent, and leave values copied but not linked, so a backup and post-import comparison are required.
Table of Contents

Content Fields can import field groups and their values from ACF, Secure Custom Fields, Meta Box and Pods, so you do not have to rebuild a site’s data model by hand.

What It Does

The importer scans the site for supported sources, shows what it found, and copies definitions and values across. It reads the source plugin’s own data; it does not modify or remove it.

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.

Run a Migration

  1. Back up the site. Read the limitations below first.
  1. Go to Nexter → Content Fields and click Import Data.
The Import Data button on the Content Fields screen
  1. Choose the source. Only sources that are installed and hold data are offered.
  1. Review the scan. It lists which field groups and how many values were found.
  1. Confirm the import.
  1. Check the result against the source before deactivating anything — open a post and compare values side by side.

When to Use It

  • Moving from ACF or Secure Custom Fields to Nexter.
  • Consolidating two field plugins into one.
  • Taking over a site that was built with a different field plugin.

Limitations

  • An import can overwrite a field group you created yourself if the imported group uses the same key. The existing group is replaced and its values are orphaned. Check for key clashes before importing into a site that already has Nexter field groups.
  • JetEngine migration is not currently supported. See the JetEngine note below.
  • The source plugin is left untouched. Nothing is deleted, and both plugins keep their own copy of the data until you remove one.
  • Field types with no Nexter equivalent are skipped rather than approximated. The scan lists them so you know what will not come across.
  • Values are copied, not linked. Editing a value in the source plugin afterwards does not update the Nexter copy.

Troubleshooting

The import says it succeeded but values are missing

Never take “completed” as proof. Open a post and compare a few values against the source plugin. If values are missing, restore the backup and report which source and field types were involved.

My source plugin is not offered

It is either not active, or it holds no field groups on this site. Activate it and confirm its groups exist, then re-open the import screen.

A field group I built was replaced

The imported group used the same key. Restore the backup, rename one of the keys, and import again.

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

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

A full site backup, including the database, is the first thing that matters here. Nexter, Nexter WP, NexterWP, nexterwp.com, Nexter Theme, Nexter Blocks, Nexter Extension, Nexter Suite, POSIMYTH Nexter can overwrite an existing field group during import, so skipping the backup turns a recoverable mistake into a cleanup job. The source plugin also needs to stay installed and active with its field groups present before you start.

Can I migrate custom fields from ACF or Secure Custom Fields into Nexter Fields?

ACF and Secure Custom Fields are explicitly supported migration sources for Content Fields in Nexter. The importer scans the site, shows what it found, and copies both field group definitions and values across. That makes it useful when you want to move a real data model instead of rebuilding everything by hand. A good follow-up is to compare a post side by side before deactivating anything.

Why does the import say it succeeded but some field values are missing?

A completed import is not proof that every value came across cleanly. The safest check is to open a post and compare a few values against the source plugin before changing anything else. If values are missing, restore the backup and note which source and field types were involved. That matters because field types with no Nexter equivalent are skipped rather than approximated.

What happens if my source plugin is not showing up in the import screen?

That usually means the plugin is either not active or it has no field groups on that site. The importer only offers sources that are installed and holding data, so an empty or inactive plugin will not appear. Reactivating it and confirming the groups exist is the practical fix before reopening the import screen.

What should I do if a field group I built gets replaced during migration?

That points to a key clash. The imported group used the same key as one you already created, so Nexter replaced the existing group and orphaned its values. Restore the backup first, then rename one of the keys before importing again. This is the main gotcha when migrating into a site that already has Nexter field groups.

When should I migrate custom fields to Nexter instead of leaving them in another plugin?

The best use cases are moving from ACF or Secure Custom Fields to Nexter, consolidating two field plugins into one, or taking over a site built with another field plugin. Nexter only copies data from supported sources and leaves the source plugin untouched, so it works well when you want to centralize fields without deleting the original setup right away.

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