Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →You can’t convert a Hostinger AI Builder site made in manual mode into WordPress or another CMS in place. Hostinger’s documented process is to prepare a replacement site, transfer the content the destination supports, and then delete the AI Builder site. WordPress has a dedicated content-export route; for another CMS, the transfer is manual. Because deletion is permanent, save what you need before removing the old site.
What changes when you switch
This is a replacement, not a conversion: the existing AI Builder site does not become a WordPress or other CMS site. Hostinger’s switch instructions call for deleting the builder-based website and setting up a new one on the destination platform. The old website cannot be restored after deletion. Hostinger’s switching guide
As an Amazon Associate I earn from qualifying purchases.
The transfer options differ by destination. WordPress has an export tool for supported content, but it does not carry over the site’s design or several kinds of functionality and data. For another platform, Hostinger describes copying and rebuilding the site manually.
Choose the transfer route
| Transfer route | What can move | What you must rebuild or leave behind | Store data |
|---|---|---|---|
| WordPress export | Regular pages, text, images, and other files supported by the export | Styles and layout, integrations, forms and collected submissions, and SEO settings are excluded | The online store is excluded |
| Another CMS, manual transfer | Text, images, and other files you save and upload yourself | Create pages and sections again, recreate the layout, and review formatting and links | Hostinger says its ecommerce store data, including products, is not included in this transfer process |
These are the routes described in Hostinger’s switch guide, its WordPress export instructions, and its manual-transfer guide. The documentation does not establish that other CMS platforms have an equivalent automated importer.
#1 Best Overall
Before you delete the AI Builder site
- Back up email first. Hostinger recommends backing up email before changing the website solution.
- Inventory what the export will not move. Save any design references, forms or submission records, integration details, SEO settings, and store information you still need. The WordPress export excludes these items and the online store.
- Save media and files. For a manual move, download images and other media from the Media Library, plus documents such as PDFs. Organize them by page or section.
- Prepare the replacement before switching the domain. For the WordPress export, Hostinger requires an already-set-up WordPress site, WordPress 6.5 or higher, and a propagated domain.
- Keep the current site until you have what you need. Hostinger states that a deleted website cannot be restored and its content is lost permanently. Switching guide
Move supported content to WordPress
Hostinger’s export tool transfers supported content, not the old site’s appearance or full functionality. Set up the destination WordPress site before starting, and follow the live WordPress export guide if its interface or requirements have changed.
- Prepare WordPress. Confirm the site is set up, runs WordPress 6.5 or higher, and uses a domain whose DNS has propagated.
- Set the required WordPress options. Set permalinks to “Post name.” In Hostinger Tools, configure application passwords as directed by the export guide. Deactivate plugins before starting the export.
- Start the export in AI Builder. In the editor, open the sidebar settings menu, choose “Export content to WordPress,” enter the destination domain, and start the export.
- Approve the connection. When prompted, approve the connection in the WordPress admin panel, then go to the WordPress site to check the imported content.
- Revoke the application password. Hostinger recommends revoking the export application password after the transfer for security.
If the export reports that application passwords are disabled, Hostinger’s guide says to enable them in Hostinger Tools and restart the export. Once content is imported, plan to recreate the design and any excluded functionality in WordPress.
Move content to another CMS manually
For a platform other than WordPress, Hostinger’s documented approach is to collect the content yourself and rebuild the site on the destination. Use its manual transfer guide as a checklist.
Recommended Free Tools
- Work through every page. Copy headings and text into a safe document. Download images and media from the Media Library, and save downloadable files such as PDFs.
- Organize the files. Group the text and media by page or section so you can match them to the new site.
- Recreate the site on the destination. Make equivalent pages or sections, paste and format the text, upload the saved media, and rebuild layout elements.
- Review before publishing. Check links, images, and formatting on the destination site.
Hostinger’s manual procedure does not include ecommerce store data, including products. Plan separately for that data rather than assuming it will transfer with page content.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Delete the old site and reuse the domain
Delete the AI Builder site only after you have saved what you need and prepared the replacement. Hostinger’s switch guide says the domain is released when the builder site is deleted; use that released domain when setting up the replacement site. Deletion is permanent, so do not treat it as a reversible step. Follow the current switching instructions for the deletion and setup sequence.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
