ICT-Hotlist Topic

Back to the ICT-Hotlist...

How to Migrate from Zarafa to Microsoft Exchange Server 2013 or Office 365

By Johan van Soest.

Published : 2014-06-04.

Last updated : 2019-01-25.

OGD ict-diensten (OGD IT services) is a Dutch IT service provider. From five offices, over 700 ambitious and highly educated professionals specialize in the fields of IT infrastructure, service management and software development and work for over 1600 customers. Their best known product TOPdesk is an award-winning solution for ITIL aligned service management software for IT, Facilities Management, and eHRM help desks.

OGD have switched from Zarafa with Active Directory integration to Microsoft Exchange 2013. In the excellent blog Dave Stork (IT Architect at OGD) writes about:

The reasons why OGD has migrated from Zarafa to Microsoft Exchange 2013.
From open source groupware solution Zarafa to Exchange: Part 1, A New Beginning. "The goal of the migration is to migrate existing mail from Zarafa to Exchange, in such a way that users will have the most smooth transition possible."...
From open source groupware solution Zarafa to Exchange: Part 2, Active Directory. "Luckily, in most cases you can re-use the same objects (for example Distribution groups, Users and Contacts) and mail(box) enable them in Exchange. Zarafa and Exchange can be implemented in the same AD forest (during migration), but there are some gotchas." ...
More on the migration tools in upcoming blogs.

Zarafa uses Microsoft Outlook or Microsofts ExMerge to import the Exchange Data to their semi open-source Zarafa Mail-server solution. They use the PST format to export a user mailbox and import it in Zarafa. This route can also be reverted as Zarafa writes "It is also possible to export .pst files from Zarafa" with the zarafamigrationtool.msi as can be read here in the ZCP-Migration-tool-manual.pdf release 7.2.1 Identical tools are used with Zarafa's successor Kopano

You may vote your opinion about this article:

Scripts and programming examples disclaimer

Unless stated otherwise, the script sources and programming examples provided are copyrighted freeware. You may modify them, as long as a reference to the original code and hyperlink to the source page is included in the modified code and documentation. However, it is not allowed to publish (copies of) scripts and programming examples on your own site, blog, vlog, or distribute them on paper or any other medium, without prior written consent.
Many of the techniques used in these scripts, including but not limited to modifying the registry or system files and settings, impose a risk of rendering the Operating System inoperable and loss of data. Make sure you have verified full backups and the associated restore software available before running any script or programming example. Use these scripts and programming examples entirely at your own risk. All liability claims against the author in relation to material or non-material losses caused by the use, misuse or non-use of the information provided, or the use of incorrect or incomplete information, are excluded. All content is subject to change and provided without obligation.