Migrating emails from the existing email service to SkyDesk Mail
SkyDesk Mail offers a simple solution to migrate your emails from your existing email service to the respective user accounts in SkyDesk Mail directly. IMAP Migration is the most recommended process to migrate the emails as the emails are migrated along with their folders and state details. The impact of the change in email service will be very minimal for the users, as they can continue from where they left. This also ensures that they easily get accustomed to the new email service, without affecting the productivity.
In case the previous email server does not support IMAP, then the emails can also be migrated via POP migration.
If the previous email service was run by an in-house/ on-premise Exchange Server (without POP/IMAP support) or the users emails were in Outlook and available as offline PST files, then the administrator can use Exchange Migration Wizard to migrate the emails from Exchange Server/ Outlook to the respective user accounts in SkyDesk Mail. The SkyDesk Mail Migration Wizard also supports Hosted Exchange Environments, to migrate the emails using Outlook Profile details, connecting to the Hosted Exchange server.
If your emails are in a cloud hosted email service like Google Apps or Yahoo or any other cloud email server which support IMAP Access, you can perform a server to server migration via IMAP from the Control Panel.
SkyDesk Mail supports both IMAP and POP Migration, but IMAP Migration has more advantages compared to the POP Migration.
|IMAP Migration||POP Migration|
|Folder details are migrated.||POP does not support Folder based migration. All emails are migrated to Inbox.|
|Email states (Read/ Unread) are maintained.||The emails retrieved as 'Unread' via POP|
Multiple Client support:
Only Single Client support:
|The migration is generally fast, and the migration info is detailed.||The migration via POP is slower than IMAP Migration.|
|Specific failures in migration can be tracked and corrected.||The failure information in POP is not specific and will be vague.|
For both POP/ IMAP Migration, the following details are required.
- Name of the Server - Hostname of the IMAP Server or the POP Server from which the migration needs to initiated
- Server Port - For source Server standard ports for SSL and Non SSL are supported.
- Supported ports for IMAP - 143 (Non SSL), 993 (SSL)
- Supported ports for POP - 110 (Non SSL), 995 (SSL)
- SSL Type - Only Trusted Certificates are supported. Self Signed SSL certificates are not supported due to security reasons.
- Migration Protocol - Choose if your migration protocol is POP or IMAP.
- Source User Names and Passwords for the user accounts - Make sure that the source accounts have IMAP access turned On.
- Exclude Folder List - The administrator can exclude some folders like "Spam" to quicken the migration process. Further, they can ask the users to create a common folder and move the emails that need not be migrated. This folder can be provided in the commonly exclude list, which will apply for all users.
- Maximum Connection Limit - The maximum connection limit is the number of maximum connections accepted by the server at a given time. For example, if you provide 5 as the maximum connection limit when the migration is started, the migration process will be started simultaneously for 5 users. The migration process will be faster when there are parallel migrations happening between the servers.
- Path Prefix - Some IMAP servers expect the PATH Prefix details for connecting and retrieving emails via IMAP.
- Black Out Time - In case there is any known down time for the server or particular times of the week during which the server is overloaded, specify the Day of the week, Time in 24-hour format (From 'x' hours to 'y' hours) and the corresponding Timezone. The migration would be paused during the specified time duration to avoid any migration failures due to that. The Blackout Time and Timezone are applicable, only if there are any predetermined Time Intervals, during which the migration should be paused.
Source Server Details:
To add a new migration, you need to add the source server from which the emails should be migrated. You can also perform the migration in batches, and also from different servers if you have multiple domains hosted with different providers and want to migrate everything to SkyDesk Mail.
- Log in to https://www.skydesk.jp/en/apps/mail/
- Launch Control Panel, go to Mail Administration, and choose Email Migration.
- Select Add Migration, to provide server details for migration.
- Provide a title for the migration.
Select the Migration Protocol as IMAP or POP based on your preference.
- Provide the Host-Name of the server, the SSL type and the port number for migration.
- Select if your migration is going to be done from Gmail or other services. Migration from Gmail follows a slightly different process, as described here.
- Provide the maximum connection limit for your server.
- Exclude Folder List - The list of folders that need not be migrated during the migration.
- Select Add Migration to save the server details.
- You will be taken back to the Migration Homepage.
- You need to add the account details to be migrated as the next step.
After you have added the Server details, you will be taken back the Migration Homepage. Click the name of the migration, under the Migration Name field, to add the source accounts to be migrated.
You can add the accounts manually or import the details from a CSV file. However, make sure that you have the source and the destination account details ready. For each user added, the source credentials are checked with the server and the user gets added only if the source authentication is successful.
Steps to add user accounts for Migration:
- Select the Migration Name to which you want to add the source and destination details.
- Select Add Accounts to add the account details manually
- Provide the Source username/ Password and the Destination to which the emails should be migrated to.
- In case of IMAP migration, you can choose to skip any folders during migration.
- The skip folders will be handy when the admins rerun migrations for the same set of users for some new emails or missed emails.
This will be authenticated with the source server provided, once you click Add.
Steps to Import users from CSV file:
- Prepare an excel file or a SkyDesk Sheet with the headers Source, Password, Destination. You can optionally include a column Priority, which specifies the order in which users accounts needs to be migrated.
- Fill in the details under the respective columns for the user accounts to be migrated.
- Save the file as a CSV file.
Click Upload Accounts link in the Migration Accounts page.
- Choose the respective file and Click Ok to upload the accounts.
The accounts added will be listed in the section.
- You will be able to modify the Server details or the Migration type before you start the migration.
- Check whether all the accounts to be migrated has been listed in Accounts section.
In Gmail accounts, the emails are organized under labels and the labels act like folders when accessed via IMAP. Gmail allows an email to be under more than one label, as per its behavior. During migration to SkyDesk Mail, the same email is migrated into different folders based on the labels applied to that email in the Gmail account. i.e. An email which has 4 labels, will be migrated 4 times and will occupy 4 times its size because of the duplication.
Let’s say that the Gmail account has an email of size 10 MB under the labels Inbox and Work. During migration, the email would get copied to the Inbox and Work folders over here at SkyDesk Mail and it takes up 20 MB of space, leading to usage of more space than you anticipated initially. Apart from that, Gmail also has a label called 'All Mails' which it applies to all the emails. Hence the email can actually take up 30 MB of space in the place of 10 MB.
This, in turn, might lead to your migration getting suspended, in case the account does not have required storage. You can request your users to remove the labels from Gmail, in case they have too many labels and multi-labelling practices. In other cases, you can just ignore the 'Gmail' folder during migration.
- Make sure that the user has not changed the password of the source account when you run the migration.
- The access to the old server is still in place for the account, until the migration is completed.
- In case you are migrating from Google Apps servers, you may have to login via the web once to authenticate the IMAP activity in your account. In this case, request the user to login to the Google Apps account from web and follow the steps listed in this help page for the error 'Web login required': https://support.google.com/mail/answer/78754
- Similarly, even in Outlook.com, your source account access may be blocked on detection of activity from new IP Addresses. We request you to login and allow access to the SkyDesk Mail IP addresses, listed there under Recent Activity. Select 'This was me' to trust the SkyDesk Mail IP addresses and proceed with the migration.
In the Control Panel, navigate to Migration under Mail Administration. Ensure that the source passwords are not changed after adding the users for migration. The password should be the same until the entire migration process is completed.You can add multiple migrations from different servers or from the same server for different sets of users to have a phased and planned migration.
- The list of migrations you have added will be listed in the Migrations page.
Click 'Start' link, across the migration you have just added to start the migration.
- The Migration will be scheduled and the status will be 'In Progress' for the migration that is currently running.
You can view the overall migration status in the listing, and detailed migration status in the Accounts section.
- For IMAP Migration, detailed statistics along with folder information will be available.
Click the count under the Total field to view the detailed information about the folder-wise migration details.
- Under each account, the errors, if any, will also be listed with details. Click Failed to view the number of emails not migrated and the reason.
- The common reasons include:
- Email Size Exceeded - If the size of the email in the source server exceeds the maximum size defined in the user's email policy, such emails will not be migrated.
- Mail already present - If the email is a duplicate of an email already in the user's account in SkyDesk, the duplicate emails will not be migrated.
- Too many addresses - If the number of To Addresses in an email exceeds the permitted limit in SkyDesk Mail, the email will not be migrated.
- Invalid Message - If the email format is not as per the RFC definitions, with an incorrect header or email format, such emails will not be migrated.
Unable to Process - In case there are any internal processing errors during the migration of a particular email, such emails will be skipped during migration.
- Apart from the migration statistics, the administrator and the users will receive a summary of migration information after the completion.
In case of some failures like Internal Error, the administrator can migrate only selective folders instead of entire migration. This will optimize the run time for the migration, by removing the duplicates and the check for duplicate emails.
Suspension of Migration
During the process of migration, if the size of the emails migrated in the account, exceeds the allowed storage, the incoming emails may get blocked. Hence to avoid this, if the account reaches 80% of the allowed storage, the migration gets suspended(paused) temporarily. You can create more space either by deleting some of the old or unwanted emails in your previous account or by purchasing additional storage for your SkyDesk account.
Once you are confident that the account has enough space, you can resume the migration.