Laugh at the worst online-setup ever, then show your own smarts with solution

I must be the perfect case study of why CMS are not a great idea for the simple minded. I am a photographer with a little blog and site designed to attract people who are coming to Paris and want photos. I was clueless when establishing my online presence and the result is a ridiculous setup that I want to change. I cannot just start from scratch, however, because I have been told I have good inbound links.

How I created this mess:
I started a site using a Flash/HTML template from a company that every photographer was using at the time called Bludomain. The original setup was a “Splash Page” that was the homepage for oneandonlyparisphotography.com and had two buttons. One button would take you to the Flash version of the site. The other button — for people who didn’t have flash installed — would take you to an HTML version of the exact site. I soon added a WP blog that opened under “oneandonlyparisphotography.com/blog as a third splash page option. Of course the WP blog got all the Google love, so I soon wanted to kill the Flash/HTML site and convert the WP blog into a blogsite by adding static pages. The problem was I had already picked up some good inbound links before I figured this out.

I hid the Flash version of my site. Now I’m left with a splash page with very little crawlable content and 2 links:

Splash Page: “oneandonlyparisphotography.com” (Good inbound links to this weak page.)

1 splash page direct link to the blog: “oneandonlyparisphotography.com/blog” (Good links and some of them deep in the post pages.)

1 splash page JavaScript-based link that triggers the HTML version in a new window: “oneandonlyparisphotography.com/htmlver” (Not many inbound links.)

The strangest setup is the way a button in the WP blog navigation menu called “Website” opens a new window for the HTML site. This button makes the HTML site pages resolve with the “www”. If you access the same HTML version through clicking on the JavaScript-based link on the splash page, however, the site resolves without the “www”, just like the splash page itself and the WP blog resolve without the “www”.

What I want:
I have a theme I love that they say is good (Prophoto4). I want to ditch my current HTML site and put a new WP install at the root (oneandonlyparisphotography.com). I’ll build this new WP install into blogsite with static pages and post pages. The big question that stumps SEOs and developers is the following: Can I import all the content on my old blog’s post pages without killing all my Google equity? The old WP install is on oneandonlyparisphotography.com/blog. Since my new install will be at the root (oneandonlyparisphotography.com) can’t I just put a button on that install’s nav menu called “Blog” that opens the old post pages? Even if the content of the post pages of my old blog is moving to a new install of WP, won’t the URLs of all those old posts still start with “oneandonlyparisphotography.com/blog”? Again, I am only talking about the post pages where my valuable inbound links are, and not my old WP blog static pages. The posts currently reside under “Home” in the navigation menu of my old WP blog.

So when you recover from slapping your forehead against your palm over my silly mess, could you give me a solution that doesn’t require a bunch of 301 redirects and risk losing what little Google strength I’ve built up?