Email Migration Advice:
-
@popester said in Email Migration Advice::
There are about 6000 emails that i would like to pull into our system. (pull into our system may not be the correct term).
You say you're going to import them into 'our system' - are you already on O365? If so, you don't need to setup a new account on O365 at all assuming you're moving those users from the smaller HVAC company into your own account.
-
@Dashrender said in Email Migration Advice::
@popester said in Email Migration Advice::
@Dashrender said in Email Migration Advice::
@popester said in Email Migration Advice::
@Dashrender said in Email Migration Advice::
There's more to do, but MS actually does a pretty good job of walking you through it from what I recall.
Question - why O365? why not stay there? or someone else?
Yes, I am reading up on it now, thank you.
Borg mentality here..... My rank doesn't yet allow me in on the platform decisions. Soon though... Soon.
you work for an MSP?
No, three man IT team at https://www.tempoair.com/
We all wear a lot of hats. I just don't have the one that says IT manager.oh, you're merging with another HVAC company (or maybe buying them out, etc)...
Exactly, the owner of the company worked for Tempo 30 years ago and decided to go out on his own. He decided to retire and didn't want to sell it so "for a nominal fee" we simply take over and pull his business and brand into ours. I have the phone carrier migration in the hopper already so this is what i have left. Getting email and domain in the correct/new location.
-
@Dashrender said in Email Migration Advice::
@popester said in Email Migration Advice::
There are about 6000 emails that i would like to pull into our system. (pull into our system may not be the correct term).
You say you're going to import them into 'our system' - are you already on O365? If so, you don't need to setup a new account on O365 at all assuming you're moving those users from the smaller HVAC company into your own account.
Yes, we are totally "assimilated" in office 365. And yes, we are taking over the domain and eventually moving it to our hosting service Bummer Hosting. I just need to suck out all the email history and deposit it in our O365 environment so the one employee we inherited can deal with any loose endings with billing and customer issues and emails.
-
@Dashrender said in Email Migration Advice::
This is super easy.
Create your O365 account, give it your domain name. MS will create a @domain.onmicrosoft.com account for you. You can then create the users in O365, assign licenses. Then you can use MS's import tool to suck in the email from the old system, you'll need the email addresses and passwords for the old system to do this.You don't even need licenses assigned to import email.
-
Here is what appears to be working.
Added newdomain.net to O365 accepted domains.
Added TXT record to godaddy.com dns record.
Created shared mailbox with newdomain.net in O365
Created Migration endpoint in O365
Created Migration batch on O365
Started batch.
Verified emails are populating shared mailbox. -
@popester said in Email Migration Advice::
Here is what appears to be working.
Added newdomain.net to O365 accepted domains.
Added TXT record to godaddy.com dns record.
Created shared mailbox with newdomain.net in O365
Created Migration endpoint in O365
Created Migration batch on O365
Started batch.
Verified emails are populating shared mailbox.See, not to hard at all. In your situation, I'm not sure adding the new domain was actually required. The migration should have just used the IMAP address to connect to the godaddy server, authenticate and suck in the mail.
-
Though adding the additional domain will allow you to continue to receive email at those old addresses, once you change the DNS records and create aliases of the old addresses somewhere.
-
@Dashrender said in Email Migration Advice::
@popester said in Email Migration Advice::
Here is what appears to be working.
Added newdomain.net to O365 accepted domains.
Added TXT record to godaddy.com dns record.
Created shared mailbox with newdomain.net in O365
Created Migration endpoint in O365
Created Migration batch on O365
Started batch.
Verified emails are populating shared mailbox.See, not to hard at all. In your situation, I'm not sure adding the new domain was actually required. The migration should have just used the IMAP address to connect to the godaddy server, authenticate and suck in the mail.
You have to have the email domain in O365 for it to import. It will not import something you don't "own".
-
@JaredBusch said in Email Migration Advice::
@Dashrender said in Email Migration Advice::
@popester said in Email Migration Advice::
Here is what appears to be working.
Added newdomain.net to O365 accepted domains.
Added TXT record to godaddy.com dns record.
Created shared mailbox with newdomain.net in O365
Created Migration endpoint in O365
Created Migration batch on O365
Started batch.
Verified emails are populating shared mailbox.See, not to hard at all. In your situation, I'm not sure adding the new domain was actually required. The migration should have just used the IMAP address to connect to the godaddy server, authenticate and suck in the mail.
You have to have the email domain in O365 for it to import. It will not import something you don't "own".
you tested this? How would they even know? the IMAP connection goes to the address you setup, not the MX record for the domain in question.
Now I want to test this with my gmail account importing all the shit into my O365 account.
-
-
@Dashrender said in Email Migration Advice::
the IMAP connection goes to the address you setup, not the MX record for the domain in question.
What does an MX record have to do with anything? I think you have no idea WTF you are are talking about.
