Open Settings → Data Sources, give your integration a name, and choose what to capture: the plugin’s options and settings, its custom post types, its taxonomies, and even its own database tables. WPChangeSync writes it all into the same Git-friendly JSON it uses for everything else. Reviewable, versionable, and ready to move.
Capture the plugin’s option records exactly as stored: settings pages, config, and feature toggles.
Bring custom post types, their entries and metadata, and the taxonomies and terms that organise them.
For plugins that keep data in their own tables, capture those rows directly. No exporter required.
Go to Settings → Data Sources and start a new source.
Give the integration a clear name. It’ll appear in your Library.
Select the plugin’s options, post types, taxonomies, and tables that should travel with your site.
WPChangeSync groups everything into one tidy entry in the Library.
Run it in workflows, batches, and dry-runs alongside your native integrations.
Most migration and sync tools only move what they were built to recognise, so the one plugin your build depends on is the one that breaks. WPChangeSync ships with a deep set of native integrations and lets you add the rest yourself. The plugin doesn’t need to know WPChangeSync exists for its data to come along.
Add a source the day you adopt a plugin. No roadmap request, no waiting.
Custom sources run in workflows and batch jobs exactly like built-in ones.
Package a source as a developer integration and reuse it across projects.
Built a source for your own plugin? Export it as a developer integration and bake first-class WPChangeSync support right into your product, so every site that runs it can sync your data out of the box. WPChangeSync is self-hosted, so there’s no account to manage and no service to depend on: it’s a standard you implement once.
Turn a working data source into a shippable integration manifest.
Hook into WPChangeSync from your own plugin for deeper, native support.
A start-to-finish walkthrough of building a custom data source.
Open guide →What a custom source is, the part types, and exporting for developers.
Read docs →Ship native WPChangeSync support from inside your own plugin.
View guide →