Moving a WordPress Website with ACF and Custom Post Types to Brightspot CMS

Migrating a website from WordPress to Brightspot CMS can seem daunting, particularly when the WordPress installation relies heavily on Advanced Custom Fields and Custom Post Types.

Both ACF amd CPT give WordPress sites their flexibility, but they also mean there is more to think about when moving to a new platform. With some careful planning, however, the process can be managed smoothly.

Understand the Data Structure

The first task is to take stock of the current WordPress site. Identify all custom post types and their associated ACF fields, noting how they relate to one another and to any taxonomies. At the same time, review how Brightspot structures content. Brightspot is built on a flexible model where custom classes define content types, so every field and relationship needs to be mapped over thoughtfully.

Export the Data

WordPress provides several options for extracting data. You can make use of the REST API, WP-CLI, or dedicated plugins such as WP All Export to create JSON or XML files. The data stored by ACF lives in the wp_postmeta table, so it is important to include this in any export. If you are using ACF Pro, its JSON export of field groups can also be useful. Don’t forget media assets, which you will need to collect from the /wp-content/uploads directory.

Map WordPress to Brightspot

With the content in hand, the next stage is to map it to Brightspot’s schema. Each custom post type in WordPress should be mirrored by a corresponding Brightspot content type class, and each ACF field translated to the appropriate Brightspot field. Relationships, whether one-to-many or many-to-many, must also be replicated to preserve the integrity of the data.

Import into Brightspot

Unlike WordPress, Brightspot does not provide a ready-made importer for this purpose. Instead, you will need to write a custom import routine, typically in Java, using Brightspot’s APIs or its DataSync framework. The exported WordPress data should be transformed into a format Brightspot expects, then ingested into the system. Once the import is complete, it is worth verifying the results carefully to ensure nothing has been lost in translation.

Recreate Functionality

The data is only half the story. The site’s functionality must also be carried over. ACF fields become custom Brightspot fields, while WordPress templates are replaced with Brightspot’s templating engine, usually based on Freemarker or React. Custom taxonomies need to be redefined as Brightspot taxonomies, and media files uploaded into its Digital Asset Management system.

Test, Refine, and Launch

Before going live, a staging environment is invaluable. Here you can check that data has migrated cleanly, that templates render correctly, and that editorial workflows remain intuitive. Once testing is complete and any refinements have been made, the migration can be repeated for the live site. Finally, update DNS settings to point to the new Brightspot instance.

Migrating from WordPress to Brightspot is less about pressing a button and more about translating one content model into another. By carefully analysing your existing data, exporting it cleanly, and mapping it thoughtfully into Brightspot, you can achieve a smooth transition without losing the flexibility that ACF and custom post types once provided.