Moving Company Email from a Rental Server to Microsoft 365 or Google Workspace
Cost and Steps
Moving custom-domain email from a rental server to Microsoft 365 or Google Workspace: Workspace prices, MX/SPF/DKIM/DMARC cutover, parallel run, vendor costs.
Moving from the email bundled with a rental server to Microsoft 365 or Google Workspace is decided less by licence fees than by the DNS cutover and by how past mail is carried over. Licences run from a few hundred to a few thousand yen per user per month, so for a five-person company the monthly difference between plans is small. A botched cutover, however, can mean email goes missing for hours or days. This article covers when to consider moving, how to choose between the two services, migration approaches, the DNS cutover steps, vendor cost ranges, and common failures, in terms a non-IT manager can use to decide.
When to consider moving
Because bundled email comes with the website hosting contract, many companies simply keep using it. The following signs mean it is time to review.
- Running out of space: mailboxes are near their limit and people delete old mail to cope
- More spam and spoofing: spam filtering is crude and protection against fake mail using your domain is weak
- Server contract renewal: you redo the website and want email handled separately
- Joiners and leavers: only someone with access to the server panel can add or suspend accounts
- Poor phone and calendar sync: shared schedules and smartphone sync do not work well
- One-person dependence: only one person (or the web agency) knows the settings
- Website server change: moving the server forces the email settings to be rebuilt as well
The last two hurt the moment that person is unavailable. The main goal of migrating is to put control of company email in the company's own hands.
Microsoft 365 or Google Workspace
Both let you keep your custom-domain addresses (info@yourdomain). The difference is fit with the tools you already use. If staff work daily in Word, Excel and PowerPoint and exchange those files with clients, Microsoft 365 fits; if work is browser-based with shared spreadsheets and documents, Google Workspace fits. For a wider comparison see Google Workspace vs Microsoft 365, and for groupware costs see groupware cost comparison. Here we focus only on what matters for email migration.
| Item | Microsoft 365 (Business) | Google Workspace |
|---|---|---|
| Mail interface | Outlook (app and web) | Gmail (web and app) |
| Monthly price per user | Check the official page (varies by Teams option and term) | Starter JPY 800 / Standard JPY 1,600 / Plus JPY 2,500 (excl. tax, official Japanese page, Nov 2026) |
| Smallest plan with email | Business Basic type (web-based apps); choose a higher plan if you need desktop Office | Business Starter (30 GB storage per user) |
| Best for | Companies exchanging Office files | Companies co-editing in the browser |
| Past-mail migration tools | IMAP migration from the admin center, etc. | Data migration service in the admin console |
| Billing | Price differs between annual and monthly terms | Billed monthly (check the official page for annual discounts) |
| Watch out for | Same name, different products depending on Teams | A limited-time discount was shown in November; check conditions officially |
Google Workspace prices are the monthly amounts shown excluding tax on the official Japanese page in November 2026. Microsoft 365 splits into different products and prices by Teams option and by annual versus monthly terms, and we could not confirm the amounts on the official page when writing, so we give no figures here. Check the tax-excluded price for your headcount on the official Microsoft 365 Business page before contracting. Either way, the per-user monthly difference is often smaller than the outsourcing fee for the migration work.
Two migration approaches
The workload depends heavily on whether you simply start fresh or also bring past mail along.
| Approach | What it means | Suits | Effort |
|---|---|---|---|
| Fresh start only | New mail after cutover goes to the new service; past mail stays on the old server (viewed there) | Little need to revisit old mail / few users | Low |
| Migrate past mail too | Copy old mailboxes to the new service with a migration tool | You search deal history or keep quotes and contracts | Medium to high |
| Manual export | Each user makes a backup (e.g. PST) in a mail client and imports it | 1 to 3 users where tooling is overkill | Scales with users |
With a fresh start only, cancelling the old server also makes past mail unreadable. Save what you need before the cancellation date.
Overview of the steps
The work falls into four stages: preparation, building the new environment, cutover and cleanup. The cutover day looks like the key moment, but most accidents come from oversights in preparation.
| Stage | What to do | Typical time |
|---|---|---|
| 1. Inventory | List addresses, shared addresses, forwarding, auto-replies and systems that send mail | 3-7 days |
| 2. Contract and domain verification | Sign up and prove domain ownership (add a TXT record) | 1-3 days |
| 3. Create accounts | Users, aliases, shared mailboxes or groups | 1-3 days |
| 4. Shorten TTL | Lower the MX record TTL 2-3 days before cutover | 2-3 days before |
| 5. Migrate past mail | Start copying before cutover (hours to days depending on size) | 1-5 days |
| 6. DNS cutover | Point MX to the new service; update SPF, DKIM, DMARC | Cutover day (outside business hours is safer) |
| 7. Parallel period | Collect mail still arriving at the old server and sync differences | 1-2 weeks |
| 8. Device setup | Reconfigure PCs and phones | Around cutover |
| 9. Retire the old service | Cancel the old mail contract and tidy accounts | After the parallel period |
Easily missed items in the inventory
The inventory is the least glamorous step and the most effective. List the following.
- All addresses: not just personal ones but shared ones such as info@, support@, sales@, plus aliases and mailing lists
- Forwarding and auto-replies: settings made on the old server are not carried over automatically
- Systems that send mail: contact forms, booking and invoicing systems, multifunction printers that scan to email, newsletter services; many use the old server's SMTP
- Other uses of the address: login IDs for other services and password-reset destinations
- Who manages DNS: the registrar, the server company or the web agency
- Large mailboxes: heavy users take longer to migrate, so identify them early
Printers and forms are the easiest to forget. Make it possible to send test messages from them before cutover.
DNS cutover steps (MX, SPF, DKIM, DMARC)
The heart of the cutover is changing DNS. DNS is the domain's address book, and it also states which server receives your mail. Changes are made in the management screen of whoever manages the domain (registrar or server company).
| Record | Role | Action at cutover |
|---|---|---|
| TXT (domain verification) | Proves to the new service that you own the domain | Add right after signing up; does not affect delivery |
| MX | Which server receives mail for your domain | Replace the old server's value with the new service's on cutover day |
| SPF (TXT) | Servers allowed to send mail as your domain | Update to include the new service; keep a single record |
| DKIM (TXT/CNAME) | Public key for the signature on outgoing mail | Enable in the new admin screen and add the values it gives |
| DMARC (TXT) | Handling of SPF/DKIM failures and reporting address | Check any existing record; otherwise start with monitoring (none) |
Once MX changes, new mail for the domain reaches the new service. DNS changes take time to propagate, though, so some mail keeps arriving at the old server for a while. Shortening the TTL limits this. TTL says how long a setting may be cached; lowering it to a few minutes or an hour 2-3 days before cutover shortens the time it takes for mail to reach the new environment. Note the original value and restore it once things settle.
SPF, DKIM and DMARC prevent outgoing mail from landing in spam or being rejected by clients. For how they work and a staged rollout see SPF, DKIM and DMARC for small businesses. A frequent mistake in migrations is leaving the old SPF record and adding a new one, ending up with two. Keep one SPF record per domain.
Parallel period and device setup
Do not shut down the old server on cutover day. Until DNS propagation finishes, new mail can still reach it. Keep the old mailboxes for one to two weeks and pull stray mail into the new environment. During this period switch PCs, phones and printers to the new settings. Servers change, and so do authentication methods and passwords. Companies with more than ten devices should split the work and plan to finish in the morning of cutover day.
- 1-2 days before: tell everyone the cutover date, what will change and how to set the initial password
- Cutover day: change MX, then test sending and receiving among 2-3 people (internal and with an external free mail account both ways)
- Day after: confirm mail from clients, form notifications and printer scans work
- One week later: check again for mail left on the old environment
- Two weeks later: if no problems, proceed to cancel the old service
Do it yourself or hire a vendor
With one to three users and someone who can edit DNS, doing it in-house is realistic. As headcount grows, inventory gaps and device setup effort swell. The figures below are rough guides only for outsourcing, and vary with headcount, mailbox size and scope. Confirm actual costs through quotes.
| Work item | Guide (excl. tax) | Notes |
|---|---|---|
| Current-state survey and inventory | JPY 20,000-50,000 | Addresses, sending systems, DNS owner |
| Contract and initial setup | JPY 20,000-50,000 | Domain verification, users, shared addresses |
| Past-mail migration | JPY 10,000-30,000 plus a few thousand per user | Varies with size and method |
| DNS cutover (MX, SPF, DKIM, DMARC) | JPY 30,000-80,000 | Depends on whether on-site attendance is included |
| Device setup (PC and phone) | A few thousand yen per device | May be cheaper per unit at higher counts |
| Parallel-period follow-up and support | JPY 20,000-50,000 | Check the limits on period and number of inquiries |
| Total (example for 5-10 users) | JPY 100,000-300,000 | Varies widely with past-mail migration and device count |
When requesting quotes, confirm what is included. A quote for only switching MX and a quote covering everything from inventory to device setup and parallel-period follow-up can differ by several times. For tidying up domain and server contracts see domain and server costs and contracts.
Common failures
- Cancelling the old server first: past mail becomes unreadable. Cancel only after verification and the parallel period
- Forgetting forwarding and auto-replies: old settings do not carry over; list them in the inventory
- Form and printer notifications stop: the sender settings were not updated for the new environment
- Two SPF records: causes spam placement or rejection; merge into one
- TTL not shortened: mail routing stays unstable between old and new for longer
- Cannot reach the DNS manager: a former web agency or ex-employee holds DNS; confirm who has authority before migrating
- Changing nameservers for the whole domain: you meant to edit mail records only, and the website goes down. Change only the relevant records
- Single admin account: if that person leaves, nobody can operate it. Have two admins and enable multi-factor authentication
For isolating mail that will not arrive or send, see first response when company email fails. If something breaks right after cutover, check the MX and SPF values first.
What to confirm after migration
Do not relax just because you signed up. Decide the account suspension procedure for leavers, password and multi-factor authentication rules, and a backup policy. Cloud mail means the provider maintains the servers, but recovery from accidental deletion or account takeover remains the subscriber's responsibility. Whether backup is needed and what it costs is covered in backup costs for Microsoft 365 and Google Workspace.
Pre-migration checklist
- Listed all email addresses in use, including shared ones, aliases and mailing lists
- Identified forwarding, auto-replies and filters on the old server
- Listed systems that send mail (forms, printers, booking, invoicing)
- Confirmed who manages DNS and where the login details are
- Chose Microsoft 365 or Google Workspace and checked the tax-excluded monthly price for your headcount on the official page
- Decided whether to migrate past mail or leave it on the old environment
- Planned to shorten TTL 2-3 days before cutover
- Confirmed the procedure for updating SPF, DKIM and DMARC for the new environment
- Scheduled cutover outside business hours or at a quiet time
- Set the parallel period (1-2 weeks) and the cancellation date of the old service
- Made two admin accounts and enabled multi-factor authentication
- Informed staff of the cutover date, initial password setup and whom to contact
FAQ
Can we keep our current email addresses?
Yes. Custom-domain addresses (info@yourdomain) stay the same. You prove domain ownership to the new service and switch the MX record to the new value; the address strings do not change.
How long does migration take?
For 5-10 users, plan on three to four weeks overall from inventory to the end of the parallel period. The cutover itself takes a few hours, but preparation and the parallel period take longer. Large mailboxes can need several days just to copy.
Will email stop arriving during the cutover?
If you shorten the TTL, cut over outside business hours and keep the old environment during a parallel period, a gap in delivery can almost always be avoided. During propagation mail may reach either side, so check the old environment for one to two weeks.
Do we have to migrate past email?
No. Companies that rarely look back at old mail can start fresh and keep the old environment for a while to read it. Cancelling the old server makes it unreadable, so save deal history and contract-related mail before cancelling.
How much do the monthly prices of Microsoft 365 and Google Workspace differ?
The official Japanese Google Workspace page in November 2026 shows Business Starter JPY 800, Standard JPY 1,600 and Plus JPY 2,500 per user per month, excluding tax. Microsoft 365 prices vary with the Teams option and term, so check the tax-excluded price for your headcount on the official page.
Should we do it ourselves or hire a vendor?
With one to three users and someone able to edit DNS, in-house is feasible. With more users, many sending systems or an unreachable DNS manager, outsourcing even just the inventory and cutover-day attendance reduces failures.
Summary
Email migration is decided by sequencing rather than by licence choice. Inventory the senders and settings, shorten the TTL before cutover, keep a parallel period, and cancel the old service last. Follow that order and an email outage is largely avoidable. Start by putting your email addresses and DNS manager on a single sheet.
株式会社オブライト
Oflight Inc. is a Tokyo-based IT company providing software development, digital signage, web development, network systems, and IoT/AR/VR technology services.
Related free tools (no sign-up, instant results)
Feel free to contact us
Contact Us