Hybrid migration Exch 2010 to Exch Online still possible ?

%3CLINGO-SUB%20id%3D%22lingo-sub-2509776%22%20slang%3D%22en-US%22%3EHybrid%20migration%20Exch%202010%20to%20Exch%20Online%20still%20possible%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2509776%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%2C%3C%2FP%3E%3CP%3EExchange%202010%20being%20out%20of%20support%20is%20it%20still%20possible%20to%20migrate%20to%20Exchange%20Onine%20through%20the%20hybrid%20method%20%3F%20Do%20the%20Hybrid%20configuration%20Wizard%20still%20work%20%3F%20We%20have%20customers%20that%20are%20still%20with%20Exchange%202010%20and%20intend%20to%20migrate%20to%20Exchange%20Online.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2509776%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2511399%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20migration%20Exch%202010%20to%20Exch%20Online%20still%20possible%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2511399%22%20slang%3D%22en-US%22%3E%3CP%3EHey%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F737602%22%20target%3D%22_blank%22%3E%40Lohenthal%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBeing%20out%20of%20support%20usually%20means%20that%20you%20will%20no%20longer%20receive%20updates%20on%20your%20legacy%20software.%20You%20will%20not%20be%20able%20to%20call%20MS%20for%20help%20and%20MS%20would%20no%20longer%20release%26nbsp%3B%3CSPAN%3ESecurity%20fixes%20for%20vulnerabilities%20for%20your%20software.%20While%20it%20is%20still%20possible%20to%20setup%20hybrid%20from%20an%20updated%20exchange%202010%20box%20%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fenterprise%2Fexchange-2010-end-of-support%3Fview%3Do365-worldwide%23%3A~%3Atext%3DExchange%2520Server%25202010%2520reached%2520its%2Cthe%2520time%2520to%2520start%2520planning%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fenterprise%2Fexchange-2010-end-of-support%3Fview%3Do365-worldwide%23%3A~%3Atext%3DExchange%2520Server%25202010%2520reached%2520its%2Cthe%2520time%2520to%2520start%2520planning%3C%2FA%3E.%3C%2FP%3E%3CP%3EIf%20you%20read%20between%20the%20lines%20Microsoft%20carefully%20emphasizes%20on%20the%20state%20your%20servers%20were%20in%20as%20of%26nbsp%3B%3CSPAN%3EOctober%2013%2C%202020%20before%20deciding%20to%20continue%20with%20hybrid.%20On%20some%20outdated%20boxes%20setting%20up%20hybrid%20might%20not%20be%20a%20good%20idea%3B%20third%20party%20tools%20like%20migrationwiz%20etc%20may%20be%20a%20better%20choice%20for%20those%20servers.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello all,

Exchange 2010 being out of support is it still possible to migrate to Exchange Onine through the hybrid method ? Do the Hybrid configuration Wizard still work ? We have customers that are still with Exchange 2010 and intend to migrate to Exchange Online.

 

Thanks

2 Replies

Hey @Lohenthal 

 

Being out of support usually means that you will no longer receive updates on your legacy software. You will not be able to call MS for help and MS would no longer release Security fixes for vulnerabilities for your software. While it is still possible to setup hybrid from an updated exchange 2010 box :

https://docs.microsoft.com/en-us/microsoft-365/enterprise/exchange-2010-end-of-support?view=o365-wor....

If you read between the lines Microsoft carefully emphasizes on the state your servers were in as of October 13, 2020 before deciding to continue with hybrid. On some outdated boxes setting up hybrid might not be a good idea; third party tools like migrationwiz etc may be a better choice for those servers.

 

Thanks

Your best move is likely to install a minimal Exchange 2016 footprint and use that for the migration. This is a loaded topic so I won't elaborate much, other than to say that you can do this (introduce 2016) in a way that users will be impacted by the change, or in a way that users won't be impacted. The latter is pretty commonly done, the former (the official/proper way) is also done, just less often.

In either case, knowing Exchange client access (URLs, FQDNs, Autodiscover, etc.) is key to controlling what impact is had by introducing Exchange 2016 into the organization.