Finale 25/26/27 can do this., 25/26 to MusicXML up to 3.1; 27 to xml v.4.0. You had three years to update any version to 27 for $79-$129 depending on what sales were going on. Now the cost is $149 and includes a Dorico license.

Nice of you to want it for free, I suppose, but that is unlikely.

I'm seeing better results importing MusicXML 4.0 into MuseScore 4.x vs. Dorico 5.x, and the difference is pretty big/noticeable - at least for me.  That is basically all I've been using Finale for the past 2+ years - opening up MusicXML that people share to me because it tended to handle the output from anywhere pretty well, while spitting out sane output that tripped up other applications less often.

I guess MuseScore will become that solution, moving forwards, since it has always had the best MusicXML support outside of Finale (and Dolet, by extension).

For people who want to be able to archive open the MusicXML that requires the least amount of extra work to "look as close as possible" to Finale, then it may be worth exploring keeping MuseScore around for that purpose.  Dorico 5 is better than Dorico 3.5 or 4, so I expect it to improve, but it's definitely behind the alternatives in that area.

I'd still do all new work in Dorico, though.

I still think PDF > MusicXML as a long-term archival strategy.  Too much time wasted re-doing the same work with MusicXML when you want to open and print something out.

MusicXML export from MuseScore 4 is certainly better than Dorico 5 nowadays, that's for certain. Import from Finale depends but I also give the edge to MuseScore. A couple years ago, both were horrible. 

In the Dorico forums, Michael Good points out that there are features and functions found in 27 that Dorico and MuseScore can't handle (yet?) and this will affect MusicXML 4 imports from Finale. As he invented MusicXML and didn't retire from MakeMusic till earlier this year, it's a good idea to pay attention to that.

I just imported the same file into MuseScore 3.6.2 (Rel. 01/2021) and the formatting is practically identical to the source Finale file, like the MuseScore 4.4 import.  Same result.

So, the disparity between it and Dorico (in this area) has existed at least for the past 3.5+ years; and I'd argue longer, considering Dorico 3.x was bordering on useless when it came to MusicXML Imports.  I don't think Dorico was ever approaching on par with MuseScore for this.

I have a large amount of work in Finale.  I took one file, converted it to XML and opened it in Dorico 5 Pro.  Success.  Now, how can I do more than one file at a time?  How do you open them in Finale v27 to make this conversation?  Thank you.

How do you open them in Finale v27 to make this conversation?

You don't open them first. Finale has the ability to batch convert to .musicxml and include subfolders. There are a number of YouTube videos on this but I would start here. You can ask questions if they are not answered in the 27 posts.

https://forums.steinberg.net/t/batch-convert-finale-files-to-musicxml/929956/3 

I am having a hard time getting music XML from Finale into Sibelius. Whenever I create a Music XML file from Finale and try to open it in Sibelius, Sibelius gives an error message, stating that this is not a music XML file.
This whole Finale ending debacle is causing a great deal of grief for everyone.

Do you know what version of Music XML you're exporting? It might be a version mismatch - check in this location below. Sibelius has a reputation for Music XML import sketchiness and just as in Dorico, many launder their music xml through MuseScore. 

Sibelius has this tutorial, which you might have already seen
https://www.avid.com/resource-center/how-to-migrate-from-finale-to-sibelius

Sibelius since 2019 uses the free Dolet 8 plug-in from MakeMusic to handle MusicXML 4.0. Download it from this ink if you don’t have it yet.
https://www.musicxml.com/dolet-plugin/dolet-plugin-for-sibelius/

Otherwise, select MusicXML 4.0 and Export uncompressed... from the Preferences as referenced above.

Here is how my MusicXML Preferences are set. Notice that these are not the default settings.