What needs to move
Check leaving SiteGround by inventorying the actual site and service dependencies and rebuilding equivalent DNS, mail, database, application, caching, cron, TLS, and backup responsibilities at the destination.
Migrate from SiteGround
Plan a SiteGround-to-DotMoose move across the site, database, email, DNS, caching, cron, TLS and backups, with destination testing before traffic changes.
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 SiteGround by inventorying the actual site and service dependencies and rebuilding equivalent DNS, mail, database, application, caching, cron, TLS, and backup responsibilities at the destination.
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
SiteGround sites live inside its Site Tools panel, with files reachable by FTP, databases through its MySQL screens, and mailboxes inside the same account. Export files and database dumps, and write down the extras the panel manages: staging copies, caching settings, cron jobs and any parked domains or subdomains tied to the account.
The caching layer causes the confusing failures. A destination copy can look broken while a cache plugin tuned for the old platform serves stale or mismatched pages, and staging subdomains sometimes hold the newest content. Decide which copy is the real site, disable platform specific caching on the destination build, and test with caches cleared before judging the move.
Check staging and backup copies for content newer than the live site. Migrate the copy the business actually uses, not the easiest one to export.
Platform cache plugins need removal or reconfiguration at the destination. Test the site with caching off, then enable the new setup deliberately.
List what the old panel handled: backups, cron, TLS renewal and caching. Each item needs a named replacement at the destination.
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.