6 Reasons Behind Exchange Server Migrations

6 Reasons Behind Exchange Server Migrations

May 23

Procrastination is that self-inflicted monkey wrench that slows us down in both life and business. It’s the reason we stick around with that dreadful web host another year – even though they’ve continually failed us with lackluster support. It’s why we’re still doing business via email when everyone else has gone social media marketing. Procrastination is keeping us in the Windows XP world even though it’s basically a ticking time bomb.

Even with procrastination looming in the shadows, there are just some tasks we can’t hold off. Here are a few reasons companies decide to move forward with an Exchange Server migration.

1. Product Support

Company A is using Exchange 2003 because it still works for them. But it’s only a matter of time before the lack of support and features catches up.

The 2003 versions of Exchange Server and Outlook joined Windows XP in Microsoft’s April 8, 2014 software slaughter. They’re no longer supported, so the security updates and technical other jazz that kept them fine-tuned are completely off the table. Some companies like to live on the edge with this kind of stuff. If you’re not so adventurous, you should at least be running Exchange 2007, which will be supported up until 2017. While we’re at it, check out this Microsoft end of life list to find out how long you’ve got on your other business products.

2. Seamless Mailbox Migration

A merger of companies takes place, so a lucky Exchange server administrator is tasked with having to move mailboxes between multiple Active Directory sites and forests.

Microsoft’s mailbox technology gets slicker with each version of Exchange. This alone is a reason to upgrade. Exhange Server 2013 simplifies migrations by allowing you to move mailboxes in big batches. The system sends progress reports via email and automatically retries to complete the migration when problems arise. It also provides some nice visibility into the process by allowing you to review your mailbox migration plans before executing the move.

3. Changes in Infrastructure Management

Company B is considering outsourcing Exchange management responsibilities while still using the system for their everyday communication needs.

Exchange 2010 and 2013 both offer the ability to run the server in the cloud. Exchange Online, the cloud equivalent to the latest server product, comes bundled with Office 365 and in its own standalone package as well. If Company B is worried about giving up too much control, they can create a hybrid system that allows them to deploy a couple of mailboxes in the cloud, and keep others locally.

4. Need for Better Availability and Reliability

Company C is fed up with their Exchange server crashing and chugging along when the network gets active.

Software is prone to performance issues the older it gets. Exchange 2007 may still be under extended support, but that doesn’t mean it’s going to be as smooth as an up to date version. Exchange 2013 has Managed Availability, a handy little feature that monitors the environment and performs a little surgery when needed. For example, if certain Exchange services fail, it will restart them. If it’s a critical fail, this feature will fire up load balancing and other technology to keep the system going without disrupting users.

5. Improved Device Support

Company D is going BYOD and needs an email system that provides seamless support for multiple devices.

If you want a platform that works with the latest phones, you need a system that was made to accommodate today’s mobile technology. Moving up to Exchange 13 will give Company D reliable support for all common devices. It’s the best compatibility you’re gonna get for the iPhones, Android devices, Macs, and Windows gadgets that need to place nice in the mailbox environment.

6. Compliance Concerns

Company E is concerned how the advancement of mobile devices and email impacts the compliance requirements of their industry.

The need to satisfy compliance standards is certainly compelling enough to trigger a migration. Exchange 2013 keeps compliance in mind with Data Loss Prevention (DLP) features that provide an easier way to manage the sensitive data contained in those communications. It also improves on the retention, archiving, and eDiscovery features introduced in Exchange 2010, which helps out when compliance audits demand that certain data be produced.

Every organization has an excuse behind why they’re not running the latest greatest business system. Ironically, those excuses often end up becoming the reasons for biting the bullet and making the move.

What forced you to pull the trigger on Exchange migration?

Also, if you’re an Exchange admin looking to make email migration super simple, take a look at StorageCraft Granular Recovery for Exchange.

Photo Credit: r. nial bradshaw via Flickr