GICT knowledge base
Move Wix Content to WordPress: Rebuild and Verification Guide
Published
A Wix site cannot be treated as a cPanel backup that you restore into WordPress. Moving to self-hosted WordPress at InterServer requires a content-transfer plan and rebuilding Wix-specific design and application behavior.
Builder conversions are self-managed and are not part of InterServer’s complimentary matching-panel web hosting migrations. VPS and dedicated-server migrations are also not offered. Plan the rebuild before cancelling the source or changing DNS.
Identify what needs to move
Inventory pages, posts, media, menus, forms, member features, store data and important URLs. Use authorized source content and original media files. Wix’s external-hosting guidance explains its platform boundary; do not assume a downloaded page or content export includes the running Wix application.
Choose a supported content route
For a small site, rebuild pages and posts in WordPress and upload the necessary media. If a source feature supplies an RSS feed or other export, inspect its actual content and test an importer that explicitly supports that format. A feed can omit older entries or non-blog data and may refer to images still hosted at Wix.
The old universal domain.com/rss example is withdrawn. Find a feed through the source site’s documented controls rather than guessing a URL and calling it a complete export.
WordPress.com currently documents its own Wix importer. That is a separate hosted service, not a built-in Wix importer in every self-hosted WordPress installation. If using an intermediary or third-party tool, assess privacy, cost, export compatibility and omitted features before committing to it.
Rebuild features, not just text
Select supported WordPress themes/plugins for the intended functionality. Test forms, accounts, navigation and commerce separately. Product/order/member exports, when available, have their own scope; importing posts does not recreate those systems or transfer every password.
Preserve links and verify the destination
Map actual old URLs to the new pages. Choosing Post name permalinks alone does not provide redirects. Verify local media, content coverage and representative old links before changing DNS, and retain the source and rollback records until accepted.
Domain registration and external email are separate from the website rebuild. Preserve mail-related DNS when mail is not moving; do not replace the entire zone merely to point the website at InterServer.
Additional reference: WordPress.com Wix importer scope. Reviewed October 14, 2026. No Wix export, intermediary service or customer-site import was tested.
Related guides
Check MariaDB Versions and Compatibility on Shared Hosting
Check your actual MariaDB/MySQL server version, maintenance coverage and application requirements before requesting a shared-hosting upgrade or move.
MigrationMigrate WordPress with Migrate Guru: Scope and Safety Checks
Use Migrate Guru for a scoped WordPress copy. Review third-party processing, protect the destination and verify the application before changing DNS.
MigrationcPanel to DirectAdmin: Conversion, Restore and Verification
Convert a supported cPanel account archive to DirectAdmin with private delivery, ownership mapping and application/mail checks before DNS cutover.
MigrationcPanel to CWP: Private Backup Import and Recovery Checks
Plan a self-managed cPanel-to-CWP import. Transfer backups privately, check account conflicts and verify websites, mail and DNS before cutover.
