Your organization has scaled, and you’re migrating from G Suite to Office 365 (now Microsoft 365). We can debate ad nauseum on the pros and cons of G Suite vs Microsoft 365. However, one thing is certain – a secure and successful migration is critical to getting maximum ROI from either platform. Deep breath, step back and follow through our pointers below where we discuss the whys and hows of migration. And the important aspect of securing your Office 365 migration. Migrating the other way around from Microsoft 365 (Office 365) to G Suite? Read our Microsoft 365 to G Suite migration guide
The Whys: Migrating From G Suite to Microsoft 365 (Office 365)
Familiarity: The older giant beats Google with an incomparable adoption rate in the business community. Most of the now professionally active folks literally grew up with Microsoft. It reduces the precious time spent for communication and coordination. This helps reduce adoption effort and re-training costs. Also, if you have to send any files around, and an external partner is on your mailing list too, you’ll have to get back to the good old Microsoft formats. Desktop-friendly: Do a majority of your employees use desktop computers? Well, Microsoft 365 shines in that department. G Suite is essentially web-based. It falls short when compared with the proven offline app support of Office 365. Particularly the Outlook desktop client and OneDrive.Collaboration mechanisms: Yes, we’re talking about Microsoft Teams. Although file collaboration solutions of both platforms are pretty much identical, Microsoft managed to create a real enterprise working hub: the Teams app. It has no alternative on the market so far.Scalability: Your organization is growing. You need a SaaS platform with proven scalability. An area that Microsoft 365 (Office 365) shines in. Apart from offering a variety of plans to suit every organization size, it also has inherent Azure support for effortless scalability. It can grow with your organization.
The Hows: Migrating From G Suite to Microsoft 365 (Office 365): Buy-in, Scope, and Timelines
Before you go ahead with the technical part, understand the needs of your company. Remember, that you do not only migrate data, but entire business workflows that impact daily routines and productivity. A robust migration plan is the first step to minimizing post-migration turmoil.
Get stakeholder buy-in and migration champions. Cannot reiterate how essential strong stakeholder buy-in is to help smoothen hiccups along the way. Cultivate department-wide Office 365 experts who are aware of and fully convinced of the advantages of using the new platform.
Understand the breadth of apps being currently used. Map the working procedures and features from G Suite with their twins in Office 365, or find a good alternative.
Chalk out the timeline and scope: With rare cases, you may need to migrate everything in one move. However, a gradual, staged migration mitigates risks. Strongly consider a pilot migration to get org-wide support for your plan.
A final rollup before jumping in
Congratulations, you have a put stressful preparation phase behind you with these deliverables:
A schedule that clearly reflects your chosen type of migration: staged or cutover.
In case of a gradual migration, you’ve defined batches to be moved separately.
You have a list of essential native Microsoft or Google tools, as well as of the third-party vendors.
A tick in each of these to-do boxes? Then, let’s take off!
Step-by-step Migration Guide: G Suite (Google Apps) to Microsoft 365 (Office 365)
Setup a Google Service Account
Migrating from G Suite to Office 365 is only possible if you already acquired and verified a custom domain.In Chrome, from the Developer page for Google accounts, create a migration project by typing in your domain name twice. Follow the path IAM & Admin > Service Accounts > Create Service Account to create your service account. Click Continue and then Done on the next two screens. You’ll land in the list of the existing projects. Select yours and click Edit. From the Service account details page write down the Unique ID.Click Show Domain-Wide Delegation. Make sure that it is enabled by ticking the box at Enable G Suite Domain-wide DelegationGo back to the Service account details page. Create a JSON file with your key. The download of the file will start automatically. You will need the exact file name for later.
Grant access to the service account
Now go to the G Suite Admin page, and follow the path Security > Advanced settings > Manage Domain Wide Delegation. You see the API Clients list, choose Add newThe Client ID is the Unique ID from one of the previous steps. In the OAuth Scopes, you need to list the products to migrate, like e-mail and calendar. Separate items in the list with commas. For instance:“https://mail.google.com/,https://www.googleapis.com/auth/calendar,https://www.google.com/m8/feeds/,https://www.googleapis.com/auth/gmail.settings.sharing”Press Authorize to finish this step.
Mail Routing to Office 365
On the G Suite Admin page, open Domains > Manage domains > Add a domain. After entering a sub-domain, a few simple steps are needed to verify the ownership. You’ll also need to update your Mail Exchanger (MX) record in the Domain Name System (DNS).
Mail routing to the G Suite domain
On the G Suite Admin page, open Domains > Manage domains > Add a domain alias. Follow similar steps as in the previous section:
Eventually, you arrive at the final stage of migrating from G Suite to Office 365. In the Microsoft Exchange admin center, follow the path recipients > migration > New + > Migrate to Exchange Online. Choose G Suite (Gmail) migration.Upload a .CSV containing e-mail addresses of the migrated users.You’ll be asked to upload the JSON file from one of the previous steps. Don’t forget to enter your Google super admin email.Click Move configuration. Remember, the step Mail routing to Office 365? This one you put in here!Customize progress notifications by accessing “Start the batch”.
Does the “Synced” status appear now? Well done! Lastly, update your MX record in the DNS. For further details, please refer to the documentation here.
Some users may approach you with more extravagant requests. For such cases, – and for anything you could not solve by yourself! – you simply ping our Customer Support Hub. We are ready to talk, chat, or exchange e-mails with you. A request from any communication channel, including a support ticket opened via our online form, will be equally valued. After the migration period seems to be over, you do not give up your data protection best practices. Without changing your data recovery partner, you simply switch to CloudAlly’s Office 365 backup. Thus your entire migration from G Suite to Office 365 is completely secured from data loss.
Subscribe to our latest blog posts
Get Posts Via Email - With the latest insights on cloud-to-cloud backup.
Click the RSS icon below sign up and get our blog posts by RSS: