Five ways to ease into an Exchange 2013 migration

Planning a move to Exchange 2013 can be an overwhelming process, but preparation is the key to success. We can help.

If your enterprise is looking to move to Exchange Server 2013, there's a lot of prep work that needs to be done. Preparing for an Exchange 2013 migration can quickly become overwhelming.

We compiled expert resources to help admins prepare for an Exchange 2013 migration, including tips on what to consider before making the move, the value of a test lab, new features in Exchange 2013 and how to stop issues before they happen.

For more information on ways to prepare for an Exchange 2013 migration, check out our Exchange Server 2013 page and follow us on Twitter @ExchangeTT.

How to decide if Exchange 2013 is a good fit for your enterprise

As you weigh your options for an Exchange 2013 migration, look at how the migration will work in your enterprise. A number of factors -- including recent security breaches -- have made organizations shy away from a migration, but our expert gives three reasons why it makes sense to upgrade to Exchange 2013.

Exchange 2013 features that may make you want to upgrade

Microsoft included new features in Exchange 2013 that should improve integration with the company's own products, as well as with third-party tools. This means Exchange shops have feasible options for cloud-based and on-premises messaging, leaving shops to decide which option is best. This tip walks you through features to help in the decision process.

Working in a test lab before an Exchange 2013 migration

Before you migrate, use a test lab to get familiar with Exchange 2013. Test labs let you tinker with new features, sort out your software and hardware questions, and enable external and internal email. Plus, working in a lab can help you work on your qualifications for the MSCE: Messaging certification.

Design Exchange 2013 storage with mailbox database sizes in mind

How you design the architecture of the storage affects everything, including performance and reliability. Study Microsoft's recommendations and your options for mailbox database sizes. You should also consider factors such as DAGs, RAID configurations, provisioning disks and database replication.

Five gotchas when migrating to Exchange 2013

Exchange 2013 can be an intricate platform, so there are some specific factors to consider to ensure your Exchange 2013 migration is a success. Sizing and performance are things Exchange admins should keep an eye out for, as well as ambiguous namespaces. With the right information, the deployment becomes much easier.

This was last published in February 2014

Dig Deeper on Microsoft Exchange Server 2013

PRO+

Content

Find more PRO+ content and other member only offers, here.

Join the conversation

3 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

It would be great to see More Exchange Server 2013 Articles here, many companies will start the Exchange Server 2013 project once the SP1 is out, which will be in couple months.
Cancel
Hi searchexchange1,
Thanks for your suggestion! We have plans to include more Exchange Server 2013 content in the coming months, but please feel free to send us a quick email or comment on an article if you have any specific Exchange 2013 issues or questions you would like to be addressed.
Cancel
As we all know, Microsoft is going to end its support for Exchange 2003 next month, so there will be no updates, bug fixes etc for the Exchange 2003.So, users would have to rely on already published articles on the third party sites and on various other third party communities. So because of this end of support, majority of the organizations that are using Exchange 2003 are planning to migrate from exchange 2003 to 2013. But Microsoft has not introduced a direct migration path from 2003 to 2013. To perform migration, you need to first export your mailboxes to PST files from Exchange 2003 using Exmerge and then import those PST files into Exchange 2007 and then you need to export PST files from Exchange 2007 by running New-MailboxExportRequest CMDLET and import those PST files into Exchange 2013.

Migrating to EXchange 2013 is a good option for the companies who are planning to migrate directly to 2013 as Exchange 2013 offers more set of new and useful features which its predecessors don't.
Cancel

-ADS BY GOOGLE

SearchWindowsServer

SearchEnterpriseDesktop

SearchCloudComputing

SearchSQLServer

Close