Custom Field Migrator & Cleaner

Custom field and post type migrator and cleaner

Custom Field Migrator & Cleaner plugin

  • Migrate content from one custom field to another custom field.
  • Migrate content from one custom field type to another custom field type, like text to textarea or text to WYSIWYG or rich-text.
  • Migrate content from a custom fields plugin, like ACF or Metabox, to custom fields created with any other plugin, like ACPT, Modern fields, etc.
  • Temporary compatibility mode to ensure your templates that ask for the values in the old fields are getting them from the new fields.
  • Change the visible name (the label) of any custom field.
  • Tracking and removing old or unused custom fields, including _subfields.
  • Use our Custom Post assist to migrate your custom posts and taxonomies.
  • Full documentation page and a guide in the plugin.
CLASSIC
FSE

Works with

ACF

SCF

ACPT

MetaBox

JetEngine

Toolset

Modern fields

Without our plugin

$ lots of time and error

Conclusion: bad choice

  • Manualy moving custom fields
  • Copy and paste from field to field
  • Not able to convert values from one type to another
  • No automatic conversion of ID’s and url’s
  • No knowledge about required syntax
  • Doing a lot of research
  • You can make more mistakes
  • Huge time investment
No real solution

Free version

$ 0

Conclusion: good choice

  • Migrate between all custom field plugins
  • Migrate from all fieldtypes to all fieldtypes
  • Automatic conversion of ID’s and url’s
  • Syntax assistence
  • Limited to one mapping row
  • No cleaning of old costum fields
  • No renaming of custom field labels
  • Limited time saver
14-Days-Money-Back

Pro version

$ 49 one-time

Conclusion: best choice

  • Migrate between all custom field plugins
  • Migrate from all fieldtypes to all fieldtypes
  • Automatic conversion of ID’s and url’s
  • Syntax assistence
  • Unlimited mapping rows
  • Cleaning of old costum fields
  • Renaming of custom field labels
  • Saving lots of time
  • Activation on 3 websites
14-Days-Money-Back
LTD license $ 49,-

Migrate content from one custom field to another custom field

Custom Field Migrator & Cleaner: the custom fields mapping user interface

Custom field mapping

  • All custom fields are automatically added to the select list, and you can refresh the list.
  • Select a custom field (source).
  • View an example value of the source custom field.
  • Select a new custom field (target).
  • Select the field type.
  • Some fields provide more options, like the image field, date, WYSIWYG field, etc.
  • Tick the temporary compatibility layer, or not.
  • Tick the fields you like to convert, or use ‘all’.
  • Save settings and Convert.
  • If you don’t like the outcome, change the settings and rerun only that field migration rule.
  • The values in the source fields are never deleted.

Temporary compatibility

  • If you ticked the ‘Enable Temporary Compatibility’ all the converted fields are automatically placed in the list of temporary compatibility rules.
  • Review the list by clicking on the Temporary compatibility tab.
  • You can add and remove Temporary Compatibility rules.
  • Now you can change your templates, and when done disable Temporary compatibility.
  • Note: while migrating custom field values, the Temporary compatibility is automatically disabled en enabled again, to guarantee correct migration.
Temporary compatibility layer for the custom fields
Custom Field Migrator & Cleaner: the interface to clean old meta-keys

Clean old Meta keys

When you eliminate the unused custom fields from your plugin or decide to uninstall the entire custom field plugin, the actual unused fields remain in the database, along with all their saved values. These residual data can occupy valuable space, slow down your website’s performance, and may even hold sensitive information.

  • Clean old Meta keys, especially to track and remove old and unused custom fields.
  • Removes the main field and, if you like, all _subfields.
  • Don’t forget to make a backup before you do this. We never experienced it, but it’s always possible you deleted something you shouldn’t have.

Change the label of a field

Did you know that when you update the label of a custom field in your custom field plugin, the label in WordPress remains unchanged? This means that clients or users will still see the old label while editing posts.

With our plugin, it’s easy to manage this. You simply select the field, see the current label, type in the new label you want, and click on “Change Label.” That’s it.

Feel free to update the label in your custom field plugin as needed; it won’t affect anything as long as you keep the meta key the same.

Change the key label of a custom field
Posttype assist for successful and easy custom post type migration

Posttype assist for your custom post(s)

Are you in the process of changing your custom field or custom post plugins and unsure how to retain your custom post type? We’ve got just the solution for you: Posttype Assist.

Even when you switch plugins, most information related to your custom post types is preserved in the WordPress database. All you need to do is inform the new plugin about your existing custom post type by recreating it in the same way as before and ensuring you also set up the same taxonomies.

To do this effectively, you’ll need the exact slugs and label names for both the custom post type and the taxonomies.

Simply choose the post type you want to migrate, and our Custom Field Migrator & Cleaner plugin will guide you with all the essential information and steps required for a smooth migration. You can either copy this information or download it as a text file. It’s that simple!

FAQ’s

Absolutely, you can. Some fields, such as text or textarea, don’t offer additional output types since they simply contain plain text. In contrast, an image field provides options like ID, Array, and URL. A WYSIWYG field includes functionalities to copy HTML as stored, remove embedded media, or extract embedded media to specified image IDs. For date outputs, there are two option fields available: input and output, which include formats like auto-detect, Unix timestamp, ymd, y-m-d, and ISO 8601.

When referring to converting a text field into a textarea, rich-text, or WYSIWYG field, or an image field to a gallery field, the answer is yes. It’s crucial to recognize that the results may not always align with your expectations. For instance, when migrating content from a WYSIWYG field to a text field, you will see the entire HTML code rather than just plain text. But, we added an output filter, that removes the HTML and keeps the text and line-breaks. Additionally, transitioning from an image field to a text field will yield an image ID or a URL instead of the actual image itself.

When you need to convert an image ID into an image URL, our plugin automatically fetches the original image’s URL and utilizes it for the new custom image field. There’s no special setup required; the process happens seamlessly.

No. Firstly, our plugin is designed to seamlessly migrate data from any custom fields plugin to another. Secondly, many custom fields require specific settings, such as an image ID, array, or URL, which necessitate human input for accurate configuration.

No need to be concerned. The plugin does not change your original custom fields or their values during the migration; everything remains intact. That’s why we divided the entire process into distinct tabs and procedures.

  1. Migrate values to the new custom fields.
  2. Activate or adjust temporary compatibility for existing templates and lay-outs.
  3. Clean (remove) old and other unused meta keys, still present in the database.
  4. Change key labels within the database itself.
  5. Posttype assist tracks your custom post type and taxonomies slug and labels, and provides you with step by step instructions for the migration.
All is reversible (except clean old keys)

You can easily revert the process. Start by removing all temporary compatibility rules and deleting any custom fields created in the custom field plugin if they’re no longer needed. Next, clean the database to restore everything to its original state.

Unless you are using the Temporary Compatibility feature, there is no further action required. If you have successfully completed the migration, cleaned up the old database fields, and adjusted your templates, it is perfectly fine to disable the plugin. It serves as a handy tool during the transition, but once your work is done, it is no longer necessary.

The Custom Field Migrator & Cleaner plugin is an outstanding plugin

It’s easy to use, and the migration and Temporary Compatibility are both totally non-destructive. Cleaning old Meta keys is not, beware!

Plugin license

  • The Custom Field Migrator & Cleaner plugin is sold as a one-time payment.
  • License for 3 sites (1 live, 1 staging and 1 to play with).
  • Always deactivate a license on an unused website; otherwise, your key slot remains occupied.
  • Prices excluding sales-tax/vat/iva
Lfetime license $ 49,-
See documentation