If you want a Word independent (i.e. not installed and so not scripting that app), I’d recommend making use of the ubiquitous Pandoc. It’s designed for document conversions … though I suspect Word might do a better job on more complex documents.
Tank you, @sylumer, I will try Pandoc. However, I have Word for Mac installed on my computer through my university’s subscription. If it is scriptable, it would be great. What I would prefer is no to convert every file manually.
Perhaps this article will give you some ideas. If you’re familiar with Word VBA then the first method is very practical, and it’s what I used a number of years ago. I was using Word for Windows then, but most of the VBA commands work on the Mac version of Word also.
Joe Kissel’s Take Control of Automating Your Mac has instructions for doing this in Keyboard Maestro. It’s a good example for learning how to use KM, but it’s also just a fancy implementation of the textutil command, which you could use straight from the command line, if you’re comfortable with that.
Given that this was a rather old thread that was revived, it might be useful to know that there was a related post about using textuil to convert from DOCX to TXT. I’m sure the referenced solution there could be easily converted by simply switching some of the format parameters.
I’ve got pandoc installed now and can use it to convert a file or two as needed. But i’m hoping to integrate it with hazel to automatically covert some files when they get put in a folder. So it’s time to learn a bit more about Bash scripting.