Yep, duplicate the entire system and then delete the extra portals, leaving the one you want behind. Do that for each one. You can of course also remove whatever modules are also not needed for each.

Rob

Hi nectar,

Yes, that's the general idea. It would be useful to have a spare domain already pointed to where you're going to create the duplicate system. And before you duplicate the database, add that domain as an alias for the portal that you're planning to retain. That way the correct portal will show up when you browse the domain. When you have the portal running, then you can start deleting other portals. If you forget to add the alias, you can do it directly in the db afterwards - there's a portal aliases table in there.

It works very well and I have created a bare-bones instance of my system, for testing purposes, by removing dozens of portals and around 200 modules. I ran into trouble only with one module, Datasprings Dynamic User Directory, which would not allow a portal to be deleted without first deleting a couple of tables in the db.

Rob