POP3 to Microsoft 365 Migration

Most POP servers only store a few weeks of mail data. The majority resides on the local client such as Outlook. When performing a POP migration, the SkyKick Outlook Assistant will perform the entire migration process at cutover by uploading the Primary POP data store into the new Microsoft 365 Outlook profile created by the Outlook Assistant. See POP Migrations – What you need to know for more information.

The SkyKick Outlook Assistant is a powerful, yet lightweight client application to connect customer end-users to their new mailbox at the appropriate time and replicate their previous Outlook experience as closely as possible. It:

• Performs desktop and Outlook readiness checks.
• Guides customer end-users through the M365 authentication process to their new mailbox
• Migrates supported local data and settings (i.e. signature blocks and address autocomplete) where present.

For more information and requirements see Outlook Assistant 9.0 Overview.

The best way to get started with a POP to Microsoft 365 migration is to explore the Migrations Full Suite vNext Guide: POP to Microsoft 365.

As a 100% to-partner company, we built the SkyKick Migration Suites to provide IT partners with an automated migration tool to accelerate their cloud business 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 SkyKick technology automates the migration of client-side data which is critical to migrate the extensive types and amount of POP data that is not stored on the server. Beyond data migration, SkyKick technology automates manual effort across more facets of a migration project, including provisioning, migrating client-side data, and setting up Outlook profiles in Microsoft 365, to help partners manage all the essential steps across a migration project and deliver customers a seamless migration experience.

Because no two migrations are identical, it is difficult to predict precisely how long to migrate POP to Microsoft 365. 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. If you are an IT partner with a specific migration project, contact support@skykick.com for more information on the timeline.

SkyKick migration technology automatically processes data at the nearest regional Microsoft Azure data center in the country where the Microsoft 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 the source server to Microsoft 365. At no time is data written to disk, stored, or taken possession of by SkyKick. For more information see Migration Security.

Directory synchronization is not required for Microsoft 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.

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.