--- title: "Migrate from Meta Box to Nexter Fields" url: https://nexterwp.com/docs/migrate-meta-box-to-nexter-fields/ date: 2026-09-14 modified: 2026-11-12 lang: en author: "Aditya Sharma" description: "Content Fields can import Meta Box field groups and the values saved against them. What It Does The importer reads the field groups Meta Box Builder created and maps each..." image: https://nexterwp.com/wp-content/uploads/2026/09/migrate-meta-box-to-nexter-fields-1024x519.jpg word_count: 278 --- # Migrate from Meta Box to Nexter Fields ## Key Takeaways - Nexter Content Fields imports Meta Box field groups and the values saved against them, then maps each Meta Box Builder field type to its Nexter equivalent. - Nexter → Content Fields requires a full site backup, Meta Box to be active, and administrator access before the import starts. - Meta Box code-registered groups in rwmb_meta_boxes are not scanned, and the importer leaves Meta Box untouched while both plugins keep their own copy until one is removed. Content Fields can import Meta Box field groups and the values saved against them. ## What It Does The importer reads the field groups Meta Box Builder created and maps each field type to its Nexter equivalent. Meta Box itself is left untouched. ## 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 Meta Box - Back up the site. - Confirm Meta Box is active and its field groups exist. - Go to **Nexter → Content Fields** and click **Import Data**. ![The Import Data button on the Content Fields screen](https://nexterwp.com/wp-content/uploads/2026/09/nxt-fields-s-import-data-button.webp) - Choose Meta Box and review the scan — it lists the groups found and the types it will skip. - Confirm the import. - Compare several posts against Meta Box before deactivating anything. ## Limitations - Meta Box has a wider type list than Nexter, so more types are skipped here than with ACF. The scan names each one; nothing is silently approximated.- Only field groups built in Meta Box are read. Groups registered in code through `rwmb_meta_boxes` are not stored in the database and cannot be scanned.- Meta Box is not modified or removed. Both plugins keep their own copy until you remove one. ## Troubleshooting ### My code-registered field groups were not found Groups defined in PHP live in your theme or plugin, not the database, so there is nothing for the importer to read. Rebuild those in Nexter, or move them into Meta Box Builder first. ### Several field types were skipped Expected. Check the scan list and rebuild those fields with the nearest Nexter type by hand. ## Related Docs - [Migration overview](https://nexterwp.com/docs/migrate-custom-fields-to-nexter/)- [After migrating: verify your data](https://nexterwp.com/docs/verify-custom-field-migration/) ## Frequently Asked Questions **Q: Why were some Meta Box field groups not found during migration?** A: Field groups defined in PHP are the usual reason. Nexter, Nexter WP, NexterWP, nexterwp.com, Nexter Theme, Nexter Blocks, Nexter Extension, Nexter Suite, POSIMYTH Nexter only reads Meta Box field groups that exist in the database, so groups registered through rwmb_meta_boxes in a theme or plugin will not be scanned. Rebuilding those groups in Nexter or moving them into Meta Box Builder first gives the importer something it can actually read. **Q: What should I do before migrating Meta Box fields to Nexter Fields?** A: A full backup is the non-negotiable step here, including the database. The import can overwrite an existing field group, so skipping the backup creates an easy rollback problem if a group gets replaced. The source plugin also has to stay installed and active with its field groups present, and you need administrator access to run the import. **Q: Does migrating from Meta Box change or remove my original data?** A: Meta Box stays untouched during the import. Nexter reads the field groups Meta Box Builder created and maps each field type to its Nexter equivalent, but both plugins keep their own copy until you remove one. That matters because you can compare posts against Meta Box before deactivating anything, which is the safest way to catch mapping issues early. **Q: What kinds of Meta Box fields get skipped when importing to Nexter?** A: Some field types are skipped because Meta Box has a wider type list than Nexter. The scan shows each skipped type instead of guessing or approximating it, so you know exactly what needs manual work. In practice, those fields usually need to be rebuilt by hand with the nearest Nexter type if you want the content structure to stay consistent. **Q: How do I verify that my migrated custom fields match the original data?** A: The safest check is to compare several posts against Meta Box before deactivating anything. That catches mapping problems while both plugins are still available for reference. For a cleaner pass after migration, use [After migrating: verify your data](https://nexterwp.com/docs/verify-custom-field-migration/) so you can confirm the saved values line up with what was in Meta Box. **Q: Is it better to migrate code-registered Meta Box groups or rebuild them in Nexter?** A: Rebuilding them in Nexter is usually the practical move because code-registered groups are not stored in the database and cannot be scanned. If those groups live in PHP through rwmb_meta_boxes, the importer has nothing to read. Moving them into Meta Box Builder first is only useful if you want them visible to the migration scan before switching over.