If you haven't sen it already, you might find the Migration Guide available from this page
helpful. It is written for 2.x, It looks like an updated version for 3.1 is not yet available.
As a general rule, it is best to work with the OOo native file formats (odt, ods, etc.) and only save as MS or other formats when needed for sharing with those who do not have OOo. If you need to stick with the plan to use MS formats, you will need to carefully detail what OOo features must not
be used by your employees because they will be lost when saving to a different format.
For example, OOo includes a "conditional text" field that is not supported by in the .doc format. So, for example, I have a funeral template that includes "conditional text" fields for pronouns and certain other words referring to the deceased. All I have to do is indicate once whether the individual in question is male or female, and then OOo will automatically enter the right pronoun (e.g. "her") or word (e.g. "daughter") in the various conditional fields scattered across the document. But if I save the resulting file in .doc format, all those fields are lost, and there are pronouns and words missing all over the place. I learned this the hard way.
Some of the displacement issues may not be solvable in a global sense, and may require individual correction each time the file is opened if it is saved in a non-native format.
NeoOffice (app store version) OpenOffice.org 4.1 and LibreOffice 4.3 on Mac OS X El Capitan
OpenOffice.org 4.1.2 on Windows 10 (Previously on Vista)