2

I have inherited a client project that involves a number of EE installs (6 in all, though some are MSMs themselves, so total number of sites is ~10) which I would like to merge into a single MSM install.

One of these installs is EE1, the rest are various versions of EE2. All use Matrix, Playa and Assets. The EE1 site could be migrated to EE2 though (the DB at least).

I'm trying to work out the best way of migrating the data (as far as I am aware there is no first party tool to import an existing site into an MSM install).

At the moment our approach is an increasing complex custom script that maps data from the columns of the old DB to the (manually created in the case of exp_channel_titles/exp_channel_data) columns in the new db. I'm concerned that this is actually such a complex task that we're going to miss something in the process though.

If you have accomplished this task in the past, how did you go about it? What approach/tools did you use etc.

2

We not merged like this, but I would probably go about it like this:

  • set up the main site
  • set up the msm sites and don't import any channels.
  • upgrade all EE1 sites (you can check license, but I'm pretty sure if you do this locally, you aren't breaking any rules)
  • use field editor from mighty big root to export the channel fields and import them into the new set up.
  • use datagrab to import all the entries etc.

It's probably the best way. Can think of unless someone else has a suggestion?

1
  • This is pretty much exactly what I was going to suggest as well. Even merging one MSM site will be a major undertaking and require a significant amount of time. Good luck.
    – CreateSean
    May 1 '13 at 23:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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