Microsoft 365 Migration in Malaysia: Google Workspace to M365, Tenant Moves & Timeline

Short answer: A Microsoft 365 migration in Malaysia after an acquisition is usually three migrations in one: Google Workspace mail, calendars and Drive into the group tenant, any hosted (IMAP) mailboxes, and sometimes a second Microsoft 365 tenant. Microsoft's own tools handle Workspace mail and Drive. Settle identities, the local domain, devices and data-transfer questions before you move a mailbox. For 30-40 users, five to eight weeks end to end is a typical range.

Who is this guide for?

This guide is written for a group IT manager at a Hong Kong or Singapore company that has just bought, or is about to buy, a small business in Kuala Lumpur. The acquired team has its own email and files, usually on Google Workspace, sometimes on a local hosting provider, occasionally on its own Microsoft 365 tenant. The group wants everyone on one tenant, one sign-in and one set of security policies.

It is the Malaysia companion to our playbook for a Microsoft 365 migration after an acquisition in Singapore, which covers a tenant-to-tenant move. Here the more common starting point is Google Workspace.

Case study (illustrative composite, not a named client): A Hong Kong trading group buys a 35-person distributor in Kuala Lumpur. Most staff use Google Workspace on the company's .com.my domain; the four-person sales team still uses mailboxes on a local web host that came with the website. Files live in a mix of personal Drives and two shared drives. Laptops were bought by staff and are not managed. The group runs Microsoft 365 from Hong Kong with Intune and Conditional Access, and wants the Kuala Lumpur team inside that tenant within one quarter of completion.

What does "bringing the team into the group tenant" actually involve?

It is tempting to treat this as moving mailboxes. In practice there are five separate jobs, and the mailboxes are the easiest of them.

• Identity. Each person needs an account in the group tenant, with a naming convention, a licence and the right group memberships. Decide whether the Kuala Lumpur staff keep their .com.my email address, move to the group domain, or carry both.
• Data. Mail, calendars and contacts, plus Drive files and shared drives, have to move with their folder structure and, where possible, their sharing permissions.
• Mail flow. At some point the MX records for the .com.my domain point to Microsoft 365 instead of Google or the web host. Until then, the two systems have to coexist.
• Devices. Laptops and phones need to be enrolled in the group's device management so the group's security policies apply. Unmanaged personal laptops are the usual surprise.
• People. Staff need to know what changes on which day, in a language they read comfortably. Many Kuala Lumpur teams work across English, Bahasa Melayu and Mandarin.

Which migration path fits: Google Workspace, hosted email or another tenant?

The source system decides the method. Most acquisitions have more than one source, so expect to use more than one path.

• Google Workspace to Microsoft 365. Microsoft documents a native Google Workspace migration in the Exchange admin center that moves mail, calendar and contacts in batches; Microsoft recommends its automated method, which completes several of the Google-side setup tasks for you. Some items do not move, including shared calendars and event colours. Drive content moves separately, through Migration Manager in the Microsoft 365 admin center: you connect to Google with the Microsoft 365 migration app, scan and assess the drives, review destinations, map identities and migrate. A simplified Migration Manager Lite is enabled by default for tenants with fewer than 300 Microsoft 365 licences.
• Hosted email (IMAP) to Microsoft 365. Mailboxes on a web host or local ISP usually come across with an IMAP migration. IMAP moves email only; calendars and contacts have to be exported and imported separately, or rebuilt.
• Another Microsoft 365 tenant to the group tenant. Microsoft's native cross-tenant mailbox migration needs a per-user Cross Tenant User Data Migration licence, a one-time fee that also covers OneDrive. Third-party migration tools are the other route, especially when Teams and SharePoint have to move too.
• Google Sites, Apps Script and add-ons. These rarely have a clean migration path. Inventory them early and decide whether to rebuild, replace or retire each one.

Brocent publishes reference prices for third-party migration tooling on the Microsoft 365 migration pricing page, so you can see per-user tool costs before anyone quotes you labour.

What has to be decided before you move a single mailbox?

Most migrations that go badly were decided badly in week one. These are the decisions to close first.

