​​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.​

Only mail folders are migrated with POP (Inbox Only) or IMAP as a source. Contacts and Calendar items will need to be exported/imported manually.

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.

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.

IMAP and POP Item Migration Limitations

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