Migrate Google GSuite to Microsoft 365 with Native Tools - Part 2/3
Вставка
- Опубліковано 19 вер 2024
- Video - Part Two of Three - (2/3)
Yes it is possible. You can migrate Google GMail and Google Drive into Microsoft 365 (Exchange Online and OneDrive) without any third party tools. Now this doesn't mean that the tools no longer provide any value because there are definitely situations whereby the toolsets are an awesome thing to have during a migration. What it means is that sometimes the migrations are considered fairly simple in nature.
When this is the case then Native Tools can get the core workloads across into Microsoft 365 without a huge amount of work.
Please click here to subscribe to the channel. ua-cam.com/users/th...
In this video series I have three sessions.
Part One
* The Discovery Process for the Google environment
* Extracting the User Lists and deciding who is migrating
* Creating the identities in Microsoft 365
* Enabling licensing for the accounts
* Preparing the accounts in Microsoft 365 for OneDrive migration
Part Two
* Preparing Google to extract the data
* Performing the complete Mail migration, showing it in real time
* Updating MX records for Mail Flow
* Forwarding mail from Google to Microsoft 365, for use in a 'Slow Burn' migration rather than a 'Big Bang' approach
Part Three
* Preparing Google Drive to extract the data
* Using the Native Tools in Microsoft 365 to migrate the data to OneDrive
* Discussion on issues in OneDrive during a migration
* Showing the data extract End-to-End
* Summary
All of these contain all the errors, mistakes, and things that go wrong along the way. I fix the problems in the video too, but this is all to keep the series more real world as this stuff always happens.
I do hope this video series is helpful for anybody needing to migrate from Google into Microsoft 365. Please subscribe to my channel to stay updated with new videos.
Please visit the website for more cloud based content - thecloudgeezer...
Mark - The Cloud Geezer
I didn't actually try this yet (doing a pre-run of your series before watching a second time and completing alongside you), but this is incredible. That it's 2023 and this is the only clear way that demonstrates the process is mind-boggling. That you presented everything so methodically and clearly, and answer every question that comes up here, is amazing. I subscribed. Thank you!
Thanks for the comment. I just replied to the other one too.
The best video ever regarding Google GSuite to Microsoft 365 migration! Microsoft Learn provides basic information but unfortunately sometimes the explanation is not clear enough. I reviewed some other materials but definitely this is the best!
Thank you for that. I really appreciate you taking the time to write it. Mark.
Thank you so much! This had helped me with migrating my 3 mailboxes from G Suite because the KB from Microsoft was too confusing.
To add, I encountered another error which did not show on your demonstration. The error I got was: TooManyTransientFailureRetriesPermanentException: The job encountered too many transient failures (61) and is quitting. The most common failure is GoogleContactClientTransientException with the hit count 60.
Not a lot of details from the other videos, but to resolve it, you just need to enable the Google People API then resume the migration! :)
Very glad that helped out. I can tell you that the 'TransientFailure' message is quite common across many migrations into M365 and is one that normally just clears on its own after a few retries. The Google People API yes that needs to be enabled definitely, looks like that might be missing from the video so thank you for pointing that out.
@@thecloudgeezer Got the same transient error. I have enabled the People API to see if that clears it. I have the following APIs enabled - Gmail (was already enabled), Calendar (had to enable it for the project M365 created event though the migration UI would have you believe it took care of it), Contacts (had to enable it for the project M365 created event though the migration UI would have you believe it took care of it), People (enabled it because Google said the Contact API was no longer in development).
@@jonnychambers I had this error as well and I had to enable the People API as well as the Contacts API even though it is not used! When I enabled the Contacts API, it finished perfectly. It's ridiculous that this isn't documented by Microsoft!
OMG thank you. You saved my whole weekend. Why TF is this not documented by Microsoft. I am glad I checked the comments here.
As of Aug 2024, You will need to go into Google consoles and enable/verify the following APIs are enabled, or you will get errors:
- Gmail API
- Google Calendar API
- People API
- Contacts API
Yes, there are some updates there. Will mean recreating the video! :-) But thank you for commenting, have an awesome week. Mark.
This is awesome. Thank you! What a mess this is to pull off. I looked at a paid service, and their guide to using their software was like a 32 step process so I figured the native tool couldn't be much worse!
It can be a bit cumbersome and tools can make it easier, however I do live and breathe this stuff which makes it a bit easier. That's why I try and share the knowledge to help others. If you do have specific questions or need me to get involved, then drop me a note to mark@thecloudgeezer.com
@@thecloudgeezer I will follow-up if we need some cloud help. The MS product is pretty complicated, we are pretty technical but pulling the levers in control suites is a totaly different ball game. We are a small business, etc. Happy to pay for help if find something tricky we need.
Hi. Sure thing. Let me know if I can be of any assistance. Mark.
This is genius, love your work!
Update on my previous comment: Although I did enable both the Contacts *and People* API, I still get the "TooManyTransientFailureRetriesPermanentException" error for all mailboxes. I am still unclear on whether this affects just contacts, or mail as well. Either way, still unable to find a fix.
EDIT: SOLVED. You need to enter YOUR NEW PROJECT in the Cloud console and manually enable the relevant APIs. I did not successfully complete the migration yet, it's still in process, but I immediately noticed upon entering the specific project that these APIs weren't enabled. What the video doesn't make clear is that you have to enable them in the specific project. Not just when you enter the console.
Yes that is true. Make sure that the API’s are enabled in the specific project that you have the service account etc tied to the M365 migration manager.
Great video! How come you didn't have to setup the mail routing subdomains on Google WorkSpace and M365 as required by the prerequisites? Thank you.
Yes that is a requirement to setup, they are done in other videos, but you are right that they should be in this one. Seems like I need to push some updates. :-)
I love this series and it is helping with my pre-planning. My question is how does this work with a staged migration? I need to move just a few users first while the rest of the company remains using Google.
No problem with coexistence. That is what the setup for the routing domains is about. That way forwarders are in place for the accounts that have already migrated. Also, there are forwarders on the mailuser records in the target that send things across to Google until those users are converted the mailboxes and have people using them. Plenty of different scenarios to cover though but it can work quite happily. If you want to send me a note to mark@thecloudgeezer.com then I am happy to dive into any specifics with you. Mark.
This video is great!!
I have a question on aliases. At what stage do I add them on Microsoft 365? Do I need to do anything differently?
Hi. To stage an alias, you just need to either add an additional alias via the M365 admin center. It is in the Manage Alias section in the Mailbox. Or you can use PowerShell and add an SMTP address that way. You can add as many aliases to a users as you basically want, but obviously they must be unique.
The video is good and clear but I am hitting walls. At the step of Creating Google Workspace service account - The circle spins for hours. No error. If I try to manually create a service account I don't get a checkbox for " Domain Wide Delegation" - The Google instructions say to add permission in User Admin - Security - Access and data control - API controls - MANAGE DOMAIN WIDE DELEGATION using OAuth. If I do that and enable the APIs, it still fails to create the endpoint due to insufficient access. Really stuck.
Hi. I can tell you that the Service Account and the Domain Wide Delegation are in two different areas, in cloud.google.com and admin.google.com but either way you should see the checkbox at least. Drop me a email to mark@thecloudgeezer.com so we can share some screenshots and I can help you a bit better. Mark.
Hello, Thank you for your video. I hope you can help me with my issue below:
My problem is that my company currently has 20 active gmail accounts. However, we want to migrate only 10 accounts to MS 365 and keep 10 accounts using in gmail.
So, I am worried that those 10 gmail accounts won't be able to send/receive their emails via Gmail when I connected domain to Microsoft 365. Cuz I see from your video, we have to delete all DNS records for google and reconnect DNS records to MS 365.
Therefore, I would like to ask if is it possible that we can use our same domain in both gmail and outlook after Migration? And how to do so?
Hi. It is possible yes, with a little bit of configuration. Essentially the domain would still be registered at M365 but you place MailUser identities in there that forward the emails to a subdomain that you have registered on Google. Outbound from Google will continue to work fine. Email me at mark@thecloudgeezer.com and I can give you more detail. Mark.
@@thecloudgeezer Thank you for this series, it really is the best out there! However, can you please post instructions on how to do these migrations in batches like this? This seems to be a very popular topic. I am trying to do the same thing and it seems like a prudent thing to do before cutting over completely.
@@ZedPM7for batching up the users the CSV files that you make for each batch need to be created. Then you can have the batches as small as you like. Normally there is about a 200 mailbox soft limit on batches but it is ideal to make them smaller so you can manage them better. If you want to chat though about your specific scenario then email me at mark@thecloudgeezer.com
@@thecloudgeezer Thanks, I got it sorted out. It works perfectly and you can keep your users on Google and O365 until you are ready to move them all.
Thanks for sharing and helping the community definitely deserved a subscribe😊.
Thank you very much. Glad it was useful.
Great tutorial, thank you! However when enabling the APIs in Google, I get a message that "I may need credentials to use this API", any thoughts on how to get around it? Thank you!!
did you find a solution ?
Can you send me a screenshot of that to mark@thecloudgeezer.com ? That way I can guide you correctly. Mark.
Hello!! I am sorry for the late reply and thank you . Somehow the issue resolved by itself on a second attempt. It might have been some failure on refreshing..
When running this i didn't get the opportunity to download the JSON file. Is there another way to redownload this?
I'm having this same issue. Any one with an answer?
@@bangile clear cache etc etc.
clear cache etc etc.
Yes, in that console, there is an option with the '...' menu on the identity page allowing you to download the JSON. Or you can remove the service account and create a new one, that would also work.
@@thecloudgeezer I did not get the option to download the JSON either and I cannot figure out wht you mena by "in that console, there is an option with the '...' menu". Can you clear that up for me?
hello, I hope you can help me I am performing this same type of migration but it does not work (the migration batch stays in "Syncing").
On the Microsoft 365 page it indicates that you have to create some routing subdomains in GoogleWorkspace and Microsoft 365, do you know if this is outdated?
Hi there. Yes I certainly can. In fact I have just published today a video that explains the 'Target Delivery Domain' and how it affects the Google to M365 migrations. Check this out, ua-cam.com/video/e8WAU7tjPUo/v-deo.html but also email me at mark@thecloudgeezer.com and I am always happy to help out with questions. Mark.
Hi, just a question, ill be doing a migration but one or 2 users has 100+gb Mail usage and the other has more than 50GB usage, is this something that can be handled by the migration or i need to do a pst migration for the said large email usage emails?
You can do large mailbox migrations into the tenant, but you may want to put some filters in place for the content and take them directly into the Archive mailbox if that is enabled on the target tenant. You may be better off using a paid tool like MigrationWiz for this type of migration though. In there you can filter it nicely and direct it straight into the archive without much work. Let me know if I can assist more, mark@thecloudgeezer.com. Have a good weekend. Mark.
Hi, Thanks for the video it was really good and informative. I do have one question. I noticed in your video when you migrated Carls mailbox that the Label called interesting with 4 items had not shown up in 365. Do any labels in google mail show up during the completion stage of the mail migration?
Thanks
Hi Joshua. That is always an interesting one as labels vs folders are the big difference between the two platforms. What will occur is that the migration process creates a folder for each label. It then puts a couple of every mail that has that label in the folder. So if an email has 4 labels, then it will appear 4 times, each copy in the respective folder. It can make a mailbox size blowout a lot if they have a ton of email so watch for that. Let me know if your experience is different during completion. I can chat on mark@thecloudgeezer.com
Labels come across and have folders created. If a mail has for example three labels, then that email will get duplicated into three folders!
Mark.
Hi, I have 3 doubts
1- when i migrate the emails so same time labels will get migrate along with email API right?
2- How many contact i can migrate per user
3- rules will migrate and it will be in off state so we need to enable right
please reply
Hi. I know we have spoken via LinkedIn however I said I would post here as well so others can benefit from your question.
The labels get converted to Folders. Each email will get placed in the appropriate folder. If an email has 2 or more labels, then it is duplicated in the mailbox into each of the folders. This can sometimes lead to a much larger mailbox in the target so be careful with users that have excessive usage of labels.
For the contacts, it is meant to be unlimited but that is an unlikely threshold. I think I need to do a test migration with a 'lot' of contacts and see what happens on the target.
Rules don't have to be 'off' in the source, however it is absolutely a recommendation that users review their use of Rules in the new Target mailbox and setup them up as native M365 versions.
Does this migrate the different versions of a document in Google Drive to One Drive?
This native tool migration only handles the most recent version. If you want previous versions and more metadata style copies then you are going to need a migration tool from a third party like MigrationWiz. If you need any assistance on that, drop me a note to mark@thecloudgeezer.com. Mark.
Great video series that helped me do my first migration using MS tools! I have another in the pipeline and they need their Google Vault data migrated. I can't seem to locate the info I need and was hoping you might have an answer for me. :)
I haven’t made a video on Google vault but that is a great idea. Will throw one together. :-)
@@thecloudgeezer, so it is possible to do with the native tools? I'm really trying to convince my team to move away from using another tool that has really done downhill. Thank you for the reply and looking forward to the new video!!
You ever run into an issue where the automated configuration freezes at "Create a Google Workspace service account in the project" I have a spinning circle for about 10 minutes now, and if I close it the project disappears and I start over. Not sure where to go from here.
I have had that yes. I did the normal clear cache etc etc. but realistically it worked the next day so I put it down to a backend configuration issue and just moved on.
@thecloudgeezer I'm encountering the same issue. Did you leave the wizard open until it eventually completed?
@@scunaz Check all the rights you have assigned. There is a part in there that is supposed to grant you the rights to do this procedure, but it didn't give me all of them. Sorry it has been months so I don't remember which rights were missing.
Is there a way to import the users recovery email and alias email information from google workspace into office365? This is one of the complaints I'm getting after a migration. Also no way to email all the users their logins, we are having to just send the password to an admin who dsitributes it
Hi. Yes, there are ways to do all that. Firstly, use the GAM tool in Google to export the Recovery Address - sites.google.com/jis.edu.bn/gam-commands/people/users?authuser=0 - Then use the PowerShell module in M365 to add it as an 'alternatve email' - Set-MsolUser -UserPrincipalName username@domain.com -AlternateEmailaddresses alternate@domain.com
As for the email sending to users, there are also ways to send emails via PowerShell too, so if you are creating the new password in the run sheets then you could use that to trigger the email with the login details.
All of this is additional functionality that is not in the normal consoles, but available through PowerShell and GAM with some custom scripting.
Happy to help out if you need me - mark@thecloudgeezer.com
Very nice 👌
Thanks 😊