Okay, realizing there was not logical way to bring in old Manila threaded discussions was a bummer. Onward and upward. I working on mapping specific URLs from each Manila peice exported to WordPress. Stories, images etc. I am relying on the a part of the Manila database called the glossary (adrSite^.["#glossary"] just in case you do care).
Over the years managing Manila servers I can recall just enough cases of trouble with this index that I have a slight superstition about it, but we’re talking about a handful of cases years ago. Since this is a rare service request (haven’t heard about a problem in years) I think I’m gonna put my trust in this source as a reliable lookup for Manila stories and pictures.
WordPress returns enough information to calculate the new URL with each new post, story or image posted. So I just need to store the old URL and the new URL together so some future process can point traffic frm the old to the new.
Next I will need to devise the most efficient way for the WordPress site to recognize an incoming Manila link (which normally it would reject as a 404 not found) and forward the request to the the object’s new location. This way we can minimize (although not entirely eliminate) breakage for your content when you move.