Slashdot Mirror
Germany Publishes Windows to Linux Migration Guide
Bombcar writes "This Migration Document is also available. It has details on going from WinNT to Linux/FLOSS/Samba et.al, with less detail on RedHat/Ximian/GNOME and more on SuSE/Mandrake/KDE. See Kurt's post to Samba Technical for more details."
With every migration, there is always the issue of "does the new product implement all 25000 features of the old product".
When you start your migration with the assumption "the new product must do everything the old product did plus possibly more" you will not only limit your options, but you will also migrate to more and more complex systems.
Instead, you should look at the requirements of the organisation, and define the properties of the system that will be implemented. Maybe Outlook/Exchange implements them, but that does not mean that it is the only solution to the problem.
Don't try to implement an Outlook/Exchange replacement, but define what your company needs and implement that. Possibly it does not need all the features of Outlook/Exchange and thus they do not need to be present in the "replacement".
We run an IMAP mailserver on Linux, with LDAP address book, and a separate web-based calendaring system. All are accessed from Mozilla on the (Windows) desktops. It works fine.
The only thing I would want to be improved is the maintenance of the LDAP address book by nontechnical users.