Slashdot Mirror
Can a Small Business Migrate Smoothly To OpenOffice.org v3?
Pay The Piper writes "As an IT Support Technician in a small corporation, I've been tasked by one of my managers to determine the feasibility of transitioning our small 40 or 50 person office from Microsoft Office 2000 to Open Office 3.0. What are some of the problems I may run into as far as document cross compatibility? Has the Open Office suite evolved to a point that permits easy transition from Microsoft's suite? Besides the obvious 'free vs. expensive' argument, what are some of the pros and cons of transitioning? Are there any reliable ways to view/edit/save a document saved in the OpenXML format through Open Office, or are my co-workers and I still going to be stuck in Microsoftland?" (Given that company-wide rollouts take some time to implement, this early look at the features of OO.o 3.1 may have some relevance, too.)
Microsoft Office 2000 to Open Office 3.0
I will say that although I have not had the joy of opening Office 2000 files with OO.o 3.0, I do recall there being some serious issues between powerpoint slides. Some weird rendering going on in OO.o for what reason I do not know. In my line of work, powerpoint is perversely pervasive--to the point of alarm for me. If this is true for you, do some testing before taking the plunge!
Are there any reliable ways to view/edit/save a document saved in the OpenXML format through Open Office ...
I regrettably give you the option of getting Novell's OO.o distribution (here) in which you can install an extension for OpenXML.
The best recommendation I can give you is to do this change only if you can assure that it will not hinder your ability to serve your customer or detract largely from productivity.
My work here is dung.
Short : YES.
Long : Yes, but you will have to tell the office whiners to STFU.
Honestly it's not that hard, it requires some retraining of habits. and requires users to not be raging Luddites.
If you get management buy in for it, the transition will take weeks before all the whining dies down. the only problem is when you get users that are not smart enough to understand what they were instructed to do because they did it the other way for the past 5 years.
Do not look at laser with remaining good eye.
Do your documents utilize VB macros? If so, you may want to look at Novell's fork of OOo at go-oo.org which improve macro support. Otherwise mainline OOo should open all your MS Office 2000 documents with ease.
The interface of OOo is closer to MS Office 2000, than MS Office 2007's interface is. Training users should actually be easier than training users on MS Office 2007.
When I converted my mother to Linux I told her she'd have to give up MS Office. When I installed openSUSE 11 and OOo 3, she thanked me for giving her MS Office. It looked so similar, she couldn't tell the difference.
The only little bit of advice I'd give you, is to go into the program options and set the default file formats. While I praise ODF, and want the world to adopt it, if you're going to send documents out to the rest of the world, you'll have to save them either in PDF format (which OOo does natively) or save them in MS formats for everyone else.
When you're done, tell your boss how you just saved the company $400 a pop times 50 people, and ask for a raise.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
Pick a sample of users - some tech-savvy, some not - who interoperate with others still using microsoftware. A pilot should bring out the most pressing points of contact and show whether or not the compatibility level is adequate.
Our office of 50+ transitioned back in the early 2.0 days with nary a hitch. A couple of people still have MS Office for specific compatibility reasons (certain spreadsheet macros, that sort of thing) but everyone else from IT to the receptionist has OOo. We spent approximately $0.00 on training, instead going with "here's your new word processor". People who need office suites picked up on it quickly and people who primarily do other things didn't really care.
Dewey, what part of this looks like authorities should be involved?
For example do you have Word setup to access a database or something ridiculous like that?
Mail merge is not usually an odd-ball feature for anyone who has more than a handful of friends or clients. As an aside and from experience, attempting to mail merge anything with over 3,000 rows in OOo generally results in pain.
There are 1.1... kinds of people.
Your biggest griper will be a finance guy (like me). For him, just buy excel. Forcing him to use something other than excel is cruel and unusual punishment.
If you're exchanging MS Office docs -- particularly ones going through multiple editions of MSWord, it is a commonplace for MS to claim the docs are corrupt and refuse to do anything. Frequently, OpenSource tools like OpenOffice.org or AbiWord read the files perfectly well, and then can save them un-corrupted in ".doc" form. My wife is an attorney, and she has to jump through that hoop all the time.
"My opinions are my own, and I've got *lots* of them!"