Exchange to Microsoft 365 Migrations

We built the SkyKick Migration Suites to provide IT partners with an automated migration tool to accelerate their customers’ cloud transformation with comprehensive planning, accurate provisioning, no lost data, and a great end-user experience. Unlike other Microsoft 365 migration tools that focus primarily on moving server-side data—one step in a comprehensive migration-consulting project—SkyKick technology automates up to 90% of the manual effort and enables partners to effectively manage all of the essential steps across the entire migration project.

The best way to get started with an Exchange to Office 365 migration – or any migration – is to contact a SkyKick Migration Suites service provider. They can share detailed information on Pre-Migration Prep Guide, Migration Planning and Configuration, Migration Monitoring and Management and Getting Started Guide for Microsoft 365.

SkyKick performs migrations to Office 365 from every version of Exchange from 2003 onward. For more information, see Exchange to Office 365 Migration.

Exchange 2003 and some early versions of Exchange 2007 support the WebDAV protocol. For those wanting to migrate from Exchange servers using the WebDAV protocol, SkyKick provides a high-fidelity migration from WebDAV with the following limitations:

• No permissions are migrated
• Distribution groups are migrated, but not membership
• Categories are migrated, but no master category list
• Impersonation is not supported (see Configuring a Delegated Access user section below)

For more information, see Migrating from Exchange WebDAV in the SkyKick help center.

For Exchange to Office 365 migrations, SkyKick can pretty much move it all. From your basic email, calendar and contacts data to email signature blocks, rules and calendar permissions, your service provider will make transitioning from the Microsoft Exchange Server to Outlook 365 easy and low risk. For more information, see Exchange to Office 365 Migration.

Yes, while Office 365 to Office 365 (O to O) migrations are similar to migrating from any hosted Exchange EWS server, there are critical differences that require additional attention. For more information see Office 365 to Office 365 Migrations – What you need to know and to discuss a specific O to O migration, contact a SkyKick Migration Suites service provider.

SkyKick migrates server-side data, including email, calendars, tasks, contacts, and inbox rules for individual mailboxes, shared mailboxes, as well as public folders and associated permissions. SkyKick also migrates local client-side data, including auto-complete and email signature blocks.

Because no two migrations are identical, it is difficult to predict precisely how long a migration from Exchange to Office 365 will take. This is due to a variety of factors, including migration method, data source, data type and density, network performance, end-user engagement, and throttling, that can extend the duration required to complete the migration. However, SkyKick makes it easy to schedule and adjust a migration date, scope and requirements, depending on the desired timeline.

Unlike other email migration vendors, SkyKick charges the same price for public folders as mailboxes.

SkyKick migration technology automatically processes data at the nearest regional Microsoft Azure data center in the country where the Office 365 tenant specified in the Migration Planner is located. All email content remains in the region during a migration. This includes compute, path of information from source to destination, and storage of metadata/state files. This information is transferred directly from source server to Office 365. At no time are data written to disk, stored, or taken possession of by SkyKick. For more information see Migration Security.

Directory synchronization is not required for Office 365 or SkyKick Migrations. However, if the company being migrated wants to implement directory synchronization, SkyKick technology can still be used. For more information, see Configuring Active Directory Synchronization for an Office 365 Migration.

Local PC health is essential to the success of the Outlook Assistant. It is recommended that Windows Update be run on all machines prior to the installation of the Outlook Assistant to ensure that the local Office installation is ready to connect to Office 365. For additional requirements see Outlook Assistant Overview.

SkyKick conforms to all the HIPAA requirements of a Business Associate. It can therefore sign and fulfill the elements contained in its Business Associate Agreement (BAA) (once completed and signed by a covered entity performing the migration). The BAA contains the elements specified at 45 CFR 164.504€, including:

• A description of the permitted and required uses of protected health information by SkyKick.
• The provision that SkyKick will not use or further disclose the protected health information other than as permitted or required by the contract or as required by law
• Requirements to use appropriate safeguards to prevent a use or disclosure of the protected health information other than as provided for by the contract.

For more information, see HIPAA Compliant Migrations.