Migrate exchange from 2010 to 2016 or 2019

I am looking at migrating a very small network (6 users) from SBS 2011 to Exchange 2016 or 2019
Do I really want to go through the whole "migration" or can I simply export all mailboxes to .PST files and then import them into the new version of Exchange ?
JPD153Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rodney BarnhardtServer AdministratorCommented:
Based on the information I received at Microsoft Ignite, you cannot go to Exchange 2019 unless you have a volume license agreement. They are only issuing license keys to those customers since they feel those are the only ones large enough to justify keeping Exchange on premise. If you want to upgrade and stay on premise, you can only upgrade to 2016.

Also, if there are only six users, it may be easier to just have the email from 2010 to PST files and have new emails go to the 2016 server. There are a lot of settings to creating a hybrid environment to perform migrations.
JohnBusiness Consultant (Owner)Commented:
Also, we specialize in small business clients and all clients have outsourced email. At your level, this is cheaper and automatically keeps you up to date.  I recommend you outsource and Microsoft Office 365 is a good choice.
Seth SimmonsSr. Systems AdministratorCommented:
Do I really want to go through the whole "migration" or can I simply export all mailboxes to .PST files and then import them into the new version of Exchange ?

i'm dealing with this right now - moving from 2010 to 2019 though there is no direct upgrade path; need to go to 2016 first so it's a 2-step process.  however, only 6 users?  seems more trouble than it's worth (both in time and money)
as john said, host it

but, if you really want on-prem, export to pst files, remove exchange entirely, then install 2019 on a new server 2016 install.  just beware of the downtime.  again, more trouble than it's worth for such few users
Maximize Customer Retention with Superior Service

The IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more to help build customer satisfaction and retention.

JPD153Author Commented:
The 6 users system I am talking about is a test for more customers with 35 to 75 users. SO I really want to make sure I do the full migration
Jose Gabriel Ortega CastroEE Solution Guide/Topic Advisor and CEO Faru Bonon ITCommented:
Just one thing guys...
to go Exchange server 2019, you do need Windows Server 2019. so if you don't have it, just don't bother.
Coexistence mode between 2010 and 2019 doesn't exist.

1.png
I tried to do a video of doing that  (Installation of exchange 2019). and I failed big time...
So I had to do it using ws2019.
https://www.youtube.com/watch?v=EpGe6pUt6Xo

I'd recommend you to check this in detail because you just can't have a windows server 2019 and try to install exchange server 2019.
https://docs.microsoft.com/en-us/exchange/plan-and-deploy/system-requirements?view=exchserver-2019
JohnBusiness Consultant (Owner)Commented:
to go Exchange server 2019, you do need Windows Server 2019. so if you don't have it, just don't bother

(Deleted comment on further reading)

By the way, even for 75 employees, hosted Exchange makes economic sense.
Jose Gabriel Ortega CastroEE Solution Guide/Topic Advisor and CEO Faru Bonon ITCommented:
John I've tried to do it before... :) and I was live, so I can say for sure that is not possible to do it with 2016.
JohnBusiness Consultant (Owner)Commented:
Yes. I deleted my comment on further reading. Sorry about that.
Jose Gabriel Ortega CastroEE Solution Guide/Topic Advisor and CEO Faru Bonon ITCommented:
Np john!
JohnBusiness Consultant (Owner)Commented:
@JPD153  - You can see the issues unfolding. It is getting ever harder to justify on premises Exchange. The cost of software, hardware and support gets high in a big hurry.
Rodney BarnhardtServer AdministratorCommented:
I actually think MS is trying to force smaller companies to their services. As I first mentioned, they will not even provide a license key for Exchange 2019 unless you are a volume license customer. So, even if a company wanted to keep everything on premise, and I work for a larger company that does, the software vendors are making it harder to do unless you have some size to your company.
JohnBusiness Consultant (Owner)Commented:
You do not necessary have to use Microsoft Office 365 - there are other Hosted Exchange companies and my clients are using them. It is as much as anything a matter of economics in terms of the investment required for in-house Exchange.
Vidit BhardwajAdminCommented:
Migrating to 2016 or Exchange online would be best for you
Saif ShaikhServer engineer Commented:
If you are on exchange 2010, I think migrating to 2016 would be a best option. Exporting PST and importing it to a new mailbox in 2016 exchange is your decision. SBS exchange 2010 to 2019 no direct upgrade path. You need to migrate to 2016 first.

For Exchange 2019 read below comments.

Windows Server 2012 R2 is the minimum OS and AD for Exchange 2019, if Exchange RTMs before October 2018 when Windows 2012 R2 goes into extended support. If Exchange 2019 RTMs later, we may see the minimum requirements set to Windows Server 2016 instead.

For Windows domain 2012 R2 inplace upgrade to windows-server-2019 read below comments.

http://louistechviews.com/2018/04/10/in-place-upgrade-windows-server-2012-r2-to-windows-server-2019-preview-maybe/

For Windows domain controllers on 2016 inplace upgrade to windows-server-2019 read below comments.

https://www.starwindsoftware.com/blog/in-place-upgrade-domain-controllers-from-windows-server-2016-to-windows-server-2019

So since minimum requirement for OS and AD for exchange 2019 is Windows Server 2012 R2. I would say you will have to migrate your AD to the new Windows Server 2012 R2 first, then move all FSMO roles and feature from old existing AD and then you need to demote your 2012 domain controllers. So once you are on supported platform then you can install a new OS(Windows Server 2012 R2) on a new VM for exchange and then install exchange.


If your domain is already on Windows 2016 which is supported environment. Meaning your AD domain is in supported environment,  you can also install exchange 2019 on Windows 2019.

You can also do an inplace upgrade from windows 2016 to windows 2019.

For Windows domain controllers on 2016 inplace upgrade to windows-server-2019 read below comments.

https://www.starwindsoftware.com/blog/in-place-upgrade-domain-controllers-from-windows-server-2016-to-windows-server-2019
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.