In general, Exchange Server Migration is somewhat tedious and challenging. The reason being, it is complicated and demands experts’ surveillance. However, using several methods, you can make this considerably tricky task a bit easier. To do so, you have to follow a systematic guide of process steps.
Depending on the setup of an individual, Exchange Server migration takes place. Migration process typically follows a particular set of necessary procedures along with pre-requisites. Read this blog to learn about the Comprehensive End-to -End Migration Guide.
The Exchange Server Migration from 2010 to 2013 Process is sub-divided into three main phases.
The Three Main Phases are as follows:
This section contains the critical information that is required for successful deployment process. It includes segments such as Setup and deployment, Mailbox, Public Folders, Mail Flow, Exchange Management Shell, Client connectivity, and Exchange 2010 coexistence.
The second phase guides users about the Exchange Server Migration from 2010 to 2013 along with co-existence establishment without disrupting the existing services.
The third and last phase is all about the migration. It includes migration of mail flow, public folders, clients, mailboxes, etc. Best-recommended software to move mailboxes from one Exchange Server to another: EDB to PST Converter.
Checklist for Exchange Migration
1. Get acquainted with the release notes.
This section includes the critical information that is required for a successful deployment process. It contains segments such as Setup and deployment, Mailbox, Public folders, Mail flow, Exchange Management Shell, Client connectivity, and Exchange 2010 coexistence.
2. Authenticates the requirements of the system
This section acquaints you with the obligation of the Exchange 2013/ 2010 for Exchange data recovery that is must to be grabbed before installation. It includes information about hardware, clients, software, Operating system, or Network needs. Adding more, it also guides you about the supported coexistence scenarios.
3. Check and ensures whether prerequisite steps are done
This section entails you about the installation of necessary requirements for the Microsoft Exchange Mailbox, Edge Transport Server, and Client Access roles. These installation steps are for prerequisites Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2012 along with Service Pack 1 (SP1) Operating System.
It also offers details about the prerequisites needed for the installation of the Exchange management tools on Windows 8.1, 8, and 7 client systems. Further, it also guides you about the Deployment security checklist. This list ensures whether Exchange objects ACL rights are minimized, Administrative permissions are in-sync with the modification requirement or whether each internal default message paths are encrypted.
4. Ensures configuration of the disjoint namespace
This section briefs you how you can configure the Domain Name System (DNS) suffix search list using use the Group Policy Management console. The DNS suffix search list is needed to add multiple DNS suffixes.
5. For all Exchange 2007 mailbox databases, choose an offline address book
This section briefs you how you can use the Exchange Management Shell or the Exchange Management Console for provisioning the offline address book (OAB) downloads recipients. There are three ways to identify which recipient uses which OABs.
[accordion-item title=”+ These methods are required when an individual uses multiple OAB in the organization.“] i. Per-Mailbox Database
For this, you need to access the Exchange Management Shell or Exchange Management Console. It will specify you about the public folder database and the OAB being download by the recipients. ii. Per-Recipient
For this, you need to use Set-Mailbox cmdlet within the Exchange Management Shell. At this level, you cannot specify public folder database but can state which recipients will download. iii. Per Multiple Recipients
For this, you need to use pipeline command in the Exchange Management Shell. At this level, you can define some OAB recipients for downloading a particular OAB on the basis of the mutual attributes.
6. Generate the legacy Exchange hostname
This section guides how you can create and check legacy domain name system (DNS) host name. It is necessary to ensure that legacy Exchange 2007 and Exchange 2010/2013 coexist. Client Access servers and Autodiscover use this hostname while redirecting legacy users to the servers.
7. Exchange 2013/2010 Installation
This section guides how you can use Microsoft Exchange Server 2013/2010 Setup Wizard for Exchange 2013/2010 Mailbox and Client Access roles and Edge Transport role installation. Further, it also guides how you can verify the installation of Microsoft Exchange Server Migration from 2010 to 2013. For this, the recommended way is run the Get-ExchangeServer cmdlet and review the setup log file.
8. Prepare an Exchange 2013/2010 mailbox
In an Exchange organization, Mailboxes are considered as a most common recipient type for the information workers. Every mailbox has an Active Directory user account associated along with it. These mailboxes are used to send and receive messages and to salvage tasks, appointments, documents, tasks, messages, notes, etc. You can easily create the mailbox using Shell or EAC.
9. Ensure the configuration of Exchange-related virtual directories
This section briefs how to ensure the Exchange-related virtual directories configuration. Irrespective of the fact that Exchange 2013 Client Access server does not tackle with client protocols processing, still certain settings need to be applied to the Client Access server. These setting are for certificates and virtual directory.
10. Ensure configuration of Exchange 2007 as well as 2010/2013 certificates
This section outlines an overview of Digital Certification. It also provides details about different types of certificates, which certificates to choose, Proxying, and Digital certificate best practices.
Generally, in Exchange, SSL is designed to create secure communication between a server and client. The reason being, clients use computers as well as smartphones inside an organization and computer outside an organization. Therefore, when we install Exchange 2013, the client communication are auto-encrypted.
11. Ensure configuration of Edge Transport server
This section guides how you can create Internet mail flow using a subscribed Edge Transport server.
To establish Internet mail using an Edge Transport server, an individual needs to subscribe for the Edge Transport server to an Active Directory site. On subscription, it auto generates the much-needed twin Send connectors for Internet mail flow.
These Configured Send Connectors are as follows:
• One Send Connector is to direct the outbound email to all Internet domains
• Another Send Connector is to direct Edge Transport server Inbound Email to the Exchange 2010/2013 Mailbox server
Prior to beginning with the configuration process, you need to perform the following:
• Assign Permissions
• Authoritative domains, as well as email address policies, for Exchange organization are configured
• Enable Secure LDAP Port 50636/TCP
12. Ensure configuration of Unified Messaging
To successfully deploy UM, there are certain factors that you should consider. These factors are the different components, features, and elements of Unified Messaging. These factors help in planning appropriate Unified Messaging infrastructure as well as deployment. It is the most basic-yet-vital step that helps in UM deployment.
It helps you in planning your Voicemail System, UM Deployment, and establishing a connection with the telephony network. To proceed with deployment, you need to be aware of UM IP gateways, UM hunt groups, UM mailbox policies, Voice mail for users, UM services, UM dial plans, auto answer & route incoming calls.
13. Enable and ensure configuration of Outlook Anywhere
This section guides the user about Outlook Anywhere and its benefits. In the Exchange Server, it is also defined as RPC over HTTP. The main feature of this attribute is that it allows Microsoft Outlook 2013, 2010, or 2007 clients establish a connection with their particular Exchange Server even over the Internet and from outside the Corporate Network. It will entail you about Outlook Anywhere management, coexistence, and testing of connectivity.
14. Ensure configuration of service connection point
Undoubtedly, the Client Access server in Exchange 2013/2010 does not take responsibility for the customer protocols processing, but still, certain settings are being employed to the Client Access server. These settings are the certificate settings and virtual directory settings.
15. Ensure configuration of Exchange 2007 URLs
This section talks about the systematic configuration as well as testing guidelines of the Exchange 2007 external URLs. Usually, when we connect Exchange 2007 mailbox user to Exchange 2013 Client Access server, it redirects the connection to Exchange 2007 Server. For this redirection, the Exchange 2013 server is using external hostname configured on Offline Address Book, Outlook Web Access, and Unified Messaging virtual directories, Exchange Web Services, the internal hostname for the Exchange ActiveSync virtual directory, and Exchange ActiveSync of Exchange 2007 server.
The main point to be considered here is that in the Exchange 2007 server, internal as well as external host names are different from the Exchange 2013/2010 server hostnames. Further, they are pointed to the Exchange 2007 server.
16. Ensure configuration of DNS records
After the configuration of the server, the next paramount thing is the DNS record changing. It helps the individual to direct the connection to the new Exchange 2013 server.
This section clears your apprehensions such as:
• How one can ensure that its Exchange 2007 hostname is configured correctly
• How you can set up your public DNS as well as internal DNS record
• How you can ensure the precise working of it
DNS Configuration includes the following aspects:
• Verification to ensure that the hostname and Client Access server for Exchange 2007 resolves to the publically accessible external IP address
• Change in primary host names. This points to the Exchange 2013 Client Access server external, publically accessible, IP address towards the user public DNS provider.
• Changing of the primary host names for pointing the Exchange 2013 Client Access server internal machine name on the user internal DNS servers
17. Migrate mailboxes from Exchange 2007 to Exchange 2013/2010
This section will brief you about the individual needs to move mailboxes from one Server to another. It also guides about Exchange 2013/2010 moves, and Migration endpoint. Both the mailboxes can be on the same server, variant server, different domain, dissimilar Active Directory site, or in any forest.
Stellar Converter for EDB also helps to migrate mailboxes from one Exchange Server to different. For this, you need to select user mailboxes, enter the login credentials and export them to a live Exchange Server.
You may try yourself for free Demo:
18. Ensure seamless migration of public folder data from Exchange 2013 to Exchange 2013
This step is helpful for those Enterprises which use Public Folders. It helps you get acquainted with the Public Folder. It also guides you on how an individual can migrate public folders to Exchange 2013 from previous versions using serial migration.
By the end you will be aware of what all you need for migration, how a user can do the migration, how to eliminate public folder databases from the legacy Exchange servers, how migration can be rolled back, and how can you ensure the precise working of the same.
19. Post-installation Tasks
This section helps in the configuration of the new Exchange 2013 organization after Microsoft Exchange Server 2013 installation. By this end of this segment, you will be acquainted with mail flow & client access configuration, Internet mail flow configuration via subscribed Edge Transport server, Exchange 2013 installation verification, and Exchange 2013 management tools installation.
By now, you are aware of all that is for migrating mailboxes migration from One Exchange Server to different Exchange Server & Office 365. Let us have a quick look on how you to migrate from one server to another.
How Can You Migrate Mailboxes from One Exchange Server to Different?
To migrate mailboxes from one Exchange Server to another the best practice is the use of third-party converter software as they are easy, fast, simple, and free from manual intervention.
If a suggestion is to be given, then Stellar Converter for EDB is the sure-shot solution. Not only it is user-friendly but is also reliable and secure. Some of its important traits are particular mail searching option from the converted file, Selective conversion option, the capability to save the result in various formats, preview option, multiple files conversion flexibility, and supports archive mailboxes conversion.
Use following steps to move mailboxes from one Exchange Server to another with the help of Stellar Converter for EDB: Step 1: Select ‘Offline EDB file’
Step 2: Browse EDB file
Step 3: Exchange mailbox preview window
Step 4: Select mailbox folder or complete EDB file then Click ‘Live Exchange’ option. Click ‘Next’.
Step 5: Enter live Exchange server credentials, Click OK.
Step 6: Map Mailbox & Click Export
Step 7: That’ it, Your mailboxes has been exported on live Exchange Server.
This do-it-yourself software is in complete harmony with the compatible with Office 2019, 2016, 2013, 2010, 2007, 2003 and MS Exchange Server 2019 2016, 2013, 2010, 2007, 2003, 2000, and 5.5.
The Way Forward
Exchange Migration is a very crucial process. It includes some basic procedures and processes along with pre-requisites for comprehensive end-to-end migration. With the above-stated checklist, you can ensure smooth, fast, and secure migration.