How to move a couple emails to office365

kwest

Well-Known Member
Reaction score
540
i have a client that is a CEO of a very large company and he is always complaining about his email syncing and not working right. I would like to love just him to office365 if that is possible.

Has anyone tried this?

Thanks in advance for your help.
 
i have a client that is a CEO of a very large company and he is always complaining about his email syncing and not working right. I would like to love just him to office365 if that is possible.

Has anyone tried this?

Thanks in advance for your help.
Ok that is clear as mud. What is he using for email now? Is it his own domain?
 
Sorry if it is not clear.

His company has a domain with lots of users. Let's say company.com

Is it possible to move just one email off of that to office365 exchange.

Everyone is on google IMAP user@company.com

I want to move ceo@company.com only to exchange.
 
No. There is no way to do that and keep the domain name. You can move the entire domain to a different provider, like for example Rackspace, and have email and exchange level users. You can mix and match email types in that environment. You can't have two different providers using the same email domain.
 
You cannot move just one email address to a totally different server. But what you can do is setup a second MX record to another server. So if their existing email is exchange.company.com you could setup the second one at O365 as mail.company.com. Then setup forwarding in the first server. But that could be rather messy.
 
Everytime I've tried that
You cannot move just one email address to a totally different server. But what you can do is setup a second MX record to another server. So if their existing email is exchange.company.com you could setup the second one at O365 as mail.company.com. Then setup forwarding in the first server. But that could be rather messy.
That's what his link describes above. It could work but it might get outgoing email tagged higher as spam. And it could be slow depending on how fast google is at forwarding email.
 
i have a client that is a CEO of a very large company

If he is a CEO of a very large company, then he himself should know the difference between home grade products, and business grade products. Just tell him that he needs a true business grade solution, and it will cost him $X per month.

In this case, you have to jump in with both feet. ALL email accounts have to be moved, as said by @nlinecomputers and @markverhyden

Andy
 
Have the investigated why google email isn't syncing correctly? Google Apps is a solid platform and shouldn't have syncing issues.

Now, a small trick we played with a company that wanted to avoid the migration to a new hosting environment and wanted Exchange mail for only a small handful of people was to setup a new domain that is very similar to the original domain. We made it different enough that it won't confuse people, but it is still readily accepted by all parties. The original was tomsplumbing.com and the new was tomsplumbingservice.com.

Then we just linked the tomsplumbingservice.com to Exchange.... low cost, low implementation fees, and it works 100%.
 
You CAN do some hybrid setups.....both with Office 365 and also an on-prem Exchange server....or between O365 and some other mail hosts.

https://community.office365.com/en-us/w/exchange/simple-domain-sharing-for-smtp-email-addresses

I know RackSpace supports hybrid setups if you have them host both.....my colleague has done some hybrid setups 'tween on-prem Exchange and o365...and not long ago he did a hybrid setup for a real estate agent....the broker has an O365 account and the rest of her office/agents have regular POP/IMAP accounts with their website hosting company. In this hybrid setup where the rest of the office is on some POP/IMAP host...leave the CEO's mailbox there but with a forwarding rule. Forward to the default O365 mailbox address, like ceo@hisocompany.onmicrosoft.com
In the O365...you'll add the recipient policy for the company domain, and set it for his default e-mail address. But leave the login address as the onmicrosoft.com one (doesn't really matter but that's what I did).
Add the Microsoft servers to the SPF record so e-mail from the CEO originating from Microsoft is allowed by spam filters.
 
Last edited:
Another option for a hybrid setup is to use an email spam filter service that allows for delivery to different locations based on the email address.

All email for the domain is sent to the service as normal, and it then scrubs the email and delivers it based on the set rules you specify.
 
I know rackspace allows "split domain" emails. I have one setup where majority of emails are on rackspace email service (pop, imap not exchange). Then at the business on-prem is an exchange server with a handful of email addresses for same domain there. Basically rackspace receives all incoming email for domain.com. if there's not a user setup, the email will be forwarded to the onsite exchange server. Works pretty slick! No need to have 2 different domain names.

Not sure if google allows this but worth a check.
 
I know rackspace allows "split domain" emails. I have one setup where majority of emails are on rackspace email service (pop, imap not exchange). Then at the business on-prem is an exchange server with a handful of email addresses for same domain there. Basically rackspace receives all incoming email for domain.com. if there's not a user setup, the email will be forwarded to the onsite exchange server. Works pretty slick! No need to have 2 different domain names.

Not sure if google allows this but worth a check.

I'm curious as to how the SMTP part is handled on the exchange server. Does it point to the rackspace SMTP? And how is the forwarding handled?
 
I have it setup with 2 send connectors. 1st connector send to rackspace relay. Through scoping this contains the company email domain so company emails essentially get looped back through rackspace for any not already in exchange. (I believe if exchange recognizes one of it's own in the TO field, it will just send internally first w/o hitting send connectors).

For 2nd send connector I just have the cost higher and * for scoping as a regular exchange setup.

The nice thing about this setup for outgoing emails is if the exchange server gets blacklisted for any reason, or problems sending to certain domains, I can just push it through rackspace smtp server through the use of scoping.
 
Back
Top