Information and procedures for the migration of Exchange servers to OGo.
TODO:
More general info, maintainers wanted, contributors wanted!
Status
We currently need people with Exchange experience who can fill this section.
Required are all kinds of information on extracting Exchange data into plain
text or structured files.
General Informations
Exchange and OpenGroupware.org do not map to each other one to one. Exchange
has features which OGo doesn't include by default and the reverse.
Specifically a large group of people use Exchange only for sending and
receiving emails, not for calendaring, contact management or task management.
So to fully replace Exchange you also need an email server like Cyrus or
Courier.
Exchange Versions
The "problematic" versions of Exchange are all versions up to Exchange 5.5.
Exchange 5.5 isn't built upon the "WebStore" technology used in Exchange
2000 and 2003 and has no open protocols to access the storage.
So dumping information from Exchange 2000 is relatively easy by using the WebDAV protocol while Exchange 5.5 and below are hard because we need to
collect information on MAPI based export tools.
Mailinglist
We'll setup a mailing list on demand.
Using Outlook for client side migration ...
Notes:
Export as CSV:
Outlook can export any folder data (be it in Exchange 5.5, or locally) as CSV and in a multitude of other formats. In the case of Contacts you can import such CSV files using WebUI. In all other cases you can use the XML-RPC API to import CSV files in a bulk way.
CSV Importer Example
Copy using ZideLook:
If you have a ZideLook copy you can just drag-and-drop or copy-and-paste
contacts, tasks or appointments from a local or Exchange folder into a
ZideStore folder.
That way you can also clean up your folder structure during the migration.
Related Links
The Exchange Server Replacement HOWTO
Microsoft Homepage on Exchange
MSDN on Exchange
Microsoft Technical Resources for Exchange