What needs to move
Check leaving Hostinger by treating the move as a workload export: site files, databases, mail, DNS, scheduled tasks, certificates, and application-specific settings all need an owner.
Migrate from Hostinger
Plan a Hostinger-to-DotMoose move across files, databases, email, DNS, scheduled work, certificates and provider-specific settings that may need to be recreated.
Hosting options
Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →02Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
Check leaving Hostinger by treating the move as a workload export: site files, databases, mail, DNS, scheduled tasks, certificates, and application-specific settings all need an owner.
Copy the site or application to the new host and test it privately. Check logins, forms, database writes, scheduled jobs, email and any external integrations.
Choose when to stop or synchronize new writes. Include orders, uploads and mail that arrived after the first copy. Avoid letting both systems accept independent changes.
Save the old DNS and routing settings. Switch traffic after the final tests, monitor the result and keep the old service until the agreed rollback period has passed.
Field guide
Hostinger accounts run on hPanel, a custom control panel, so exports follow its own menus. Download the website files from its file manager or FTP, export each database as SQL, and save the list of email accounts, forwarders and scheduled tasks shown in the panel. Nothing in that export assumes the destination runs the same panel.
Panel specific settings are what get lost. Cron schedules, PHP settings, redirect rules and access protection live in hPanel screens that no file download captures, so each one needs a note and a manual rebuild. Walk the panel menu by menu during the inventory, then test redirects, scheduled tasks and protected folders on the destination copy.
Screenshot or note every hPanel settings screen for the site. Settings screens are the only record of cron, PHP and redirect configuration.
Database names and users rarely survive a panel change unchanged. Update the site configuration file with the new values during the restore.
Export the address and forwarder list from hPanel mail screens. Recreate the same addresses at the destination before moving stored messages.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.