Outcome
You can recover the affected WordPress data using WPChangeSync backup records, pre-import exports, or Git-tracked JSON.
Restore from Backup
Recover after a bad import, failed release, or wrong conflict choice.
Video walkthrough
▶
Video walkthrough coming soon.
The YouTube embed will appear here.Risk level
High. Recovery path. Stop further syncs and restore narrow scope first.
Before you start
- Stop additional imports or editor changes.
- Identify the workflow run/import that caused the issue.
- Find the latest safe backup/export before that run.
Steps
- Open Activity
Find the failed or bad import and note affected integrations/items. - Locate backup data
Use backup records or a pre-import JSON export. - Restore narrow scope first
Restore only the affected post/template/item when possible. - Re-run with safer conflict strategy
If re-importing, switch to prompt/skip or a smaller selected payload. - Verify and document
Record what was restored and why, then keep the backup until the release is stable.
Screenshots
wp wpchangesync statusnwp wpchangesync workflow show Create a pre-restore backup
Before reverting, capture the current broken state too. It can help diagnose what went wrong.Verify and recover
After completing this guide, verify the result in Activity and on the target site. Keep the pre-change export or backup until the release has been accepted. If anything looks wrong, stop further syncs, restore the affected item or integration from backup, and re-run with a narrower scope or safer conflict strategy.