ok, here's an overview as this is a bit of a tall order:)

i need to migrate our entire site into wp. right now we're just using wp for a blog page (installed in subfolder w/ subdomain), and all other pages are static in the root of the site.

i want to get all of this combined into one wp install for our main site, blog, and international sites.

here's what i'm doing now -

  • test wp multisite installed in subfolder of root
  • migrated existing wp posts, plugins, and static pages into multisite (one site for main site, another for uk site)

once i have all content migrated into my multisite install, what is the best way to handle making it live? there are some files and folders with other subdomains pointing to them in the root that exist outside of wp and can't be moved / changed.

I was thinking i would,

  • point mysite.com to my test multisite install subfolder and change my site url in wp to mysite.com
  • point my uk domain to my test multisite install subfolder and change my site url in wp to mysite.co.uk

is this the best way to go about doing this? also, what would be the best way to keep my top domain pointing to all of my other static content in my root? should I just drop all of those static files into my multisite install folder? can putting those other files in my wp folder mess up my install?

this is a complex job and i'm looking for the best way to do it with minimal headaches (although i kinda have one now after posting this:)!

thanks so much!!!

  • The whole point of having a CMS is not to use static pages. Will you be moving the content from static pages into WP?
    – Steven
    Aug 15, 2011 at 21:38
  • yes, i've moved all of my static pages into wp pages, but there are a lot of files in my root that need to stay there (used for clients and other internal needs). i've been doing a lot of reading and i think i may just have to move my multisite install to the root with all of the other files when complete. i'm just hoping that it works this way - mysite.com (goes to my new wp site) mysite.com/oldfile (still goes to the old file in my root where my wp install is) mysubdomain.mysite.com (still goes to my old subdomain) should it work this way? thanks!
    – scvdlk
    Aug 19, 2011 at 19:46

1 Answer 1


Moving all content that is just pure text information into Wordpress is step one.
You must choose if you want to create pages or posts for this content.

As a basic rule (for me), the pages generates the navigation structure for my site, and posts are articles. So one page may list several articles.

Then you might have PHP files that generate content by them selves. E.g. retrieveing data from custom DB.

For these pages, you create custom templates. The easiest way is to add the following at the very top of your PHP pages that needs to be kept as theu are:

  Template Name: You custom template name

Then of course add the header, left section, footer etc.

Inside WP just create a page and select the corresponding template.

In this way, you can easy update "static" content by editing pages / posts, and for the custom tempaltes I guess the data needs to be altered in DB or whereever you get the info.

It's the same process for single and multisite.

  • thanks so much for getting back. yes, i've created a set of templates for some of my static pages. my main concern now is moving multisite to my root with all of my older files. can a wp install be mixed in with other non-wp files? are there any docs on moving multisite? i've seen the 'moving wordpress' docs, but didn't find anything specific to moving multisite. thanks again!
    – scvdlk
    Aug 31, 2011 at 19:31
  • You only have two options. Install WP and enable multisite. Then you can either A) move conten manually or B) create or find a script that reads the content of existing site and inserts it into the proper wp multisite. There are no problems mixing "non-wp" files and wp-files. E.g. I've got custom tempaltes that are using custom created libraries / classes. No restrictions there.
    – Steven
    Sep 4, 2011 at 18:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.