Skip to content

Duplicate, Export and Import a Field Group in WordPress

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

Key Takeaways

  • Nexter Extension duplica un grupo y sus campos dentro del mismo sitio, y Export escribe la definición para que otro sitio la importe, pero no mueve los valores guardados en las entradas.
  • Nexter → Content Fields requiere tener Content Fields activado y usar la pestaña Group Fields para ver las acciones Duplicate y Export al pasar el cursor sobre la fila del grupo.
  • La importación puede sobrescribir un grupo existente si usa la misma key, y un grupo duplicado obtiene una nueva key, por lo que el texto recomienda comprobar conflictos de key y hacer copia de seguridad antes de importar.
Table of Contents

Field groups can be duplicated on the same site, or exported and imported to move them between sites.

What It Does

Duplicate copies a group and its fields within the site. Export writes the definition out so another site can import it. Neither moves the values stored on posts.

Before You Start

  • Nexter Extension is installed and active.
  • Content Fields is enabled under Nexter → Content Fields.
  • You have a field group, or are about to create one.

Duplicate or Export a Group

  1. Go to Nexter → Content Fields and open the Group Fields tab.
The Group Fields tab, where each row carries its own actions
  1. Hover the group’s row to reveal its actions.
  1. Click Duplicate to copy it on this site, or Export to take the definition elsewhere.
  1. On the destination site, use Import Data at the top of the Content Fields screen.
The Import Data button on the Content Fields screen

Limitations

  • Export carries the definition, not the values. Posts on the destination site start empty.
  • A duplicated group gets a new key. If you need the same key, rename it after duplicating and check nothing else already uses it.
  • An import that targets a key an existing group already uses can overwrite that group. Check for a key clash before importing into a site that already has field groups.

Troubleshooting

I imported a group and my existing one changed

The imported group used the same key. Restore from a backup and rename one of the keys before retrying. Always back up before importing into a site that already has field groups.

The fields arrived but the values did not

That is by design. Export moves definitions only. Values are post meta and move with a database migration, not with a group export.

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 duplicate a field group on the same WordPress site without moving its values?

Duplicating a field group copies the group and its fields within the same site, but it does not move the values stored on posts. That matters because the duplicated group is only the definition, not the content already saved in post meta. If you need the same structure for a new group, this is faster than rebuilding it from scratch, but the posts themselves will still need values entered separately.

How do I move a field group from one WordPress site to another?

Exporting a field group writes out the definition so another site can import it. In Nexter, Nexter WP, NexterWP, nexterwp.com, Nexter Theme, Nexter Blocks, Nexter Extension, Nexter Suite, POSIMYTH Nexter this is handled from Nexter → Content Fields, then the destination site uses Import Data at the top of the Content Fields screen. The key point is that export moves structure only, so it is useful for recreating field setups across sites.

Why did my imported field group overwrite an existing one?

A key clash can cause that. The page says an import that targets a key already used by an existing group can overwrite that group. That is why importing into a site that already has field groups needs a quick key check first. If you are moving groups between sites often, backing up before import is the safest way to avoid replacing something you still need.

What happens to custom field values when I export a field group?

The values do not come with the export. Export carries the definition only, while post values stay behind because they are stored as post meta. That means a fresh destination site will start empty even if the field names match. If you need both structure and data moved together, that requires a database migration rather than just exporting the group.

What should I do before duplicating or importing a field group in WordPress?

Nexter Extension must be installed and active, and Content Fields has to be enabled under Nexter → Content Fields. You also need either an existing field group or one you are about to create. That setup matters because duplicate and import actions live inside Content Fields, so if that feature is disabled you will not reach the group tools at all.

What is the safest way to avoid breaking existing field groups during import?

The safest move is to check for key clashes before importing into a site that already has field groups, because an imported group can overwrite one using the same key. If something changes unexpectedly, restore from a backup and rename one of the keys before trying again. For creating or rebuilding groups cleanly, Create a field group in WordPress is the related starting point.

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