WordPress migration: what carries over
Review supported content and redirects before moving to ZeroHost CMS. WordPress themes, plugins and commerce state are not portable promises.
By SAGOZEN Labs · Reviewed
Start with a private source audit
A migration starts with reviewing the WordPress source, not replacing the live website. ZeroHost retains a private audit, identifies supported content and reports unsupported content. Protected content remains audit-only; it is not automatically copied onto a public site.
Review content and redirect mappings
Import reviewed supported content into the target site's maintained theme and CMS controls. Review redirect mappings alongside the imported content. Do not assume every source URL, arbitrary HTML behavior or layout survives unchanged. Keep the original site available until you have checked the target.
Leave unsupported behavior out of scope
Existing WordPress themes, PHP plugins, comments and commerce state are not promised portable. ZeroHost sales support is a catalog with validated external links, not an ecommerce engine. A store with orders, customer accounts or plugin-dependent behavior needs a separate migration assessment.
Approve the draft before publication
Check imported text, contact destinations, appearance and redirects in the private draft. AI proposals require human review and never publish automatically. Publication is a separate authorized action; custom-domain ownership and HTTPS must be checked separately. Migration and structured data do not guarantee rankings or citations.