Migrate to an in-Kingdom cloud: a practical guide for Saudi businesses

Moving to a Saudi-resident cloud sounds like a big project. Done right, it isn't — most SMBs migrate email and a website over a weekend with no lost mail and no downtime, then consolidate domains, DNS and files at their own pace. The key is sequencing: change things in the right order, keep the old system live until the new one is verified, and cut over DNS last. This guide gives you the checklist we actually use, plus an honest note on what's guided and what's self-serve.

Start the move: Start your free 14-day trial — no credit card. Set everything up and verify it before you flip a single record.

Why migrate in-Kingdom at all

Three reasons drive most moves to Skyline Cloud:

1. Data residency / PDPL. Your email, files and customer data become Saudi-resident — a clean posture for PDPL obligations and NCA guidance, and a one-sentence answer to "where is our data?"
2. One SAR bill instead of five. Domain, email, hosting, DNS, Drive and SSL stop being five vendors in three currencies and become one prepaid wallet.
3. Local support and lower latency for users in Riyadh, Jeddah, Dammam and across the GCC.

What's guided vs. self-serve (honest scope)

• Guided migration support is available for email from Google Workspace, Microsoft 365 and GoDaddy — this is the part with the most moving pieces, and where help matters most.
• Domain transfers, DNS, web hosting setup and Skyline Drive are straightforward self-serve in the console (with support on hand).
• We do not offer a free, done-for-you migration of everything — including arbitrary AWS/Azure infrastructure. Be wary of any provider that promises that for free; real infrastructure migration is project work. We're upfront so you can plan.

The migration checklist

Phase 0 — Prepare (before you change anything)

• Create your Skyline Cloud account (free 14-day trial).
• Fund the wallet in SAR for the services you'll keep.
• Inventory what you're moving: domains, mailboxes (and rough mailbox sizes), websites, DNS zones, shared files.
• Note current TTLs on your DNS records — lower them to 300s a day or two before cutover so changes propagate fast.

Phase 1 — Email (the careful part)

• Add your domain in the console and create the mailboxes you need (assign-first: create the right addresses, not just the signup one).
• Use guided migration to copy mail from Microsoft 365 / Google Workspace (OAuth connect) or GoDaddy into the new mailboxes. The old mailboxes stay live the whole time.
• Set up SPF, DKIM and DMARC for your domain (managed in the same console as your DNS).
• Test send/receive on a pilot mailbox; sign in to Outlook / phone with just email + password (MAPI / ActiveSync).
• Cut over MX last: point your domain's MX to Skyline Mail only after the new mailboxes are verified. Keep forwarding from the old system for ~2 weeks to catch stragglers.

Phase 2 — Website & hosting

• Choose a hosting plan (Shared 49 / Dedicated 119 / Cloud 199 SAR) or a cloud server if you need OS-level control.
• Copy your site files and database; for WordPress, use one-click install + import.
• Verify the site on a temporary URL before changing DNS.
• Free auto-renewing SSL issues automatically once DNS points at your hosting.

Phase 3 — Domains, DNS & files

• Transfer the domain into Skyline Cloud (or just point DNS) — full domain-transfer detail lives in our domains guides.
• Recreate DNS records in the zone editor (A/AAAA, CNAME, MX, TXT for SPF/DKIM/DMARC); enable DNSSEC.
• Move shared files into Skyline Drive with per-seat quotas — KSA-resident.
• Flip DNS last, with low TTLs, and watch for a clean cutover.

Phase 4 — Verify & decommission

• Confirm mail flows, the site resolves over HTTPS, and team members can sign in.
• Keep the old system in read-only/forwarding mode for ~2 weeks.
• Cancel the old vendors once you've confirmed nothing is missing — and enjoy one SAR bill.

Zero-downtime principles (the short version)

1. Build and verify the new system before touching DNS.
2. Lower DNS TTLs ahead of time so cutover is fast.
3. Cut over MX and DNS last, not first.
4. Keep the old system forwarding for ~2 weeks as a safety net.
5. Migrate the right things, not everything at once — email and the website first; files and extras after.

Ready when you are: Start your free 14-day trial — no credit card →. Build it, verify it, then cut over with confidence.

Related reading: Skyline Cloud — the in-Kingdom platform · Data residency in Saudi Arabia & PDPL · Skyline Cloud vs hyperscalers · Email hosting in Saudi Arabia

Frequently asked questions

Will I lose email during migration?

No, if you cut MX over last. The old mailboxes stay live while mail is copied; you flip MX only after the new mailboxes are verified, and keep forwarding for ~2 weeks.

Do you help with the email migration?

Yes — guided migration support is available for Microsoft 365, Google Workspace and GoDaddy.

Can you migrate my whole AWS/Azure setup for free?

No — arbitrary infrastructure migration is project work, not a free service. We're honest about scope; email/website/domain/files moves are well-supported.

How long does it take?

Most SMBs do email + website over a weekend, then move domains, DNS and files at their own pace.

Is everything Saudi-resident after I migrate?

Yes — email, files, sites, DNS and servers become in-Kingdom, billed in SAR on one wallet.