Custom fields and post types, ACF-compatible.
Field groups stored exactly like ACF, with location rules, 22 field types including a repeater, and Custom Post Type UI-style screens for post types and taxonomies. Templates read values with getField() or the [acf field] shortcode.
Bundled with Presscomet · Replaces Advanced Custom Fields, ACF PRO, Custom Post Type UI, Meta Box, Pods
What it does, and what it doesn’t.
You get
- ACF field groups and values used as they are
- Repeater field included
- Post types and taxonomies registered from the admin
- ACF 6.1+ post types and taxonomies converted
Not included
- No Flexible Content, Gallery, Clone, Group, Link, oEmbed or Google Map fields
- No options pages and no ACF blocks
- Meta Box and Pods definitions aren’t converted
Same storage, so nothing is rewritten
ACF keeps field groups as acf-field-group posts and values in post meta under the field name. This plugin uses the same layout, so a migrated site’s fields and values work without a conversion step.
Relational values — images, files, post objects, relationships, galleries — point at post IDs that change during migration, so those are remapped automatically.
Presscomet Custom Fields compared
Feature by feature, including what isn’t there. Rows describe what the bundled plugin’s code does today.
| Feature | Advanced Custom Fields | Custom Post Type UI | Presscomet |
|---|---|---|---|
| Field groups with location rules | Included: Yes | — | Included: Post, page and user rules |
| Basic, choice, relational and date/colour fields | Included: Yes | — | Included: Yes |
| Repeater | Partly: PRO | — | Included: Included |
| Flexible Content, Gallery, Clone | Partly: PRO | — | Not included: Not included |
| Options pages | Partly: PRO | — | Not included: Not included |
| Blocks built from fields | Partly: PRO | — | Not included: Not included |
| Post types & taxonomies from the admin | Included: Yes (6.1+) | Included: Yes | Included: Yes |
- Included
- Partly, or on a paid plan
- Not included
- Not needed, with the reason
ACF and Custom Post Type UI features as publicly documented.
What moves over automatically.
Field groups, fields and values are already in ACF’s format, so the importer mostly tidies up and remaps IDs.
Imported
- ACF field groups and fields, keys and active state
acf-field-groupacf-field - Values stay in post meta under the field name; relational IDs remapped
imagefilepost_objectrelationshipgallery - Custom Post Type UI post types and taxonomies
cptui_post_typescptui_taxonomies - ACF 6.1+ post types and taxonomies
acf-post-typeacf-taxonomy
Not imported
- Meta Box definitions (they live in PHP code); values stay in post meta
- Pods definitions; values stay in post meta
- Field types without an equivalent fall back to a plain text input
- Custom Fields: 6 field groups, 2 post types, 1 taxonomies (1 converted from ACF), 84 relational values remapped.
How switching works.
- 01
Check your site
Run the free site check to see which of your plugins Presscomet replaces and what needs attention.
- 02
Run the migration
Connect your WordPress site. Content, users, media and plugin settings are imported into a new Presscomet site; your live site is only read.
- 03
Review and switch
Open Custom Fields in the admin menu: Field Groups, Add New, Post Types, Taxonomies to check the imported settings, then point your domain at the new site when you’re happy.
Where to find it: Custom Fields in the admin menu: Field Groups, Add New, Post Types, Taxonomies.
Custom Fields: questions
Do I need to rewrite my templates?
PHP templates don’t run, but the data is the same. In your theme code, read values with getField() / getFields(), or use the [acf field="name"] shortcode in content.
Is the repeater field included?
Yes. Repeaters are included, along with text, number, choice, image, file, WYSIWYG, relational, date and colour fields.
What happens to Flexible Content fields?
There is no Flexible Content editor. The stored values stay in post meta, but the field is shown as a plain text input, so a site built around Flexible Content isn’t a good fit yet.
Can I keep running Advanced Custom Fields instead?
No. Presscomet doesn’t run PHP, so WordPress plugins can’t be installed. The bundled Custom Fields plugin does the job instead, and the migration imports the settings listed above.
Does Presscomet support WooCommerce?
Not today. Presscomet is for content sites — blogs, magazines, business and documentation sites. If your site sells through WooCommerce, it isn’t a fit yet.
Related plugins and next steps
Related
- AlternativeAdvanced Custom Fields alternativeACF-format field groups and values, repeater included, plus post types and taxonomies — but no Flexible Content or options pages.
- BundledRole EditorCreate roles and toggle capabilities per role or per user, using WordPress capability names.
- BundledDuplicate PostClone or New Draft for any post type, with control over which fields, meta and taxonomies are copied.
Move your WordPress site in one go — content, users, media and plugin settings. Free and open source; your live site is only read.
Managed hosting with backupsAll 19 bundled plugins
Advanced Custom Fields, ACF, Custom Post Type UI, Meta Box, Pods are trademarks of their respective owners. Presscomet is not affiliated with or endorsed by them. Names are used only to describe compatibility and migration.