If I understand correctly the case, it is a matter of using a tool in an organisation without having to think over the nature of the tool.
The relevant questions are: what is the “production”? how is it produced (workflow, people, …)?
From my experience, trying to change for a new tool without taking human factors and tool specificities into consideration is doomed to failure. The startegy “new tool, no change in habits” is wrong, if not suicidal.
Your main argument is about people: they would use the tool routinely and must not need to understand the arcanes of it while using it. This calls for a reasonable amount of automation in the process of producing letters, specifications, reports, proposals, … Add to that, you probably have a “graphic chart” as part of corporate communication. In MS Word, it likely translates into various style sheets, one for each type of document unless all are merged into a giant one.
Your people are accustomed to giving styles Date for the first line, then Addressee, then Subject, then Text Body when they come to the core of the letter. The style sheet may have some Heading n paragraph to emphasise structure of content. At the end, you may have Salutation for a formal good-bye and Signee.
With this scheme, your people already know that they have to click somewhere when they make a topic or structure transition. Jumping to a new page is one of these transition, which is cleverly achieved through a style in the sheet. It is even the only way to guarantee that all documents adhere to the rules defined in the chart, so that all look alike.
You can do the same with LO Writer and even better.
LO Writer has no style sheet per se, because styles are integrated into a document. But, it has a very powerful feature: templates. Templates contain not only styles but also text, such as company logo, legal information in the first page footer, pre-typed data like subject:, refers:, attachments:, reply address, … It is easier for the average Joe to delete unneeded paragraph than add a wanted one consisted with the graphic chart.
Your job is to design those templates and a short notice explaining what is not self-explanatory. Make experiments with administrative clerks to get their feed-back.
You may object that templates imply maintenance work. Yes and this an advantage. Put the templates on a server shared by everybody. Then, every update is immediately available and automatically used by all. When the comm guys fancy to change the corporate logo or the “official” font face, how do you presently make sure that everybody switches to the new rules at once and simultaneously without some black sheep using stale stylesheets?
As you see, it not only a matter of comparable or equivalent features, but before all, a matter of work organisation. Maybe the clerks do not need to understand what happens behind the stage, but you, as an IT learned skilled professional, must objectively evaluate the differences between both tools, make your benefit from them and design the required templates which will make people forget which tool they use and be happy in their work. You must anticipate the consequences of your choices. This is not easy and can’t be done pusillanimously in one day. It has a deep impact on company productivity since written communication is one of the chore works.
You did not tell what your deadline is.