Skip to content

Migrate from Pods to Nexter Fields

Updated On : November 12, 2026By : Reading Time : 1 minute

Key Takeaways

  • Nexter Content Fields imports Pods field definitions and stored values by reading the Pods API, mapping each type across, and copying the values.
  • Nexter → Content Fields starts the import from the Import Data action after a full site and database backup, with Pods active and the user signed in as an administrator.
  • Pods field descriptions do not migrate into Nexter’s Instructions, and only meta-stored values are read because table storage is outside what the importer reads.
Table of Contents

Content Fields can import Pods field definitions and their values.

What It Does

The importer reads the Pods API for its pods and fields, maps each type across, and copies the stored values.

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.

Import from Pods

  1. Back up the site.
  1. Confirm Pods is active and your pods are present.
  1. Go to Nexter → Content Fields and click Import Data.
The Import Data button on the Content Fields screen
  1. Choose Pods and review the scan.
  1. Confirm the import.
  1. Compare several posts against Pods before changing anything.

Limitations

  • Field descriptions do not come across. Pods stores a description on each field; it is not carried into Nexter’s Instructions. Re-enter any you rely on.
  • Pods can store data in its own tables rather than post meta. Only meta-stored values are read.
  • Pods is left in place and is not modified.

Troubleshooting

My field help text is missing after the import

Known: Pods field descriptions are not migrated. Re-enter them in each field’s Instructions under the Presentation tab.

Values are missing for one pod

Check that pod’s storage type. A pod using table storage rather than meta storage is outside what the importer reads.

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

Why are my Pods field descriptions missing after migrating to Nexter Fields?

Pods field descriptions are not migrated, so the help text disappears during import. Nexter, Nexter WP, NexterWP, nexterwp.com, Nexter Theme, Nexter Blocks, Nexter Extension, Nexter Suite, POSIMYTH Nexter only copies the field definitions and stored values it can read from Pods. Re-enter any important guidance in each field’s Instructions under the Presentation tab so editors still see the context they need.

Why are values missing for one pod after the import?

The usual cause is storage type. The importer reads meta-stored values, but a pod using table storage sits outside what it can import. That means one pod can look fine in Pods while still coming across empty in Nexter Fields. If only one pod is affected, storage type is the first thing to check before assuming the data is gone.

What should I back up before migrating Pods to Nexter Fields?

A full site backup with the database included matters here because an import can overwrite an existing field group. That makes this a data-safety step, not a nice-to-have. The source plugin also needs to stay installed and active with its field groups present so the importer can read them during the migration.

Does Nexter Fields import all Pods data types?

No. The importer reads the Pods API for pods and fields, maps each type across, and copies stored values, but it only reads values stored in post meta. Pods data kept in its own tables is outside that scope. In practice, that means some setups migrate cleanly while others need manual review after import.

How do I verify a Pods migration before switching over?

Compare several posts against Pods before changing anything else. That catches mismatches early, especially when a site mixes different storage types or has fields with descriptions that won’t carry over. The page also points to After migrating: verify your data for a structured check after the import.

Is it safe to keep Pods installed after moving to Nexter Fields?

Pods is left in place and is not modified, so the migration does not remove or rewrite it. That makes rollback and comparison easier because you can still inspect the original setup while testing the imported fields. The page’s Migration overview fits well if you want the broader migration flow around this importer.

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