Well, providing your modifications have been mostly limited to plugins, this should be fairly straightforward. Unfortunately I don’t have time to answer all of you individually, but hopefully this post will help!
Your first step should be to back up your existing Elgg install and back up the database, just in case anything goes wrong. If your current Elgg install is where you want to install your Elgg Multisite install (e.g. in
/var/www) you will want to move it out of the way before continuing.
Once you’ve backed up and prepared your installation directory, set up Elgg Multisite as documented in my previous article.
Migrating your domain
Migrating your domain to point at your new Elgg multisite domain is a two step process, and you’ll need an extra sub domain depending on your configuration.
Basically, you’ll need one domain to act as an admin domain (e.g. pointing at
/var/www), and then the domain your migrating should be pointed at the Elgg multisite docroot (e.g. in
Next, you need to visit your admin domain and add the Elgg multisite domain details in the configuration – the domain name your migrating, plus the database details of the existing Elgg database you’re importing.
On the current version of Elgg Multisite you’ll get an error at this point complaining that the database could not be created. It already exists, so this error can be ignored.
You should now have a functional vanilla Elgg install visible when you visit your migrated domain.
If you have any custom plugins which are not part of the standard Elgg install (including themes), these should be copied over at this point. You must activate them for the domain through the Elgg Multisite admin interface in order for them to be visible in Elgg’s plugin administration page.