What can replace Toolset?

Toolset combines several different WordPress features in one ecosystem: custom post types, custom fields, taxonomies, relationships, queries, templates, forms and dynamic content.
That means there isn’t one universal Toolset replacement.


The right Toolset alternative depends on how your site uses Toolset and what you want to achieve by replacing it. Some sites can move much closer to native WordPress. Others benefit from a dedicated custom-content framework such as Meta Box, ACF, Pods or JetEngine.

Compare Toolset alternatives

The comparison below looks at how different approaches can replace the main parts of a Toolset implementation — and where additional tools or custom development may still be needed. The alternatives listed here are not necessarily available as automated WP Recode migration targets. WP Recode’s first migration target is Native WordPress, with additional targets planned for the future.

CapabilityNative WordPressMeta BoxACFPods
Custom post types✓✓✓✓✓✓✓✓
Custom taxonomies✓✓✓✓✓✓✓✓
Custom fields✓✓✓✓✓✓✓
RelationshipsCustom development✓✓*✓✓✓
Front-end formsCustom development✓*✓*✓✓
Queries / Views replacementCustom / blocks✓✓*Custom / blocks✓
TemplatesBlock theme / custom✓*Builders / custom✓
Dynamic contentNative / custom✓✓✓✓✓
Plugin dependency after migrationNone / minimalMeta BoxACFPods

✓ Supported: The capability is available, but may require configuration, custom implementation or additional components.
✓✓ Strong Toolset replacement: A strong, relatively direct replacement for the corresponding Toolset capability.
* Additional requirement: The capability requires or may depend on an additional component, extension or paid version.

  • Meta Box relationships require MB Relationships.
  • Views and some front-end functionality depend on Meta Box extensions.
  • ACF front-end editing typically requires ACF PRO and/or additional implementation.

Native WordPress – first WP Recode support, coming soon

Best for reducing dependencies
  • No replacement framework required = No recurring fees
  • Uses WordPress’s own data model
  • Long-term portability
  • Less plugin lock-in
  • Not every Toolset feature has a native equivalent
  • Advanced relationships and presentation logic may require custom implementation
  • Less convenient UI for managing complex structures

Best for: sites where Toolset is primarily being used for content structures and fields.

Meta Box – second WP Recode support, coming soon

Best all-round Toolset replacement
  • Strong custom field support
  • Post types and taxonomies
  • Relationships
  • Views and dynamic functionality
  • Developer-friendly
  • Conceptually relatively close to Toolset
  • Replaces one framework dependency with another
  • Some functionality requires paid extensions
  • Toolset Views and Templates don’t have direct one-to-one equivalents

Best for: complex Toolset sites that still need a comprehensive custom-content framework.

Advanced Custom Fields (ACF)

Best for fields and broad ecosystem compatibility
  • Extremely widely supported
  • Excellent field management
  • Large ecosystem
  • Works with many themes and builders
  • Familiar to WordPress developers
  • Not a complete Toolset replacement by itself
  • Relationships/querying/presentation may require additional implementation
  • More complex Toolset sites often need ACF + other tools/custom code

Best for: sites where Toolset is mainly used for fields and structured content.

Pods

Best open-source all-in-one alternative
  • Custom content types
  • Fields
  • Relationships
  • Free and open source
  • Broad feature set
  • Smaller ecosystem than ACF
  • Less direct equivalent for some Toolset presentation functionality
  • Migration path may require more custom handling

Best for: sites looking for an open-source structured-content framework.

Ready to Leave Toolset?

Find out what your current Toolset site uses and whether it can be moved to Native WordPress with WP Recode.

Get started See how WP Recode works