IMAP and POP Migration FAQs

The following guide covers general information for IMAP migrations utilizing MigrationWiz. 

Preparing for an IMAP or POP Migration

Make sure IMAP access is enabled on your email provider.

​​You need to specify the host name and the port of your IMAP server on your connector.

Typical IMAP ports are:​

  • 143 without SSL/TLS.
  • 993 with SSL/TLS.

When the connection details entered in the MigrationWiz endpoint do not work, MigrationWiz will permute the connection details to attempt different port/SSL configurations to establish connection. 

Many IMAP systems are not properly RFC-compliant. Please contact our Support Team​ if you see unexpected behavior.​

Migrating from IMAP without administrative credentials

Most IMAP systems do not support administrative credentials.

However, here are some systems which support administrative credentials over IMAP.

G Suite supports OAuth authentication. 

To use this feature:

  1. On each mailbox, specify the user name as follows:
    • domain\adminUserName\mailboxUserName
  2. On each mailbox, specify the administrator's password.

Here are some examples of user names you would specify on each mailbox (depending on your configuration):

  1. domain.com\admin\user1
  2. domain\admin\user1
  3. domain\admin@company.com\user@company.com

Some versions of Novell GroupWise support Trusted Key authentication. 

Some versions of Exchange IMAP support admin authentication. 

To use this feature:

  1. On each mailbox, specify the user name as follows:
    • domain\adminUserName\mailboxUserName
  2. On each mailbox, specify the administrator's password.

Here are some examples of user names you would specify on each mailbox (depending on your configuration):

  1. domain.com\admin\user1
  2. domain\admin\user1
  3. domain\admin@company.com\user@company.com

Request administrator login

If administrative login is not available, you may want to:​​

  1. Request credentials from each user.
  2. Reset mailboxes to use the same password (this will lock users out).
  3. Have us automatically request credentials from end users via the steps below.

Request credentials through MigrationWiz

In some cases, you may want to migrate a mailbox but you do not have the credentials. We offer a mechanism in which you can securely request the user name and/or password from the end user that you are going to migrate.

This can be done on an individual basis. To edit the settings of an item that is already configured:

  1. Sign in to your MigrationWiz account.
  2. Open your Project to see its items.
  3. Click on the name of the mailbox you wish to request credentials for.
  4. Click on the Edit Item icon (this is the pencil icon on the far right).
  5. Select I don't know the username or password for the Source or Destination.
  6. Click on Save Item.

This can also be requested on a bulk level, when you want to add users in bulk:

  1. Sign in to your MigrationWiz account.
  2. Create a MigrationWiz mailbox migration project. When entering the Source information, do not click on the checkbox to enter admin credentials.
  3. Click on the green bar for Bulk Add.
  4. Click on the checkbox labeled I don't know the login name and password for the Source mailboxes.
  5. Click on the Upload bar.
  6. Click on the Choose File button. Select and upload your CSV file that contains the list of mailbox names.
  7. Click on the Save button.

When you submit the mailbox for migration, we will send email with a secure link in which the end user may provide their credentials directly to the system. The sequence of steps are as follows:

  1. You submit the item for migration.
  2. Email is sent to the email address configured with a secure link to provide the credentials.
  3. The end user clicks on the provided link, which opens a secure web page.
  4. The end user provides their credentials directly to our system.
  5. The credentials are verified.
  6. The item is immediately submitted for migration.

The status of the migration will remain as "Waiting For End User" until the end user provides their credentials to the system.

You cannot directly delete the mailbox from your dashboard while it is in the "Waiting For End User" state. If you want to delete the mailbox, you need to select the mailbox (by clicking on the checkbox next to the username), and then click on the Stop button at the top of your dashboard. This will restore the mailbox license to your account. You can then delete the mailbox in the normal manner (by clicking on the checkbox next to the username and then clicking on the Delete Items icon at the top of your dashboard).

Preparing for a POP Migration

To migrate from a POP server, you must first create an endpoint for the POP server in MigrationWiz. When creating the endpoint, you need to specify both the host name and the port number of your POP server.

Typical POP ports are:

  • 110 for disabled SSL/TLS.
  • 995 for enabled SSL/TLS.

 POP will only migrate the Inbox folder. Check if your server supports IMAP as an alternative.​

IMAP and POP Item Migration Limitations

Migrating Non-Email Items in IMAP

Migration of items other than email is not possible using IMAP. The IMAP protocol is an email only protocol

