Migration from Hosted Exchange 2010 to Office365

%3CLINGO-SUB%20id%3D%22lingo-sub-2019593%22%20slang%3D%22en-US%22%3EMigration%20from%20Hosted%20Exchange%202010%20to%20Office365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2019593%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehopefully%20I%20can%20get%20some%20ideas%20for%20a%20migration%20of%20a%20customer%20with%20250%20email%20accounts%20by%20the%20end%20of%20january.%20We%20are%20a%20small%20MSP%20provider%20and%20the%20idea%20is%20to%20migrate%20from%20a%20Hosted%20Exchange%202010%20server%20(we%20do%20not%20have%20any%20admin%20rights%20so%20migration%20tools%20will%20be%20really%20difficult)%20to%20Office%20365%20and%20Cisco%20Email%20Security%20Cloud%20Version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERight%20now%20all%20users%20connect%20with%20their%20email%20information%2C%20so%20the%20dont%20use%20their%20domain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20weeks%20ago%20we%20did%20some%20testing%20(also%20with%20smaller%20clients%20with%20the%20same%20environment)%20and%20we%20had%20a%20pretty%20good%20concept%20that%20worked%20just%20fine%20but%20after%20testing%20last%20week%20it%20is%20not%20possible%20anymore%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.Changed%20actual%20email%20configuration%20on%20the%20HostedExchange%20from%20%3CA%20href%3D%22mailto%3Atest%40abcd.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Etest%40abcd.com%3C%2FA%3E%26nbsp%3Bto%20%3CA%20href%3D%22mailto%3Atest%40abcd.my-hosted-exchange.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Etest%40abcd.my-hosted-exchange.com%3C%2FA%3E%26nbsp%3B-%20same%20credentials%20to%20login%3C%2FP%3E%3CP%3E2.%20Created%20the%20O365%20User%20and%20changed%20the%20domain%20parameters%20(autodiscover%2C%20etc.)%3C%2FP%3E%3CP%3E3.%20In%20the%20same%20Outlook%20profile%20we%20attached%20a%20new%20email%20and%20with%20the%20new%20autodiscover%20it%20was%20really%20easy%20and%20fast%20to%20integrate%20the%20new%20email%20to%20the%20existing%20profile.%20So%20by%20that%20we%20would%20have%20all%20the%20old%20Outlook%20configuration%20and%20the%20user%20would%20have%20access%20at%20the%20same%20time%20to%20his%20old%20email%20(he%20would%20receive%20new%20information%20but%20could%20check%20and%20import%20importante%20information).%20Basically%20the%20most%20important%20thing%20was%20that%20Outlook%20seemed%20the%20same%20for%20the%20user%20and%20so%20he%20would%20have%20auto%20completation%20while%20creating%20new%20emails%2C%20etc.%20Some%20user%20we%20would%20also%20import%20the%20old%20PST%20file%20to%20have%20almost%20all%20data%20from%20the%20HosetdExchange%20email.%3C%2FP%3E%3CP%3E4.%20After%20one%20months%20we%20would%20delete%20the%20old%20HostedExchange%20Email%20and%20the%20user%20only%20would%20have%20to%20delete%20it%20in%20his%20Outlook.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProblem%20now%20is%20that%20we%20were%20testing%20the%20same%20and%20now%20Outlook%20doesnt%20let%20us%20create%20the%20new%20O365%20Email%20and%20we%20get%20a%20message%20that%20the%20email%20%3CA%20href%3D%22mailto%3Atest%40abcd.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Etest%40abcd.com%3C%2FA%3E%26nbsp%3Balready%20exists%2C%20even%20though%20we%20changed%20to%20teh%20O365%20and%20alkl%20domain%20issues.%20It%20is%20like%20the%20old%20name%20is%20%22cached%22%20and%20so%20we%20cannot%20process%20the%20same%20way.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20good%20ideas%20how%20we%20can%20perform%20this%20change%20the%20best%20way%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20input!%3C%2FP%3E%3CP%3ERoland%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2019593%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2020873%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20from%20Hosted%20Exchange%202010%20to%20Office365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2020873%22%20slang%3D%22en-US%22%3E%3CP%3EBest%20use%20the%20default%26nbsp%3B%40tenant.onmicrosoft.com%20address%20you%20are%20given%20when%20you%20create%20a%20mailbox%20in%20O365.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hello,

 

hopefully I can get some ideas for a migration of a customer with 250 email accounts by the end of january. We are a small MSP provider and the idea is to migrate from a Hosted Exchange 2010 server (we do not have any admin rights so migration tools will be really difficult) to Office 365 and Cisco Email Security Cloud Version.

 

Right now all users connect with their email information, so the dont use their domain.

 

Some weeks ago we did some testing (also with smaller clients with the same environment) and we had a pretty good concept that worked just fine but after testing last week it is not possible anymore:

 

1.Changed actual email configuration on the HostedExchange from test@abcd.com to test@abcd.my-hosted-exchange.com - same credentials to login

2. Created the O365 User and changed the domain parameters (autodiscover, etc.)

3. In the same Outlook profile we attached a new email and with the new autodiscover it was really easy and fast to integrate the new email to the existing profile. So by that we would have all the old Outlook configuration and the user would have access at the same time to his old email (he would receive new information but could check and import importante information). Basically the most important thing was that Outlook seemed the same for the user and so he would have auto completation while creating new emails, etc. Some user we would also import the old PST file to have almost all data from the HosetdExchange email.

4. After one months we would delete the old HostedExchange Email and the user only would have to delete it in his Outlook.

 

Problem now is that we were testing the same and now Outlook doesnt let us create the new O365 Email and we get a message that the email test@abcd.com already exists, even though we changed to teh O365 and alkl domain issues. It is like the old name is "cached" and so we cannot process the same way.

 

Any good ideas how we can perform this change the best way?

 

Thanks for your input!

Roland

1 Reply

Best use the default @tenant.onmicrosoft.com address you are given when you create a mailbox in O365.