This is very promising -thank you! Turns out I can't even do the Word version because the export to word plugin requires access to the cloud.
Thinking now wordpress xml xport > markdown > pandoc > word ... ew!
From: Code for Libraries <[log in to unmask]> On Behalf Of Voß, Jakob
Sent: Wednesday, September 15, 2021 8:42 AM
To: [log in to unmask]
Subject: [EXT] [CODE4LIB] AW: Wordpress > Atlassian Confluence?
APL external email warning: Verify sender [log in to unmask] before clicking links or attachments
Maybe this works:
1. export Markdown from WordPress (e.g. https://github.com/lonekorean/wordpress-export-to-markdown)
2. convert Markdown to Confluence syntax with pandoc 3. import pages
Step 2 likely requires additional cleanup with pandoc filters or manual search and replace to not include junk and to keep internal links.
Von: Code for Libraries <[log in to unmask]> im Auftrag von Pikas, Christina K. <[log in to unmask]>
Gesendet: Dienstag, 14. September 2021 14:31:25
An: [log in to unmask]
Betreff: [CODE4LIB] Wordpress > Atlassian Confluence?
Recent discussions reminded me I might have good luck asking here (fingers crossed!) I'm faced with moving 2 internal WordPress sites to an internal hosted Confluence wiki. I'm thinking post > page. As far as I can tell, the Confluence community says to use a plugin to convert posts to Word and then use the Confluence tool to import from Word into pages.... This sounds... awful? I wouldn't be doing this if there were any other choice (well, besides SharePoint).
Any suggestions? I know there's a Confluence XML to move from hosted to cloud instances? Has anyone successfully done this?
Christina K. Pikas, BS, MLS, PhD
The Johns Hopkins University Applied Physics Laboratory [log in to unmask]<mailto:[log in to unmask]>