Microsoft 365 licenses for Singapore · PayNow & GST invoicing

Migration

Exchange to Microsoft 365 Migration

Exchange Server to Microsoft 365 migration for Thai and Singapore SMEs: cutover vs staged, MX DNS, THB/SGD licensing, PST archives, and MFA baseline.

August 2026 · 9 min read · Published by the M365 Deals Editorial Team

Exchange to Microsoft 365 Migration

Exchange Server to Microsoft 365 - Thailand & Singapore Guide

Many SMEs in Thailand and Singapore still run on-premises Exchange - often Exchange 2013, 2016, or 2019 - for company email on @yourdomain.com or @yourdomain.co.th. Microsoft has ended mainstream support for older versions, and hardware refresh plus security patching costs often exceed moving to Exchange Online in Microsoft 365.

This guide explains the migration path, downtime risks, and licensing for Southeast Asian businesses.

Why Move Now?

  • Security - unpatched Exchange is a prime ransomware target; Microsoft 365 shifts patch burden to the cloud
  • Cost - eliminate Windows Server, storage, backup, and UPS cycles for mail VMs
  • Hybrid work - Outlook mobile, Teams, and OneDrive integrate cleanly with Exchange Online
  • Compliance - PDPA (Thailand and Singapore) expects access logs and retention; cloud audit is easier to demonstrate

If you are on Google Workspace instead, see Google to M365 migration. For POP/IMAP hosting, see POP/IMAP to Microsoft 365.

What Gets Migrated

On-premMicrosoft 365 target
User mailboxesExchange Online
Shared mailboxesExchange Online shared
Public foldersShared mailboxes or SharePoint (plan early)
Calendar & contactsExchange Online
PST archivesImport service or staged upload
SMTP relays (scanners, ERP)Exchange Online connector

Active Directory may remain on-prem for other apps - you do not need full AD migration to move mail.

Migration Methods

Cutover (under ~150 mailboxes)

Single weekend: sync mailboxes, switch MX records to Microsoft, disable on-prem send/receive. Best for single-site SMEs in Bangkok or Singapore.

Staged (150–2,000 mailboxes)

Migrate departments in batches; keep hybrid connector temporarily. Common for manufacturing and logistics groups with plant + HQ mail.

Hybrid (complex compliance)

Mailboxes move gradually while on-prem Exchange stays as management endpoint. Higher operational cost - use only when regulations require it.

Pre-Migration Checklist

  1. Inventory - mailbox count, size, shared mailboxes, distribution lists, send-as permissions
  2. Licenses - buy Microsoft 365 before cutover (how to buy)
  3. Domain - verify domain in Microsoft 365; add SPF/DKIM/DMARC (custom domain guide)
  4. Integrations - list devices and apps that SMTP to Exchange; update connectors
  5. Archive policy - decide PST handling and retention labels (PDPA guide)

DNS Cutover (Thailand & Singapore)

Plan MX switch for Friday night → Sunday to limit business impact:

  1. Lower DNS TTL to 300 seconds 24 hours ahead
  2. Run final delta sync Saturday
  3. Point MX to *.mail.protection.outlook.com (priority per Microsoft tenant)
  4. Test inbound/outbound with IT and one pilot user per site
  5. Decommission on-prem receive connectors only after 48 hours of clean mail flow

Singapore .com.sg and Thailand .co.th domains use the same MX pattern - registrar UI differs (SGNIC, THNIC, Cloudflare, etc.).

Licensing by Region

Thailand (THB, before VAT 7%):

PlanIndicativeBest for
Business StandardS$296/user/moDesktop Office + Exchange
Business PremiumS$34.32/user/moAdds Defender + Intune

Singapore (SGD, before GST 9%):

PlanIndicativeBest for
Business StandardS$6/user/moDesktop Office + Exchange
Business PremiumS$13/user/moSecurity-conscious SMEs

See /price for current CSP rates.

Downtime Expectations

  • Mailbox sync - hours to days depending on data volume and bandwidth
  • MX propagation - typically under 4 hours with low TTL; allow 24 hours globally
  • User experience - Outlook may prompt re-profile; communicate before cutover

We plan cutovers so inbound mail queues at the old server during MX propagation - nothing should be lost if TTL and sync are done correctly.

After Migration

Singapore Office 365 Naming

Singapore buyers often search Office 365 to Microsoft 365 - if you already have cloud E3, you may only need SKU renewal alignment. Read Office 365 to M365 migration Singapore.

Get Help

M365 Deals migrates on-prem Exchange for Thai and Singapore businesses - fixed-scope quotes in THB or SGD, DNS cutover support, and post-migration MFA baseline.

Last updated: August 2026.

Common questions

How long does Exchange migration take?

Small offices (under 50 mailboxes) often complete in one weekend. Larger staged migrations take 2–6 weeks depending on mailbox size and public folder complexity.

Will we lose email during MX cutover?

Not if you run a final delta sync and switch MX with low TTL. Mail may queue briefly at the old server during DNS propagation - plan a 48-hour overlap before decommissioning.

Do we need Enterprise plans?

Most SMEs use Business Standard or Premium. Enterprise E3/E5 is for larger tenants, advanced compliance, or 300+ seats with Entra ID P1 requirements.

Can you migrate from Exchange and Google at the same time?

Usually we consolidate to one tenant per region first. Multi-source migrations are scoped as separate workstreams with a single cutover weekend.

Ready to make the switch?

If you've decided Microsoft 365 is the right fit - or you're still weighing options - we'll help you pick the right plan for your team.