Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

Migrate from SiteGround

SiteGround hosting alternative in Canada: move to DotMoose

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

Compare the services for your project.

Your requirements

What does your project need?

01

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.

02

Test 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.

03

Copy the final changes

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.

04

Switch traffic and retain rollback

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

Rebuilding SiteGround sites and their settings

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.

01

Staging copy decision

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.

02

Cache plugin reset

Platform cache plugins need removal or reconfiguration at the destination. Test the site with caching off, then enable the new setup deliberately.

03

Responsibility rebuild list

List what the old panel handled: backups, cron, TLS renewal and caching. Each item needs a named replacement at the destination.

Planning

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

SiteGround hosting alternative in Canada: move to DotMoose: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your 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.

Start my free moveSee plans and prices
See pricesFree move