e

Imapsync Massive Migration Software
Imapsync Massive Migration Update
Imapsync Massive Migration Tool
Imapsync Massive Migration Download

Package: imapsync Version: 1.182-1 Severity: normal Hi, When trying to migrate a 400Mb INBOX - one of the emails (40Mb) resulted in the imapsync process balloning to 4x the size of the email. Basically it seems that imapsync will takeup memory equivalent to 4x the size of the largest email.
Normaly there is a migration tool which does the migration for you. Unfortunately it requires a login without encryption or SSL. Uberspace only supports encrypted logins (which is a very good idea) but just STARTTLS and TLS but not SSL. Google also offers two other tools for migration, but they are only available on Windows.

The purpose of imapsync is to migrate IMAP accounts or to backup IMAP accounts. IMAP is one of the three current standard protocols to access mailboxes, the two others are POP3 and HTTP with webmails, webmails are often tied to an IMAP server. Upstream website is - imapsync/FAQ.Massive.txt at master imapsync/imapsync.

Last Version:

Product Version:

February 2015

1.3

Copyright

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Sumatra Development LLC.

2015 Sumatra Development LLC. All rights reserved.

Microsoft, Active Directory, Outlook, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Table of Contents

Understanding MDaemon Migrations

This guide explains how to take legacy scheduling data from MDaemon and insert it into Exchange 2013 or Office 365. We have included the process for migrating email via imapsync as well as provisioning and de-provisioning users.

The process of moving calendar data is usually an order of magnitude more complicated than moving email:

Email is a static object requiring format changes and proper management to move, it is connected fundamentally to a single user.
Calendars and schedules are cross-connected to multiple users. Its value results from exactly those cross-connections. They are true webs of information rather than static threads. For MDaemon migrations, historically static migrations with additional information on the guest lists have proven in the field to be very acceptable to both the user community and administrators.
Migrations like this cannot be successfully accomplished overnight on a day’s notice with no planning or testing. You have been warned.

.

Overview – Train Hard, Fight Easy!

Regardless of the method, number of users, servers, or additional engineering requirements you have, we recommend three things.

ALWAYS run your conversion on a test system BEFORE moving it into your production environment.
ALWAYS run your conversion on a test system BEFORE moving it into your production environment.
ALWAYS run your conversion on a test system BEFORE moving it into your production environment.

We cannot state enough the importance of testing prior to deployment. The most successful migrations we have seen have been the ones with the most preliminary testing. Our motto comes from Marshall Zhukov via the Navy SEALS: Train hard, fight easy.

We take migration results very seriously. The earlier you start, the better and easier the process is.

Sumatra’s MDaemon Migration Sequence

Requirements

Make sure that your environment meets the following software requirements.

MS Exchange 2013 or above

.NET Framework 4.5

The Microsoft Exchange Web Services Managed API V2.2

To insert data into Exchange or Office 365 you will need a service account with Impersonate role.

Imapsync via http://imapsync.lamiral.info/ (You will be glad you used this.)

Sumatra Tools and Scripts:

mCalReader.exe (there is a release version on the code as we send it – feel free to rename a copy for brevity – but keep the original safe in case Sumatra needs to help you with something)
RunSelectedUserMigration.ps1
DistGroupCmdlet.ps1 with mCalReader_ParseGroupFiles.exe
Deployprf.vbs

Migration Sequence

Run RunSelectedUserMigration.ps1 (you will need to edit it first for your environment – see the file itself for instructions) This script will:
1. Read your MDaemon directory and create a CSV file with a set of users and passwords
2. Provision users on Exchange 2013 or Office 365.
  1. NB: Provisioning as contacts is necessary only if you are doing a staged/segmented migration (vs. a “big bang” migration). In that case provision users who are not yet migrated as Exchange Contacts and then change them to full users before their data is migrated.
3. Migrate email via imapsync and mCalReader
Perform your quality assurance spot tests to make sure this went well.
Run DistGroupCmdlet.ps1 (you will need to edit it first for your environment – see the file itself for instructions) This script will:
1. Migrate MDaemon Public Distribution Lists if desired (see later in manual)
Run deployprf.vbs to switch Outlook to look at your new Exchange domain rather than your legacy MDaemon domain

Under the Hood – Detailed Information and References

mCalReader

mCalReader is your best friend for moving calendars from MDaemon into Exchange.

We keep the documentation for this online on our blog where we recommend you look for any news involving MDaemon to Exchange migrations.

This post goes over scripting the calendar migration.

Most of these are self-explanatory. But in general the options you check will depend on how you want to migrate.

Checking “Convert ALL calendar items to appointments” will migrate your calendar items to Exchange as though you were printing a schedule into Outlook. All your data will be there but meetings will not be “live.” If you UNCHECK this, it will re-propose current meetings, meaning that you will have invitations for your current meetings you have been invited to in your INBOX. This has the advantage of getting you closer to live meetings, but it means that it is best suited to a “Big Bang” migration for MDaemon as opposed to a phased migration for MDaemon.

“FOREIGN” users are users outside of your email domain. So if you are reproposing meetings you have the option of re-sending the invitations so that external users are once again in the guest list.

We’ve prepared this brief table to explain how we see most sites set up these options based on how they migrate.

Historical Migration	Staggered Migration – over a month or more OR are changing the domain name/smtp addresses	Staggered Migration over a few days or a few weeks	Big Bang
Convert all calendar entries to appointments	Checked	Checked	Unchecked	Unchecked
Skip Foreign users	n/a	n/a	Checked	Checked

Imapsync Massive Migration