Migrating

Exchange to Office

365BY JAMES DALTON

I have created this presentation over the last 15 hours to demonstrate my ability to take on the

task of migrating exchange to office 365. Although I have not taken on a migration of this scale,

I do have the ability to take on this task.

Not only am I a qualified option, I have several strong skills that will demonstrate I am one of your

strongest candidates.

Owning my own business (Dalton Technical Solutions, LLC) there have been several items clients

who have asked for tasks that required research my own solution. These skills were developed

as I obtained a Bachelors in Economics and Psychology at The University of Kansas. So much

information is available online, and I have the ability to get the right information using analytics.

I rose through the ranks of several entry level positions by streamlining tasks through

technological solutions; saving companies tens of thousands of dollars by creating new

procedures.

I obtained a position on a helpdesk and decided to join Centriq’s 4 month extensive, hands on

program starting a foundation as a network administrator, where I became very familiar with

Server 2012, Active Directory Domain Services & Powershell 4.0. Managing groups and group

policy, routing and remote access, and configuring backups became familiar with VMWare

Hyper-V labs brought all these processes out of the textbook and into practice. I know I can

compete your migration project. I’ve already acquired a tutor at Centriq who has the ability to

train me on any aspect I am unfamiliar with. Good luck with your interviewing; and consider me

as an option.

Why move from Exchange Server

to Microsoft Office 365

Exchange Server has been a way to maintain user mail onsite for

years, so why would a company have the desire to move the mail

server to a cloud?

First, let’s look at a traditional (rudimentary) diagram of the

Exchange Server used by most companies.

Information obtained from: https://www.youtube.com/watch?v=ZtZyQkTmOIw

o Exchange has the benefit of being located on-site

o Many File Server’s are needed to support the end users

o Since mail is located on the local server, archiving and backups

generally also take place in house

o All Remote Users need to be verified through the server , as do

any password changes, profile adjustments and additions using

more bandwidth

o Any disaster to the server (flooding, power shortage, hacking or

acts of nature have the potential to bring down all mail, including

archived messages

o The following slide shows a post migration server (in a rudimentary

format)

Information obtained from: https://www.youtube.com/watch?v=ZtZyQkTmOIw

The Benefits to a cloud based server like Office 365 can be seen

clearly:

o Decreased infrastructure decreases maintenance, and increases

operational effectiveness

o Less File Servers are needed since data traditionally saved to the

Server are hosted by SharePoint

o Information stored on local drives and units are now supported by

OneDrive

o Remote Users are now authenticated by Azure (the infrastructure

used to support Office 365

o There is no longer a need for Exchange Mail servers, nor VPNs

There are several types of Migrations based on several factors:

How many sites, domains, child domains, e-mail accounts are

located throughout the company?

What is the timeline for the migration, what version of exchange is

utilized by the company and are there are their other types of e-

mail supported?

Is third party software used to assist with the migration, such as

Migration Pro, or Office 365 Migrate, or does the company want to

use PST files imported and exported for a free version?

Despite the obvious advantage to cloud computing, Several Factors need

to be considered before jumping right in.

o How is Active Directory setup as far as synchronization is concerned?

o Are the Public Folders going to transfer smoothly to 365s answer of using

SharePoint?

o How is the e-mail security going to be effected? Especially antispam

ware.

o How will the issue of calendar sharing and address books be addressed

o And one of the biggest issues is the archiving issues. The end user wll

flood the helpdesk asking why they went from 3 years of saved e-mails

to 2 days. This issue can be overcome by remapping.

Types of Migrations

Depending on the corporate needs, network traffic, internet

speed, and the version of Exchange, the timeline of the

migration, there are 4 different types of Migration.

Remote Move:

This is the hybrid answer and while utilizing the cloud, there is

still an active mail server onsite. This is the best option if using

Exchange Server 2010, or over 2000 mailboxes .

https://support.office.com/en-us/article/Perform-a-cutover-migration-of-email-to-Office-365-9496e93c-1e59-

41a8-9bb3-6e8df0cd81b4

Types of Migrations

Staged:

In a Staged Migration, mailboxes are moved over in batches.

This is done by replicating users through Active Directory either by a CVS file or traditional Excel File.

This is done over a period of time, and when using Exchange 2003 or 2007.

Information Obtained from TechNet: https://technet.microsoft.com/en-us/library/jj898486(v=exchg.150).aspx

Types of Migrations

Cutover:

This is a short term fix, and used when there are less than 2000

mailboxes. The user identities will be managed by 365.

Types of Migrations

IMAP:

This type of migration is used for large number of user

mailboxes, and is already on online platform to allow end

users the ability to check e-mail via mobile devices. This

leads to a discussion of some of the challenges created by

Migration.

Information Obtained from TechNet: https://technet.microsoft.com/en-us/library/jj200751(v=exchg.150).aspx

There are several issues that can come up during the process of migration, especially if steps are

overlooked. These include:

Calendar Sharing among users

Problems with Address Books

Tasks not transferring from one system to another

Issues with archived messages and archiving messages.

Carefully considering the different options when migrating, following steps from both Office 365,

other third party directions and Microsoft Help such as TechNet.

A competent administrator/engineer who has the ability to troubleshoot problems by testing

options through Virtual Machine Software such as VMware; an individual who posses

exceptional research abilities, and has the ability to reach out to third parties familiar with the

process is the best way to overcome these challenges and have a smooth migration where end

users are not effected by the changes made.

Works Cited

Data Networks: Microsoft Office Migration

https://www.youtube.com/watch?v=ZtZyQkTmOIw

From InfoWorld: Top 10 Gotchas to Avoid During Migrating

http://www.infoworld.com/article/2604770/office-software/top-10-office-365-migration-gotchas-to-

avoid.html

From Microsoft TechNet: Using Powerpoint

https://technet.microsoft.com/library/mt130480.aspx?f=255&MSPPError=-2147217396

Perform a cutover migration of email to Office 365

https://support.office.com/en-us/article/Perform-a-cutover-migration-of-email-to-Office-365-

9496e93c-1e59-41a8-9bb3-6e8df0cd81b4?ui=en-US&rs=en-US&ad=US