Migrate from Live Exchange server to Office 365 (Exchange Online)

Migrate from Live Exchange server to Office 365 (Exchange Online)

Migrate from Live Exchange server to Office 365

The continually developing notoriety of Microsoft’s cloud stage (Office 365) has convinced many Exchange administrators to change over from their present condition to the cloud. Be that as it may, moving their on-premises Exchange Server to Office 365 isn’t at all a simple assignment with local choices.

Express Migration – A Noteworthy Entry in the Native Options

There are various local alternatives (like cutover relocation, half breed relocation, arranged relocation) accessible for the administrators to move from their on-premises Exchange Server to Office 365. Express Migration, which is viewed as a superior option to the cutover relocation in little and medium associations, is the most recent passage to the rundown of local choices.

As indicated by Microsoft, there is no personal time for the clients with Express Migration, as it permits mail stream progression all through the whole movement process. Express Migration is speedy, and financially savvy.

Advantages of Express Migration

Moving from Exchange Server to Exchange Online may now and again become a cerebral pain for independent ventures. Local choices (like half and half and cutover) for the most part request complex framework and server setups. In any case, Express Migration consummately suits the necessities of little and medium associations, with numerous advantages like:

Client names/passwords synchronizing from on-premises

No compelling reason to reproduce and reconstruct Outlook profiles

Zero vacation during the whole movement process

Pre-requirements for Express Migration

Utilize this technique to relocate messages on the off chance that you:

Have any of these conditions – Exchange 2016, Exchange 2013, or potentially Exchange 2010 server on-premises.

Try not to require index synchronization to deal with your clients.

Focus to relocate to Office 365 over a brief time of couple of weeks or less.

Stage 1-Preparing Express Migration (Verify Domain)

Before continuing towards the movement procedure, ensure you’ve officially agreed to accept Office 365 membership and have a checked space. The outside area name must be included as an Alternative UPN addition in ‘Dynamic Directories Domains and Trusts’.

Utilize the accompanying directions to do as such:

Right-click Active Directory Domains and Trusts, and select Properties.

To include an option UPN postfixes, give your confirmed email space name and select Add. Snap OKto spare the settings.

Doing this will guarantee that your on-premises clients are appointed their UPN addition to their coordinating email area name. In Active Directory Users and Computers, select properties, and snap Account tab and give the applicable space name against the client logon name.

Stage 2-Begin Express Migration from Office 365 Portal

Get into the Admin Center of Office 365 entryway, and explore to Users, and after that to Data Migration.

Ensure you’ve Exchange 2016, Exchange 2013, Exchange 2011 or SBS 2011, preceding downloading and executing Hybrid Configuration Wizard. This wizard causes you to set up half and half organization in on-premises Active registry. It additionally gives you a chance to characterize and arrange different parameters for your cross breed organization. To do this, it initially makes the HybridConfiguration article and accumulate existing Exchange and Active Directory topology setup information. You can likewise figure out how to make and design another half and half arrangement here.

Stage 3-Run Directory Synchronization

To perform relocation for little endeavors, select Office 365 Minimal Hybrid Configuration, and afterward select Synchronize clients and secret word one-time choice to rapidly move your client post boxes (around 50 or less), with no fluff. This will introduce Azure AD Connect for information movement and match up. Select the default Express settings and the synchronization to finish. When you are finished with the relocation, you can deal with the clients with the accompanying alternatives.

Cloud-just – A Method to oversee new clients and passwords in Office 365 gateway, however has no association with on-premises accounts.

Sky blue AD Connect – This strategy incorporates every one of the tasks identified with synchronization personality information (counting passwords) between Azure AD and the on-premises condition.

Microsoft Essential Dashboard Integration – A unified area to regulate Office 365 post boxes, and dispersion bunches without Exchange Server.

Stage 4-Assign Office 365 Licenses to Users

When Azure AD Connect has synchronized the post box clients (with their passwords), at that point you need to appoint Office 365 licenses to move their on-premises letter boxes.

In Admin focus, select Users > Active Users > Edit to dole out item licenses.

Stage 5 – Begin Mailbox Data Migration

In the wake of appointing the licenses, you can start the letter box relocation, with the accompanying advances:

Select Users > Data relocation, and select Exchange as your information administration on the Migration page.

On Data relocation page, select Start movement to permit moving the client letter drops that you need to move.

Note: It is a decent practice to run a relocation test for a few clients, before moving them at the same time. It is encouraged to guarantee that everything works consummately true to form.

Stage 6 – After Migration, Update DNS Record

DNS record is valuable for email frameworks to follow where the messages must be conveyed. Presently when your on-premises Exchange to Office 365 movement is finished, you’ve to wrap setting up your DNS record too.

In Admin focus > Settings > Domains and them update area name.

Restrictions of Express Migration

Most likely that Express Migration is a streamlined movement strategy, however it has certain impediments like:

Performs one bunch at any given moment.

Supports just a single movement endpoint.

Relocation can be performed uniquely on authorized Office 365 clients.

A few components (like a client changes the secret key physically, or new client is made) may not be synchronized with Office 365 during the movement – and consequently making unforeseen inconveniences.

The ‘Express’ strategy isn’t a perfect decision for greater associations as just a single endpoint and a solitary group relocation would be a too tedious procedure for them. Be that as it may, an outsider Exchange movement apparatus is a superior option for bigger associations to recuperate Exchange databases and reestablish them to live Exchange and online Exchange gateways.