Migrate Away From Toolset

Replace WordPress Toolset while preserving the custom post types, fields, relationships, Views, templates and dynamic functionality your site depends on.

Start with an automatic Toolset migration analysis

Before changing anything, WP Recode scans the existing site and reconstructs its Toolset implementation. You can see what your site actually depends on before deciding how to migrate it.

The analysis identifies structures such as:

Custom post types, taxonomies, fields and field groups.

Connections between posts and other content structures, including relationship configuration and existing data.

Views, Content Templates, dynamic output and other Toolset functionality used to display your data.

Toolset references in content and other areas that may need to be replaced before Toolset can safely be removed.

Know before you migrate

The analysis determines what can be migrated automatically, what requires review and what may require manual work.
You see the migration scope before committing to the migration.

1

Scan

Download and install the lightweight WP Recode Scanner on your WordPress site.

2

Analyze

Upload the scan to WP Recode. We analyze your Toolset setup and determine what can be migrated.

3

Choose

See what was found, review any limitations and choose your migration target.

4

Recode

Start the migration. WP Recode handles the conversion, mapping and verification automatically.

What about Toolset Views and Content Templates?

“This is one of the difficult parts of leaving Toolset”

Migrating custom fields alone does not remove a site’s Toolset dependency if the frontend still relies on Toolset Views, Content Templates, shortcodes or dynamic output.

WP Recode analyzes these presentation dependencies as part of the migration.

Where an automatic replacement is supported, it can be included in the migration plan.

Where the original implementation cannot be safely translated automatically, WP Recode identifies it for review rather than silently producing an incomplete migration.

Built for existing Toolset sites

WP Recode is designed specifically to change the technology behind an existing WordPress site while preserving its data and functionality.

Your site stays where it is. Your site’s data stays as it is. Toolset is what leaves.

Ready to move away from Toolset?

Start with an analysis of your existing site.

See what depends on Toolset, what can be migrated and what your site could look like without it.

1

Toolset → Native WordPress

For sites that do not need another field-management framework, WP Recode migrates your supported Toolset functionality to a native WordPress implementation.

Instead of replacing Toolset with another equivalent dependency, WP Recode creates a lightweight site-specific runtime using WordPress APIs. Your existing data remains in WordPress wherever possible.

After a successful migration and verification: Toolset can be removed.

The resulting site does not require an ongoing WP Recode subscription or connection to WP Recode to continue working.
No recurring field-framework fees.

2

Toolset → Meta Box – Coming soon

Prefer a visual interface for managing custom post types, fields and relationships? Meta Box will be available as an alternative migration target using the same WP Recode analysis.

The same Toolset analysis can be used to reconstruct the site’s structures for Meta Box rather than the native WordPress target.

Have a Toolset Site You Need to Migrate?

Not sure whether your site can be migrated automatically? Tell us briefly how your Toolset site is built or what you would like to migrate to.

You can also use this form for questions, unusual Toolset setups, or migration targets you would like WP Recode to support.