Originally Posted by ysss

@Laughing Man:

If it's their first time migrating to OO.o, chances are the company would want to engage with an external party with previous experience in doing similar project to (first) consult for the project's feasibility and risks, and to have them assist with the migration. Either this, or reassign some of your IT staff to (leave their existing tasks and) learn about OO.o and make the migration plan, etc. Either way, those are costs.

You've to train your existing personnel and also all future recruits . so training materials have to be prepared and integrated with new employees training programs. MS Office sort of get a free pass, as you'd see more office workers buy their own copies of MS Office for Dummies (ha) as they see it as a 'valuable skill to have'. Not so with OO.o.

Then when it comes time to the actual migration, it's probably as simple as a network copy + announcement email.. or having it rerolled to whatever application\package distribution system in place and pushed to the elligible departments..

..after that, you'd still have to have competent support in place to deal with any potential problems (compatibility & usability issues mainly).. do keep in mind that office files may come from or be addressed to external parties outside of your control, which 90% of them still use MS Office. (Yes, I know about PDF).