How to Export and Import Schema Pro Data

Schema Pro does not include a built-in import/export tool, but your schema configurations are not locked to a single site. Using either WordPress’s native export feature or a third-party plugin, you can migrate all your Schema Pro setups between sites, including field mappings and targeting rules. This guide covers both options and explains what each one can and cannot transfer.

Does Schema Pro Have a Built-in Import/Export Feature?

No. As of the current version, Schema Pro does not have a dedicated import/export UI. This is a standing feature request from multiple customers, and a native solution may be added in a future update.

In the meantime, two reliable workarounds are available depending on how much control you need over the process.

Option 1: Export Schema Pro Data Using WordPress XML Export (Free, Built-in)

Schema Pro stores each schema configuration as a custom post type (CPT) called aiosrs-schema, registered with can_export: true. This means WordPress’s native export tool recognises it automatically, no plugin or workaround required.

How to Export Your Schema Configurations

• In your WordPress admin, go to Tools → Export.
• Select Schema from the content type list (or choose All content to export everything at once).
• Click Download Export File to save the .xml file to your computer.

How to Import Schema Configurations to Another Site

1. On the destination site, go to Tools → Import.
2. Select WordPress and install the importer if prompted.
3. Upload the .xml file you exported.
4. All schema configurations will be recreated, including field mappings and target page rules.

Note: This method exports raw CPT data in XML format. It works reliably for site migrations but does not produce a human-readable or editable file.

Option 2: Export Schema Pro Data Using WP All Export / WP All Import (Third-Party)

For greater flexibility, such as exporting to CSV or JSON, filtering specific schemas, or remapping fields during import, the WP All Export and WP All Import plugins support the aiosrs-schema post type with full post meta.

This approach is particularly useful when you need to review or edit schema data outside of WordPress, or when importing into a site with a different content structure that requires field remapping.

What Cannot Be Exported Using These Methods

Both methods above cover per-page and per-post-type schema configurations stored as CPT entries. However, Schema Pro’s global settings, such as Organisation schema, Breadcrumb settings, and other site-wide configurations, are stored in WordPress options under wp-schema-pro-general-settings, not as CPT posts.

To migrate global settings, you have two options:

• Copy the option values manually via the database (e.g. using phpMyAdmin).
• Use a database migration plugin such as WP Migrate DB to transfer the relevant options to the destination site.

Summary: Which Method Should You Use?

Use the WordPress XML export if you want a quick, free solution for migrating schema configurations between sites. Use WP All Export / WP All Import if you need more control over the exported data, want a readable format, or need to selectively export specific schemas. For global settings, a database migration tool is currently the only option.

Frequently Asked Questions

Can I migrate all Schema Pro settings to a new site?

You can migrate all per-page schema configurations using WordPress XML export or WP All Export. Global settings stored in WordPress options require a separate database-level migration using a tool like WP Migrate DB.

Does the WordPress XML export include schema field mappings and targeting rules?

Yes. Because schema configurations are stored as CPT posts with post meta, the WordPress XML export captures the full configuration including field mappings and the pages or post types each schema targets.

Can I use WP All Export to export global schema settings?

No. WP All Export works with post types, and global schema settings are stored as WordPress options, not posts. To export these, you need a database-level tool such as WP Migrate DB or manual database access.