EE2 MSM ---> separate installs, upgrade to EE3

I don’t think you can do that easily, i.e. in the form of a “normal” upgrade. Even though you have separate outward-facing sites, it’s still a single EE installation with a common code base. Just curious, how many sites are there?

If I absolutely had to do this, I’d pull the remaining (i.e. not-to-be-upgraded yet) sites out of the existing install, put them into a separate EE2 setup and upgrade the rest to EE3. Depending on your setup, simply cloning the database and deleting unwanted sites might work, but this certainly has the potential of becoming messy. Plus, you’d lose all content shared between sites, though that might not be an issue in your case. Whatever you do, I consider thorough testing compulsory. On top of all that there might be licensing issues (the MSM is part of EE3 now, but each site needs to be licensed) as well, even though I’m in no position to comment on that.

Honestly? I’d hold back on upgrading just yet, at least in production. There is, of course, nothing wrong with cloning your setup on a staging server and kick EE3’s tires somewhat 😊

The sites have to be separated if any are upgraded. The upgrades are sold as a bundle, not individually.

Each MSM site has a separate database, only some things are shared, such as members.

But the problem is that the process of separating the MSM sites is simply not in the documentation. This is a problem.

Has anyone done this? Can anyone provide any information from experience on deconstructing an MSM site to separate sites.

I’d drop an email [email protected], they’ll be able to figure out your best option on this one.

In the absence of documentation and other user experience, I suppose that will have to be done.

To be clear, that’s not an application support action, so our team would be able to best help you and answer your questions via email.