Our team of highly experienced Microsoft engineers can perform several different types of Email Migration. And we embed this within our Email Consultancy services. This is perfect for existing businesses that wish to move to Office 365 technology. Or for those who want to migrate to later versions of Exchange. As well as businesses migrating from Office 365 to on-premise.
Email Migration from an On-premise Mail Server to Office 365 (Exchange Online)
To migrate from an On-premise mail server, typically a Microsoft Exchange Server is the most common type of migration we perform. And to achieve this, one of our consultants will review your current infrastructure. This way we can establish the best method of migration.
We’ll establish the best method to perform the migration and we’ll base this upon the complexity as well as several other factors. Which include the quantity of mailboxes and mail enabled objects being migrated. And whether there are public folders, multiple databases, DAG, and Domains being used as well as the mail server architecture. Our Consultants will also provide you with some feedback on your current configuration. As well as possible improvements and suggestions.
Email Migration from on-premise Mail Server to a new Database/Failover
The request to perform an email migration from an on-premise mail server to new databases is generally triggered as a result of recommendation. Or because of an outage or disaster.
It is good practice for businesses, when using an on-premise mail server, to use more than one Database. This is for the benefit of not only evening the load but also because you can use it for Resiliency failover.
Email Migration from on-premise Mail Server and upgrading to a newer version of the Mail Server
If you’re running an old version of Exchange for your Emails and you want to upgrade straight to the latest version Exchange 2019. Or if you just want to upgrade from an older version to a newer version, 2013 to 2016 for example. Then this is something that our Email Migration team here at Proxar IT Consulting can perform.
Below is a table showing direct upgrades and coexistence:
|Mail Server Currently running||Upgrade / Migrate to:|
|Exchange 2019||Exchange 2016||Exchange 2013||Exchange 2010||Exchange 2007||Exchange 2003|
Migrating from Office 365 (Exchange Online) to a new Office 365 Tenant (Exchange Online)
There are many reasons why you might want to migrate email from one Office 365 Tenant to another. This might be due to a merger or a split, or a change of company name for example. And when it comes to migrating, our email Migration team can schedule, project manage and perform the migration. They provide excellent comms, timelines and downtime. And they’ll work with you at a convenient time for your business. Our team can also provide consulting and advice on how to achieve this.
Migrating from Exchange Online to On-premise Exchange Server
When you use Exchange Online, you may have found that some of the features of on-premise Exchange are no longer available. Therefore you may have decided to move back to an on-premise environment.
At Proxar IT Consulting, we can perform an Exchange Online to on-premise Email Migration. This includes setting up the on-premise Exchange Server should you have previously decommissioned, or never had one. Our email migration team have many years of experience with all the different versions of Microsoft Exchange.
Support information for Microsoft Exchange Server:
|Still Supported by Microsoft||Version||Release date||Mainstream Support until||Extended Support Until|
|Yes||Microsoft Exchange Server 2019||Oct 22, 2018||Jan 09, 2024||Oct 14, 2025|
|Yes||Microsoft Exchange Server 2016||Oct 01, 2015||Oct 13, 2020||Oct 14, 2025|
|Yes||Microsoft Exchange Server 2013 SP1||Feb 25, 2014||Apr 10, 2018||Apr 11, 2023|
|Yes||Microsoft Exchange Server 2013||Jan 09, 2013||Apr 10, 2018||Apr 11, 2023|
|Yes||Microsoft Exchange Server 2010 SP3||Feb 12, 2013||Jan 13, 2015||Oct 13, 2020|
|No||Microsoft Exchange Server 2010||Nov 09, 2009||Oct 11, 2011||Replaced by CU|
|No||Microsoft Exchange Server 2007 SP3||Jun 07, 2010||Apr 10, 2012||Apr 11, 2017|
|No||Microsoft Exchange Server 2007||Mar 08, 2007||Jan 13, 2009||Replaced by CU|
|No||Microsoft Exchange Server 2003 SP2||Oct 19, 2005||Apr 14, 2009||Apr 08, 2014|
|Exchange 2019||Exchange 2016||Exchange 2013||Exchange 2010|
|CU3||September 17, 2019||15.2.464.5||CU14||September 17, 2019||15.1.1847.3||CU23||June 18, 2019||15.0.1497.2||Update Rollup 29||July 9, 2019||14.3.468.0|
|CU2||June 18, 2019||15.2.397.3||CU13||June 18, 2019||15.1.1779.2||CU22||February 12, 2019||15.0.1473.3||Update Rollup 28||June 7, 2019||14.3.461.1|
|CU1||February 12, 2019||15.2.330.5||CU12||February 12, 2019||15.1.1713.5||CU21||June 19, 2018||15.0.1395.4||Update Rollup 27||April 9, 2019||14.3.452.0|
|CU11||October 16, 2018||15.1.1591.10||CU20||March 20, 2018||15.0.1367.3||Update Rollup 26||February 12, 2019||14.3.442.0|
|CU10||June 19, 2018||15.1.1531.3||CU19||December 19, 2017||15.0.1365.1||Update Rollup 25||January 8, 2019||14.3.435.0|
|CU9||March 20, 2018||15.1.1466.3||CU18||September 19, 2017||15.0.1347.2||Update Rollup 24||September 5, 2018||14.3.419.0|
|CU8||December 19, 2017||15.1.1415.2||CU17||June 27, 2017||15.0.1320.4||Update Rollup 23||August 13, 2018||14.3.417.1|
|CU7||September 19, 2017||15.1.1261.35||CU16||March 21, 2017||15.0.1293.2||Update Rollup 22||June 19, 2018||14.3.411.0|
|CU6||June 27, 2017||15.1.1034.26||CU15||December 13, 2016||15.0.1263.5||Update Rollup 21||May 7, 2018||14.3.399.2|
|CU5||March 21, 2017||15.1.845.34||CU14||September 20, 2016||15.0.1236.3||Update Rollup 20||March 5, 2018||14.3.389.1|
|CU4||December 13, 2016||15.1.669.32||CU13||June 21, 2016||15.0.1210.3||Update Rollup 19||December 19, 2017||14.3.382.0|
|CU3||September 20, 2016||15.1.544.27||CU12||March 15, 2016||15.0.1178.4||Update Rollup 18||July 11, 2017||14.3.361.1|
|CU2||June 21, 2016||15.1.466.34||CU11||December 15, 2015||15.0.1156.6||Update Rollup 17||March 21, 2017||14.3.352.0|
|CU1||March 15, 2016||15.1.396.30||CU10||September 15, 2015||15.0.1130.7||Update Rollup 16||December 13, 2016||14.3.336.0|
|CU9||June 17, 2015||15.0.1104.5||Update Rollup 15||September 20, 2016||14.3.319.2|
|CU8||March 17, 2015||15.0.1076.9||Update Rollup 14||June 21, 2016||14.3.301.0|
|CU7||December 9, 2014||15.0.1044.25||Update Rollup 13||March 15, 2016||14.3.294.0|
|CU6||August 26, 2014||15.0.995.29||Update Rollup 12||December 15, 2015||14.3.279.2|
|CU5||May 27, 2014||15.0.913.22||Update Rollup 11||September 15, 2015||14.3.266.2|
|SP1||February 25, 2014||15.0.847.32||Update Rollup 10||June 17, 2015||188.8.131.52|
|CU3||November 25, 2013||15.0.775.38||Update Rollup 9||March 17, 2015||184.108.40.206|
|CU2||July 9, 2013||15.0.712.24||Update Rollup 8 v2||December 12, 2014||220.127.116.11|
|CU1||April 2, 2013||15.0.620.29||Update Rollup 8 v1||December 9, 2014||18.104.22.168|
|Update Rollup 7||August 26, 2014||22.214.171.124|
|Update Rollup 6||May 27, 2014||126.96.36.199|
|Update Rollup 5||February 24, 2014||188.8.131.52|
|Update Rollup 4||December 9, 2013||184.108.40.206|
|Update Rollup 3||November 25, 2013||220.127.116.11|
|Update Rollup 2||August 8, 2013||18.104.22.168|
|Update Rollup 1||May 29, 2013||22.214.171.124|
|SP3||February 12, 2013||126.96.36.199|
For more information, please contact us