Users connecting to email service providers offering IMAP access may be confused by the fact that they are able to create calendar, contact or task items. There are different possibilities:

  1. Often, items are stored on the email client's machine (in a local PST file, for example). The email client connects to the service provider using IMAP, allowing email to be stored on the server. However, other item types are in fact stored locally by the email client (like Outlook). As a result, those items can never be accessed remotely since they reside in local storage.
  2. Sometimes, users may access their service provider using a web client. The web client may allow for the creation of calendar, contact or task items. These items are stored on the server but remain inaccessible using IMAP. In some cases, the email provider may implement an API allowing retrieval of calendar, contact, or task items (CalDav, WebDav, EWS, etc.).
  3. Rarely, users may access their service provider using an email client connected using IMAP, but also use a custom synch agent/connector. The connector calls into APIs allowing retrieval and storage of calendar, contact, or task items (like CalDav, WebDav, EWS, etc.). Changes made to local appointments (for example, in a local PST file) and synched to the server and vice versa.

If the email service provider implements G Suite, do not specify IMAP. Instead, specify G Suite on your connector. This will allow items such as calendar or contact items to be migrated.

If the email service provider implements Exchange, do not specify IMAP. Instead, specify Exchange on your connector. This will allow items such as calendar or contact items to be migrated.

POP Folder Migrations

Only inbox folders may be migrated when using POP. The POP protocol only permits access to the inbox. This is because the POP protocol was designed at a time (1984) when there was no concept of multiple folders, sent items, etc.

To migrate email in folders other than the inbox, you must access the mailbox using another protocol such as IMAP. In case your email client was connected using POP, and you now decide to migrate the mailbox using IMAP, keep in mind the following two facts:

Email may have been deleted from the server:  Most POP servers implement an option to leave items on the server. If this option is enable​d, email remains on the server after being downloaded by the email client. If the option is disabled, email is removed from the server after being downloaded by the email client. MigrationWiz connects to servers (not clients) to retrieve email. So if the option was disabled, MigrationWiz may not find any content (or some content may be missing), even if you connect using IMAP.

  • If your email provider makes a web client, available, use it to determine what is stored on the server.

Email in other folders are not stored on the server: Consider an email client connected to a POP mailbox with emails in folders such as sent items, drafts, etc. As explained above, the POP protocol only permits access to the inbox. As a consequence, email in folders other than the inbox may be stored locally (i.e., PST file). MigrationWiz connects to servers (not clients) to retrieve email. So for folders other than the inbox, MigrationWiz may not find any content (or some content may be missing), even if you connect using IMAP.

  • If your email provider makes a web client available, use it to determine what is stored on the server.

GoDaddy IMAP Migrations

​​When migrating from GoDaddy IMAP, specify the following:

1. For the project, specify the server name as imap.secureserver.net.

2. For each mailbox, enter the user's email address in both the Email Address field and the User Name field, then enter the user's password.

To verify the account is enabled for IMAP access:

  • Log in to GoDaddy web mail.
  • Click on Help.
  • Click on Email Client Settings.
  • Confirm that IMAP is enabled.

Also refer to this article​: http://help.godaddy.com/article/4714.

Folder or Labels with Double Byte Spaces

These do not migrate.

An error will be returned, and reported within MigrationWiz, when retrieving any folder or label with a double byte space in the name, from any IMAP based-system.

G Suite/Gmail uses IMAP. Google has implemented functionality that strips double byte spaces from label names, when labels are created in the default manner. However, if users do not follow standard procedures for creating labels, it is still possible for users to create labels with double byte spaces. In such cases, these labels will not be migrated.

Other IMAP systems use folders rather than labels. If an IMAP system allows for double byte spaces within folder names, and a user creates folder names with double byte spaces, these folders will not be migrated.

Resolution:

Rename the folder in the source mailbox.

UPN Field Formatting for IMAP Migrations

The username name field, when migrating from IMAP systems, typically needs to include the administrator account as part of the username. Different IMAP systems follow different formats for the syntax.

The following is an explanation of the syntax used from the most common IMAP systems.

In your CSV file, each cell in the UserName column consists of two combined names: the user name of the person whose email is being migrated, and the user name of the mailbox admin account. The supported format for mailbox admin credentials is different depending on your Source email system. Here are the formats for several types of Source email systems.

Microsoft Exchange

If you're migrating email from the IMAP implementation for Exchange, use the format Domain/Admin_UserName/User_UserName for the UserName attribute in the migration file. You have a mailbox admin account, where the user name is mailadmin and the password is P@ssw0rd

imap 1.jpg

Dovecot

Source email systems, such as a Dovecot IMAP server that supports Simple Authentication and Security Layer (SASL), use the format User_UserName*Admin_UserName. Let's say you're migrating email from a Dovecot IMAP server using the mailbox admin credentials mailadmin and P@ssw0rd. 

imap2.jpg

Mirapoint

If you're migrating email from Mirapoint Message Server, use the format #user@domain#Admin_UserName#. Let's say you're migrating email using the mailbox admin credentials mailadmin and P@ssw0rd. 

imap3.jpg

Kerio Connect

At this time we can only migrate from Kerio Connect using IMAP.  Please review your Kerio Connect configuration to determine the appropriate server name and port to use with your migration.​​​​

Was this article helpful?
1 out of 2 found this helpful