How to Move ThemeRouter Settings from Staging to Production

ThemeRouter configuration export and import can move a reviewed routing setup from one WordPress environment to another. Treat the file as configuration, not as a complete site migration: the destination still needs the relevant themes, content, URLs, menus, plugins, and environment-specific dependencies.

What configuration transfer is for

A team can build and review route assignments in staging, export the ThemeRouter configuration, and import it into another environment. This reduces manual re-entry and gives the team a consistent starting point for production review.

Importing settings does not prove that a route is ready to enable. Production can differ in content IDs, installed themes, cache layers, integrations, permissions, and traffic behavior.

Prepare both environments

1. Update ThemeRouter to a compatible release in both environments.
2. Install the destination themes without activating them site-wide.
3. Confirm relevant content types, taxonomies, pages, and integrations exist in the destination.
4. Record the current production routing configuration and fallback behavior.
5. Schedule a review window and identify who can enable or pause routes.

Export the reviewed staging configuration

Use the ThemeRouter Tools area to export settings after the staging route map has completed its review. Name and store the artifact so the team can identify its source environment and review state.

Keep the file inside the project’s approved access controls. Configuration artifacts should follow the same change-management process as other production settings.

Import without assuming readiness

1. Import the configuration into the destination environment.
2. Review configuration health and resolve references to unavailable themes.
3. Compare imported assignments with the approved route register.
4. Keep routes paused or otherwise controlled until destination validation is complete.
5. Clear relevant caches after the configuration is accepted.

Validate on the destination

• The expected destination theme is installed and available.
• Representative URLs resolve to the intended assignment.
• Unmatched requests continue through the active-theme fallback.
• Navigation, forms, authentication, commerce, and plugin integrations work.
• Canonical URLs, metadata, schema, analytics, consent, accessibility, and performance are reviewed.
• Pausing the assignment returns the route to the expected fallback.

Keep an operational record

Record which configuration was imported, who reviewed it, which routes were enabled, and what evidence supported the decision. If the production result differs from staging, update the route register and resolve the dependency instead of assuming the import failed.