Splitting off a multisite sub-site

Either change the directory under sites if he's just changing the URL but that doesn't seem like what you want.. OR....

Copy the DB, set it up on the new box. Go through and do a table / field level SQL replacement UPDATE query to alter the paths (particularly in the files table) so that the path's are correct. Then copy the file structure, delete all the sites's folders that are from your current multi-site stack. Then change the pathing on his site's folder to the new one.

....not that that's not a pain in the butt but unfortunately there's no real good solution that I know of for moving stuff like that. Something to do in the future (not sure how you setup ur sites folders) but I also do the com.sitefolder (in my situation everything's psu.edu so I make all the sites folders edu.courses.name) way of creating paths. That way none of the files are ever tied to a domain incase the domain changes.

Hope this helps :p

I'm also seeing some imagecache issues -- I stuck the files folder under sites/default, and now all the imagecache images in that file don't seem to show up.

(BTW, after flushing cache, I see the bootstrap errors intermittently instead of constantly -- some progress, perhaps.)

You may be able to get away with this without doing any database hackery if you simply replicate the directory structure of the site as it was on the multisite server. For example, on the multisite server, you probably had some modules in sites/all/modules and some modules in sites/example.com/modules. Recreate those directories on the new server and make sure that every module which was under the former path on the old server is under that path on the new one, and likewise with the latter path. Likewise with sites/(all|example.com)/themes and sites/(all|example.com)/files. Does that make sense? I've successfully done it using this approach before, but YMMV.

If this doesn't work, another thing you should try before resorting to hacking the database is to disable all non-core modules and themes on the old site before doing a database dump. (Don't uninstall them, as that will cause lost data; just disable them.) Then, after you migrate, re-enable the needed modules.

Hi all... I read through this post and found some issues with my site after splitting a single drupal install into a multisite install... basically, some of the themes were removed after the split. What I did was this, to figure out some items that were erroneous in the {variable} table:

First, temporarily modified bootstrap.inc after line 478.

I found errors like:
Notice: unserialize() [function.unserialize]: Error at offset 113 of 862 bytes in /var/www/www.example.com/public_html/includes/bootstrap.inc on line 479
Parsed: theme_zen_settings

I then located the offending variable and deleted the row in phpMyAdmin:

Thank you all for your ideas... Your sharing makes things easier! :)

My approach is to do an export of the SQL tables to a .sql files with the table creates and inserts. This is done through PHPmyAdmin. Then I do a one-time mass search and replace for 'site2move.mysite.com' and change it to 'site2move.com'. I use NotePad++ to accomplish this. Then I do an import of the sql tables and inserts into the new database. The final thing I have to is run update.php on the new site and save settings on my theme.