Hi Nikhil,
I glanced at Magic Fields’s source code and it seems to me that the plugin is using custom SQL table to store meta values(rather than the WordPress’ standard wp_postmeta table). This is unfortunate for you because you can’t easily switch to different plugin – you have several options:
* Add CarbonFields without removing MagicFields, define your custom fields in the new plugin, and manually copy-paste meta values in the administration; then, remove magic fields
* Install and setup CarbonFields, and create a script to migrate the data for you from MagicFields to standard post meta
Whichever option you choose, you should also go through your front-end theme code and switch the rendering code from magic fields to get_post_meta calls.
If I were you, I’d probably just add CarbonFields(without removing MagicFields) to the project and use that for new custom fields that are needed — I wouldn’t bother changing the old custom fields if they work fine. Both plugins should work just fine together.
If you need to add repeaters to existing custom fields that are defined in MagicFields, you could change just those fields instead of all fields in the project. This isn’t ideal, but it might be the best option if you’re constrained by time.