• The domain. Add the .com.my domain to the group tenant as an accepted domain and decide when it becomes the primary address. Lower the DNS TTL on the MX record well before cutover.
• Licence mapping. Map each Google Workspace edition to a Microsoft 365 plan. Not everyone needs the same plan; frontline or warehouse staff may need less than finance. Current Microsoft 365 list prices are on the Microsoft 365 pricing page.
• Overlap period. Plan how long Google Workspace stays live after cutover for stragglers, delta syncs and anything forgotten. Budget for that overlap using Google Workspace pricing, and do not cancel the subscription until Drive data is verified.
• Security from day one. Apply the group's Conditional Access, MFA and device policies to the new accounts before they receive mail, not after. Migrating into a tenant with weaker rules for a "temporary" group tends to make the exception permanent.
• Devices. Decide whether staff laptops are re-imaged and enrolled, replaced, or allowed as personal devices with app-level protection only.
• Shared drives ownership. Shared drives often belong to people who have left. Assign an owner for each and decide whether it becomes a SharePoint site or a Team.
• Personal data and cross-border transfer. Moving a Malaysian company's staff and customer data into a group tenant may move it outside Malaysia. Malaysia's Personal Data Protection Act was amended in 2024, and the Personal Data Protection Commissioner's guideline on cross-border personal data transfer explains the current conditions. Check where your tenant stores data and ask counsel whether the transfer needs documenting. This is not legal advice; the migration plan should simply leave room for the answer.

What does a typical timeline look like?

The ranges below are typical for a 30-40 person team with one Google Workspace domain and a few hosted mailboxes. They are not a commitment: data volume, approvals and device logistics move them. Microsoft notes that a single migration batch can take from several hours to a couple of days, depending on how much data is in it.

1. Discovery and decisions (about 1-2 weeks). Inventory users, mailboxes, shared drives, groups, aliases, Sites and devices. Close the decisions in the previous section.
2. Build and pilot (about 1 week). Create accounts, apply policies, set up the migration endpoints, and migrate three to five volunteers end to end, including their phones and laptops.
3. Pre-stage the data (about 1-2 weeks). Copy mail and Drive content in the background while staff keep working in Google. Fix errors from the scan reports as they appear.
4. Cutover (usually over a weekend). Freeze changes, run a final delta, switch the MX records, and point users to Outlook and OneDrive on Monday morning.
5. Hypercare (about 1-2 weeks). Daily check-ins, a visible support contact in Kuala Lumpur, and quick fixes for missing calendars, shared mailbox permissions and phone profiles.
6. Clean-up (about 2-4 weeks). Verify that Drive data is complete, retire the hosted mailboxes, export what legal or finance must keep, and cancel Google Workspace.

Put together, that is roughly five to eight weeks from kick-off to Monday morning in the new tenant, and a few weeks more before the old systems are switched off.

Which technical details catch teams out?

A few details from Microsoft's own documentation account for a large share of avoidable delays. None of them is difficult; they are just easy to miss on a first Workspace migration.

• Mail-routing subdomains and mail-enabled users come first. Microsoft's Google Workspace migration expects routing subdomains to be set up and the target users to exist in Microsoft 365 before any batch starts. Build the accounts during the pilot week, not on cutover Friday.
• Retention policies can hide migrated mail. Microsoft advises turning off retention and archival policies on the target mailboxes before migrating, because they can make migrated items look missing. Switch them back on, deliberately, once the migration is verified.
• Large Drives need splitting. Microsoft says a single Migration Manager task for a Google Drive should not exceed 100,000 items or 1 TB of data. Split the finance or design team's large drives by root folder before you schedule them.
• Identity mapping is not the same as permissions. Mapping Google identities to Microsoft 365 accounts is a prerequisite for carrying sharing across, but file-level permissions still need a separate review. Check the shared drives your sales and finance teams depend on before cutover, not after.
• OneDrive has to exist before files arrive. Pre-provision OneDrive for every migrating user, or the destinations can fail validation.
• Phones are the long tail. Mail and files move centrally; phones move one person at a time. Budget an engineer's time in the office for the first two working days.

How do you cut over without losing mail?

The goal is a cutover that staff barely notice. The details that make it work:

• Lower the MX TTL several days before cutover, so the change propagates in minutes rather than hours.
• Pre-stage everything you can. By cutover weekend, only the last few days of mail should be left to copy.
• Keep the sources readable. Starting a Migration Manager job does not delete anything in Google Workspace, and the hosted mailboxes should stay accessible until verification is done.
• Fix aliases and distribution lists before the switch. A sales alias that silently stops receiving mail is the most common post-cutover complaint.
• Rebuild phone profiles deliberately. Tell staff exactly when to remove the Google account from their phone and add Outlook, and have someone on site to help.
• Communicate in the team's languages. One short notice in English, Bahasa Melayu or Mandarin, sent twice, beats a long technical email nobody reads.

