Anyone had any experience migrating email from a Godaddy Office 365 account to G-Suite? I'm not getting anywhere with the G-Suite migration tool. I keep getting bad authorisation or incorrect source SSL certificate messages. Should it be a straightforward O365 > G-suite migration or have Godaddy thrown a couple of spanners in the works to thwart the obvious methods?

4 Replies

This person is a verified professional.

Anyone had any experience migrating email from a Godaddy Office 365 account to G-Suite? I'm not getting anywhere with the G-Suite migration tool. I keep getting bad authorisation or incorrect source SSL certificate messages. Should it be a straightforward O365 > G-suite migration or have Godaddy thrown a couple of spanners in the works to thwart the obvious methods?

I would recommend to backup the emails to PST and them import them to G-Suite. Before doing the backup of the PST change the MX records to G-suite and then backup to PST. Then import the PST to G-suite.

There's going to be a big gap between for the users seeing their old emails between the MX record swap and getting them imported though. Would much rather have it all ready and then do the MX record swap. Also, a couple of mailboxes are enormous. It's going to take days to do them that way. Besides, what's the point of those migration tools if they're not the most useful solution?

I've managed to get in now. Just had to ignore the fact it was Google and pretend it's a bog standard Office 365, but not use the automatic settings and select Exchange Web Services and put https://outlook.office365.com/EWS/Exchange.asmx in the URL field.

Now getting the ever so helpful "Error (Retrying)" error message when importing users emails. Some more clues as to WHY might be a bit more useful here Google.

Okay... I got Google on chat and they just asked me to delete the migration and start again. That got most of it working but several mailboxes occasionally got stuck retrying. Oh, and they told me hovering over the Error displays the error code so finally worked out what the errors might have been. Turns out they were internal Google errors "17008: Internal error. Try exiting and restarting the migration. " & "13001: Internal server error. Try exiting and restarting the migration. " errors.

So all is good. I've done the bulk of the migration and just waiting for permission to get the MX record swapped before doing a final sync.

Also, it seems the tool is more reliable if you import the users via csv rather than adding them manually. I found adding them individually too fast is possibly what caused the errors in the first place. It was fine if I added one, then waited until it got going and then did the next one. but if I whacked a load through really quickly, it would choke. No such problems with the CSV so I expect there's some sort of staggered situation going on when doing it that way. A survey of one here so it would be good if there was some confirmation of that here.

Google things you could do better...

Make it more obvious where the error messages can be found.

Create a migration tool that can import emails, contacts and calendars all at once from O365 instead of having to do them individually.

The Wizard style help isn't very good if you're trying to plan ahead for potential issues.

Compared to Office 365, your user management tools are pretty poor.

Set-up needs some warnings ahead of time to inform you that it will directly mess with your DNS records instead of informing you of what changes need to be made if you follow the set-up wizard. First time around I managed to have all the MX records automatically swapped to Google's MX records before I had even got as far as creating all the user accounts. Fortunately, I realised this after just a few minutes and spent the next 10mins frantically resetting all the DNS records back to the originals. Good job I recorded all the DNS settings before I started or that could have been messy. There needs to be a 'new setup'/migration fork in the instructions somewhere.

Anyway, aside from the avoidable gotchas, it wasn't too bad an experience.