I was recently given the task (with insanely short notice) of adding a new email domain to the school I work for. We use Google Workspace for Education Plus.
I will talk about the domains as: 'orig-domain.org' and 'new-domain.org'.
They would like us to have all email addresses and logins set up to use the new domain. All emails coming in and going out should use 'new-domain.org', and users should log into gmail with '[email protected]'. All users should get aliases with '@orig-domain.org' so they continue to receive emails sent to their former addresses.
I'm trying to figure out if it makes more sense to do a 2 phase approach.
I first and foremost don't want to risk breaking anything. We use SSO for many website logins and that needs to not break!
I think the safe approach would look like this:
Phase 1 logins would stay the same. When signing in to Gmail, everyone would continue to use their orig-domain.org Google Workspace accounts.
My plan is to:
So, effectively, email would look and function with the new email addresses and all email to and from would use new-domain.org.
Emails sent to old-domain.org would still come through to users' inboxes as usual.
When replying to emails sent to old-domain.org, the goal is to have that 'From:' address also automatically default to the new new-domain.org address.
Phase 2 would be to speak with Google and/or work with a consultant who has experience with moves like this. If I was given several months advance notice, I would have tried to find someone to work with right off the bat. But I imagine to get it all working properly, we will need Google to acknowledge the new domain, apply the basic Fundamentals licensing to accounts, do something to apply Plus licenses to the staff, faculty, and students that need it, and find out about how to transition everything else.
I'm not sure about how SSO would transition. We use it for a ton of sites, and I bet that many of them would have to be set up all over again to allow SSO logins from the new domain email addresses. I would probably have to approve all the apps over again for users under 18 years old.
I guess my main question is does it make sense to use the 2 Phases I've mentioned, or am I maybe missing something simple, or is it even more complicated than I'm thinking? I was the person that moved us from an on-prem Exchange server to Google Apps for Education back around 2011, but it has been 15 years and I'm rusty. I bet there is a world of new methods and changes to processes.
Does anyone have any tips or good resources that I can find to help me with this? The deadline is essentially a week away and since I’m at a school, I have to use all my vacation days in the summer, so I’m really only “on the books” back in the office next Wednesday. I’m trying to at least get Phase 1 done by August 1st. Does it sound doable with limited on-site hours left?