Custom Field Suite for WordPress: Setup, Usage, and Migration Guide

Custom Field Suite is a free WordPress custom fields plugin that has been largely superseded by Advanced Custom Fields but remains in use on many existing sites. This guide covers using CFS on sites that already have it, and how to migrate if you need to move to a more actively maintained solution.

Understanding Custom Field Suite

CFS adds custom meta fields to WordPress posts, pages, and custom post types through field groups. You define which fields appear on which content, editors fill them in, and theme templates display the data. This is the same pattern as ACF — CFS just has fewer field types and less active development.

CFS is still functional on current WordPress versions (as of 2024). The main concern is not that it breaks immediately, but that future WordPress updates may introduce compatibility issues without CFS updates to address them.

Working With Existing CFS Installations

If you inherit a site using CFS:

1. Go to Field Suites in the WordPress admin to see all defined field groups
2. Note the field names — these are the keys used in theme templates with CFS()->get('field_name')
3. Check which post types each field suite is assigned to
4. Do not delete or rename field groups — this breaks template output

Prefer to have someone handle the setup? Describe what you need and get a free estimate — no obligation.

Creating a New Field Group in CFS

If you need to add fields to an existing CFS site (rather than migrating):

1. Go to Field Suites → Add New
2. Add fields: Text, Textarea, File, Date, Relationship, or Loop (repeater equivalent)
3. Configure the Placement rules — which post types and conditions show this field group
4. Save and edit a post of the target type — CFS fields appear in the meta box

Displaying CFS Fields in Templates

CFS data is retrieved with the CFS()->get() function:

<?php echo CFS()->get('field_name'); ?>

For Loop fields (repeater equivalent):

<?php foreach(CFS()->get('loop_name') as $row): ?>
  <?php echo $row['sub_field_name']; ?>
<?php endforeach; ?>

Should You Migrate to ACF?

For new projects: do not use CFS — use ACF Free or Meta Box instead. For existing sites using CFS: migration is justified when you need field types CFS does not support (gallery, color picker, Google Maps), when you need Gutenberg block integration, or when you want active plugin maintenance. If CFS is working and the site does not need new custom field features, leaving it in place is a valid decision.

Migrating from CFS to ACF

Migration process:

1. Document all existing CFS field group configurations (field names, types, placement rules)
2. Install ACF and recreate equivalent field groups with matching field names where possible
3. Test data retrieval — if ACF field names match CFS field names, get_field('field_name') returns the stored data without any database changes
4. Update template code from CFS()->get('name') to get_field('name')
5. Verify all data displays correctly across all affected post types
6. Deactivate CFS after confirming the migration works