Migrate Exchange Server 2013 to Exchange Server 2019 in a SBS migration scenario By Mariette Knap SBS 2008 end of life, migration guide for SBS 2008, Exchange Server 2013, Exchange Server 2019, sbs 2008 migration kit In this guide, we come from a migration of (SBS 2008) Exchange Server 2007 to Exchange Server 2013 and now we will migrate the Exchange Server 2013 to the latest version, Exchange Server 2019. This is called a double hop migration. At this point, we will introduce a new Windows Server 2019 that will be joined to the numinous.local domain as a member server. On this server, we will install Exchange Server 2019 and continue the migration of Exchange data from the Exchange Server 2013 on the Windows Server 2012R2. I assume that the SBS 2008 (in the case of a migration from SBS 2008 to Windows Server 2016/2019) is no longer active in your domain. You must have completed How to migrate SBS 2008 to Windows Server 2019 Standard, Datacenter or Essentials and Migrate Exchange Server 2007 from SBS 2008 to a new Exchange Server 2013 on Windows Server 2012 R2 or if you have already migrated to Exchange Server 2016 please use Migrate Exchange Server 2016 to Exchange Server 2019 in a SBS migration scenario This migration project cannot be completed if any Domain Controller in your network has a Functional lower than Windows Server 2012 R2 and that means that the SBS 2008 has to be demoted and decommissioned. This migration project cannot be completed if any Exchange Server 2007 or 2010 is still in your Active Directory. If you migrated from Exchange Server 2007 to 2010 or 2013 and you did not uninstall the old Exchange Server 2007 or 2010 possible leftovers in your AD can block a successful installation of Exchange Server 2019. Both Exchange servers in this project can upstream and downstream proxy for connections but it is the best practice that you connect to the highest version available. This way both Exchange Servers will coexist in the network. You can migrate mailboxes in batches. An Outlook client will connect to the highest version Exchange Server in our network, in our case the Exchange Server 2019, and if the mailbox for that user has not been migrated to the new server it will proxy the request. Before you begin! At the bottom of this guide, you find a script that you need to download and extract to c:\scripts on your new Exchange Server 2019. Read this guide before you implement it and make notes of possible questions you have. You can rely on our expertise! Easy migration guides Technician migration kits Easy to use migration guide Migration guide for migrating from one source (for example SBS 2008) to a new Windows Server environment built on the latest technology. This guide is ideal if you want to perform the migration of your old server yourself. The guide contains everything to ultimately run your infrastructure on more modern operating systems like Windows Server 2016/2019, Exchange Server 2016/2019 or Office 365. Success guaranteed! SBS 2008 migration guide Technician migration kits Technician kits are designed for professionals who need to carry out migration projects to Windows Server 2022 or 2025. This migration tutorial is part of the Windows Server 2022 and 2025 Technician migration kits. These utilize a Windows Server 2022 or 2025 Hyper-V host that supports multiple machines for the process. Additionally, the technician migration kits include all the 'Easy migration kits,' which allow us to maintain the same host name for the destination server. Get your Technician migration kit All our Easy Migration Kits and Technician Migration Kits come with exceptional support. In our store, you have the option to include support with your initial purchase or access it as needed by submitting a support ticket here. Prefer a hands-off approach? Our consulting services offer comprehensive migration support—just reach out to us to get started..