iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can’t convert a manual-mode AI Builder site into WordPress or another CMS in place. Hostinger’s documented process is to save what you need, delete the existing site, and create a new site on the destination platform. WordPress has a limited content-export route; for other platforms, you must copy and rebuild content manually. Deleting the old site is permanent, so do not proceed until you have secured everything you need.
Choose the right migration route
| Route | What transfers | What you must rebuild or handle separately |
|---|---|---|
| WordPress | Supported pages, text, images, and other files can be exported using Hostinger’s WordPress export process. | Styles, layout, store data, integrations, forms, collected submissions, and SEO settings are excluded. Configure the destination WordPress site before exporting. Hostinger’s WordPress migration guide lists the requirements and steps. |
| Another CMS | There is no documented automated transfer for this route; you can manually copy text and download media and files. | Recreate pages, formatting, and layout on the new platform. Hostinger’s described process does not transfer ecommerce store data, including products. See Hostinger’s manual migration guide. |
Both routes require replacing the Builder site rather than changing its CMS in place. Hostinger’s switch instructions say to delete the existing site, then create a new one using WordPress or another platform. Deletion also releases the domain for use with the replacement site. Read Hostinger’s site-switch instructions.
Before deleting the AI Builder site
- Back up email. Hostinger recommends backing up email before changing the website solution.
- Save your content and files. For a manual move, collect page text, images, Media Library files, and documents such as PDFs. Organize them by page or section.
- Record what will need rebuilding. Note your design, page structure, forms, integrations, SEO settings, and any store content. These are not included in the WordPress content export; Hostinger’s manual transfer instructions also exclude ecommerce store data, including products.
- Set up the destination first if moving to WordPress. Hostinger’s guide requires an existing WordPress site running version 6.5 or higher and a propagated domain.
- Plan the domain change. The existing domain can be used for the replacement after it is released by deleting the Builder site. Confirm your saved content and destination setup are ready before deletion.
Hostinger warns: “A deleted website cannot be restored; all its content is lost permanently.” Its switch guide describes deletion as part of the process, so treat this as an irreversible step.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesMove the site content to WordPress
Hostinger’s export transfers supported content, not a full working copy of the Builder site. Its support guide specifies the following setup and export flow. Interface labels may change; consult the live guide if a setting has moved.
#1 Best Overall
- Prepare WordPress. Set up the destination WordPress site, confirm it runs WordPress 6.5 or higher, and wait for the domain to propagate.
- Configure WordPress for the export. Set permalinks to “Post name.” In Hostinger Tools, configure application passwords, then deactivate plugins before starting the export, as directed by Hostinger’s guide.
- Start the export in AI Builder. In the Builder editor, open the sidebar settings menu, select “Export content to WordPress,” enter the destination domain, and start the export.
- Approve the connection. Approve the connection request 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 migration for security.
If the export fails because application passwords are disabled, Hostinger’s guide says to enable them in Hostinger Tools and restart the export.
What the WordPress export does not include
- Website styles and layout
- Online store data
- Integrations
- Forms and collected submissions
- SEO settings
Recreate these in WordPress or configure equivalent plugins and services on the destination. Check each imported page and media file before publishing; an export of supported content does not reproduce the original design or functionality.
Move content to another CMS manually
Hostinger’s documented route for a platform other than WordPress is to collect the content yourself and rebuild the site on the destination. The exact editor and import features vary by CMS, and Hostinger does not establish an equivalent automated importer for other platforms.
- Collect content from each page. Copy headings and text into a safe document. Download images and media, including files from the Media Library, and save documents such as PDFs.
- Organize assets. Group the saved text and files by page or section so you can match them to the new site.
- Recreate the site on the destination. Create equivalent pages or sections, paste and format the text, upload the saved media, and rebuild layout elements.
- Review before publishing. Check links, images, formatting, and page content on the new site.
- Delete the Builder site only when ready. After deletion releases the domain, use it when setting up or connecting the replacement site.
This manual procedure does not transfer Hostinger Ecommerce store data, including products. Plan a separate store-data migration if you need to retain it; the cited procedure does not provide one.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Delete the old site and use its domain
Once you have secured your content and prepared the destination, follow Hostinger’s current site-switch instructions to delete the Builder website, then add a new website and choose the destination platform. The domain released by deletion can be used for the new site. Because deletion cannot be undone, do not use it as a troubleshooting step or as a substitute for exporting and saving your work.
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.
