A business changing website suppliers needs to know what a content export actually carries. Commission an inventory across posts, media files, theme/plugin configuration and external services before retiring the old host. A successful XML import is only one part of a handover.
Primary evidence and claim boundaries
WordPress migration guidance describes WXR content exports and notes that widget configuration and blog/plugin settings are not exported by that method; imported media needs verification. Primary reference · Read 17 October 2026.
Filled acceptance example
Synthetic teaching scenario, not a client case, provider integration test or business result. Scroll the example table on narrow screens.
| Synthetic source inventory | Available delivery | Acceptance state |
|---|---|---|
| 12 posts /12 published IDs | 12 WXR entries;12 target posts | Content count reconciled; inspect bodies |
| 8 attachment files | 8 attachment references;6 target files verified | 2 files unresolved, not 8 transferred |
| Theme options /3 widgets | No settings package | Unknown, not reset-to-default approval |
| Form email service | External account integration | Separate owner/access handover needed |
Practical handover procedure
- Before export, agree required content types, attachments and functional settings. Keep authorised copies of files/database/configuration as applicable, with access controlled and restoration ownership recorded.
- Match stable source IDs and representative body content to target records. For media, verify bytes or an approved derivative contract, not merely a surviving external source URL.
- Test the authorised isolated target after disabling dependence on the old host. Keep unresolved files/settings in the handover and retain the original until the owner approves retirement.
Interpret the outcome
The sample has 12 content records,6 verified files and 2 unresolved files. These are separate denominators, not a single “100% migrated” score. Restoring from a file collection is also a different task from importing content, so the supplier should demonstrate the agreed recovery path.
Acceptance decision
Require complete category-specific counts, representative body/file checks and functional readback without hidden old-host dependencies. No host retirement is authorised by this worksheet.
Limits and unverified work
Synthetic inventory, not an actual WordPress migration or full backup procedure. Plugin licences, secrets, privacy and vendor-specific restoration require separate owner-controlled handling.
Download the filled bilingual acceptance record — Contains these inputs, steps, expectations and limits. This is a teaching record, not an executable integration.