What does a Microsoft 365 migration in Malaysia cost?

There are three cost lines, and it helps to keep them apart when comparing quotes.

• Licences. Microsoft 365 licences for every migrated user from the cutover month, plus Google Workspace for the overlap period. Both have published list prices on the pages linked above.
• Tooling. Microsoft's native Google Workspace and Migration Manager tools carry no separate tool fee. A cross-tenant move uses Microsoft's per-user licence or a third-party tool; reference prices are on the migration pricing page.
• Labour. Planning, pilot, cutover support and hypercare. This is where providers differ most, and it is usually quoted on scope rather than per mailbox. Ask whether onsite support on cutover Monday is included.

As a cloud service provider in Malaysia, the useful questions are less about the per-mailbox rate and more about who owns the decisions, who is in the office on Monday, and who supports the team in the month after.

How do the provider types compare?

Companies looking for enterprise cloud services in Malaysia usually choose between four kinds of help. The comparison below is by type, not by name.

• Group IT does it alone, remotely. Lowest external cost and full control. Works if the group team has done a Workspace migration before and can spare two to three people for the cutover window. The gap is on-the-ground help in Kuala Lumpur.
• A local licence reseller. Often bundles migration with the licence sale and knows the local market. Check whether the migration is a project with a plan or a script that copies mail, and who supports staff after cutover.
• A specialist migration firm. Strong tooling and experience with complex tenant moves. Usually stops at cutover; ongoing support and security belong to someone else.
• A regional managed IT provider. Plans the migration, runs the cutover with people on site, and then supports the team as part of the group's IT. Higher scope, but the same team owns the result after Monday.

Where does Brocent fit?

Brocent's Microsoft 365 and cloud services cover migration planning, staged cutover and post-migration support and governance. In Malaysia, Brocent's IT support in Malaysia page states that it runs a Kuala Lumpur service satellite site through its Malaysian entity, supports Klang Valley directly, works in English, Bahasa Melayu and Mandarin, and lists Microsoft 365 migration among its Malaysia services. That means the same team can plan the move from Hong Kong, be in the Kuala Lumpur office on cutover Monday, and take the acquired team into day-to-day support afterwards.

Frequently asked questions

How long does a Google Workspace to Microsoft 365 migration take for 35 users?

A typical range is five to eight weeks from kick-off to cutover, with a few more weeks of clean-up before Google Workspace is cancelled. The data copy itself is often the shorter part; decisions, devices and approvals take longer.

Can Microsoft's own tools migrate Google Drive?

Yes. Migration Manager in the Microsoft 365 admin center migrates Google Drive content to OneDrive and SharePoint after you connect it to Google Workspace. A simplified Lite version is enabled by default for tenants with fewer than 300 Microsoft 365 licences.

What does not migrate from Google Workspace?

Microsoft lists items that the mail migration does not move, including shared calendars and event colours. Google Sites, Apps Script projects and third-party add-ons usually need to be rebuilt or replaced. Inventory them during discovery.

Do we need a special licence to move mailboxes from another Microsoft 365 tenant?

For Microsoft's native cross-tenant mailbox migration, yes: a per-user Cross Tenant User Data Migration licence, charged once, which also covers OneDrive. Third-party tools are the alternative.

Can staff keep their .com.my email addresses?

Yes. Add the .com.my domain to the group tenant as an accepted domain and keep it as the primary or a secondary address. Many groups keep the local domain for customer-facing staff and add the group domain alongside it.

Does moving data into a Hong Kong-run tenant raise PDPA questions?

It can, because the data may leave Malaysia. The Personal Data Protection Commissioner's cross-border transfer guideline explains the current conditions. Confirm the tenant's data location and ask counsel whether anything needs documenting.

Should we migrate before or after legal completion?

Plan before, move after. Discovery and decisions can start once the deal is signed; moving data and accounts should wait until the group legally owns the business and has agreed access with the seller.

Next steps

Start with an inventory and the decisions on domain, licences, devices and data location; the copy jobs come later. For the full checklist approach, our Microsoft 365 migration checklist for Hong Kong businesses works for a Kuala Lumpur team too. If you would like a Brocent consultant to scope the migration and the support afterwards, get a quote for Malaysia and tell us the user count and the systems the team uses today.