Step 1: Confirm IMAP Source Compatibility

Identify the IMAP email service provider and confirm that IMAP access is enabled on the source system. Some providers disable IMAP by default and require it to be turned on before any connection attempt. Verify this before moving to any other configuration step.

Step 2: Gather IMAP Connection Details

Collect the IMAP hostname and port number from the email service provider. If the first connection attempt fails, MigrationWiz can detect the correct SSL configuration and port automatically. Have these details ready before configuring the source endpoint.

Step 3: Prepare the Source System

Confirm that email is stored on the IMAP server and not only in local client storage. Local storage doesn’t migrate. Export the IMAP user list to CSV or request a copy from the service provider if admin access isn’t available. This list is required before the migration project can be configured.

Step 4: Prepare the Destination Environment

Create user accounts on the destination system, whether M365, Google Workspace, Hosted Exchange, or On-Premises Exchange. Assign the appropriate licenses to each account. Confirm the destination is configured to receive inbound email before running any migration pass.

Step 5: Create the MigrationWiz Project

Log in to MigrationWiz and create a new migration project. Select IMAP as the source type. Select the destination platform from the available options: M365, Google Workspace, Hosted Exchange, or On-Premises Exchange. Name the project and save before moving to endpoint configuration.

Step 6: Configure the IMAP Source Endpoint

Enter the IMAP server name and port number. For Google Workspace IMAP migrations, provide admin credentials if available. If admin credentials are not available, individual user credentials will be collected at the user level later in the project setup.

Step 7: Configure the Destination Endpoint

Set up the destination endpoint using administrative credentials for the target platform. Verify the connection before proceeding. A failed endpoint configuration that gets missed here will surface during the migration pass when it’s harder to diagnose and fix.

Step 8: Run a Pilot Migration

Before running the full migration, test against a single user mailbox. Check that the folder structure transferred correctly and review the folder mapping configuration. Pay close attention to system folders, as IMAP only reliably identifies the Inbox folder and other system folders may use different naming conventions across platforms. Use Advanced Options to create custom folder remappings where needed. Resolve any issues before running the full migration.

Step 9: Execute the Full Migration

Select all users in the project and click Start. Choose Full Migration. MigrationWiz will migrate all mail from the IMAP source to the destination. Monitor the pass as it runs and document any failures for follow-up before closing the project.

#Migration #CloudMigration #Azure #M365Migration #EmailMigration