Dependency-aware export
WPChangeSync includes support for template dependencies, deep export, related data, media remapping, and ID remapping. This is important when a template depends on fields, media, menus, classes, variables, or related content.
Deep Export & Dependencies
Export related data and remap IDs so migrated structures keep working.
Related data concerns
- Media and attachment references need remapping.
- Post, term, menu, and field IDs may differ by site.
- Builder JSON can contain nested references.
- CSS framework tokens and global classes may need to move together.
Practical use
Use selective exports for small changes, but include related integrations when moving reusable sections, builder templates, or complete design-system changes. Review generated JSON before committing a deep export.
Think in bundles
A production-ready section may need template JSON, global classes, variables, custom CSS, fields, media, and pages. Treat those as one release unit.
Reference checklist
Deep exports should move related templates, fields, media, menus, classes, variables, and custom code as one reviewed release unit.