After all, migrating to OpenOffice would save an absolute fortune in Microsoft Office licences, which is important in a time of shrinking IT budgets. Before you jump right in and begin a migration, though, there are a few issues that you need to be aware of.
Before you commit to a migration, you need to be aware that with OpenOffice, you get what you pay for.
When you buy a copy of Microsoft Office, you're buying a mature suite of many different products. Your Microsoft Office purchase also entitles you to technical support. Although OpenOffice is comparable to Microsoft Office in many ways, there are a lot of places in which it's seriously lacking. For example, technical support is pretty much limited to whatever information you can find on the Internet.
Another major limitation to OpenOffice is that, although it offers programs that compete with Microsoft Word, Excel, and PowerPoint, it does not offer products similar to other Microsoft Office applications. The most notable example is that there is no OpenOffice version of Microsoft Outlook. You can also forget about getting OpenOffice equivalents to Microsoft Office 2003 products such as Microsoft OneNote, Publisher, InfoPath, and Access.
I'll be the first to admit that there are decent open-source database and desktop publishing applications. The fact that OpenOffice doesn't offer such programs might not be a big deal since you can get these types of applications for free from other places. However, even if equivalents to Word, Excel, and PowerPoint were all you needed, you should still think twice before giving up Microsoft Office in favour of OpenOffice. That's because the programs that come with OpenOffice do not have as many features as their Microsoft Office counterparts.
Unless you're a power user, you may never even notice the features that are missing from OpenOffice. The majority of the missing features are things that the average user doesn't tend to use. Even so, the missing features can make converting Microsoft Office documents to OpenOffice format difficult. For example, in Microsoft Office, macros are encoded in Visual Basic Script. However, OpenOffice doesn't support Visual Basic script.
This means that if you have a Microsoft Office document that you want to convert to OpenOffice, and the document contains macros, you'll have to completely recreate the macros once the conversion process is complete. You can open a Microsoft Office document containing macros into OpenOffice, but the macro code will not do anything. You can view or edit the code, but you can't execute it.
3%
5%
This article sounds like it was written by Microsoft.
Also, (for example) if the writer did a decent amount of research he would have found out that no email client was developed for OpenOffice as there are already suitable open source alternatives ... and it's not worth the effort to duplicate an existing product.
On a whole, the quality of the article is lacking.
Andrew Smith