I've been thinking about this business of creating a new, blank database that has the complete environment of your old database, except with no people. For years, the wish from many users on this forum has been for a way to do a bulk delete of people from a database. There are several ways that such a feature would be useful. For example, you could just copy a database and then delete all the people from the copy of the database. Your new (and now empty) database would have the desired characteristic of having all the lists from your previous database.
RM has stated that they will never implement a bulk delete feature because of the danger that a user will do a bulk delete of everybody from their production database and not have a backup. I believe that a bulk delete could be made safe by incorporating a required backup into the bulk delete procedure. But I'm not the designer of RM and I'm not the vendor, so fair enough.
Nevertheless, I wonder if RM might consider the following to be safe enough. Suppose there was a new feature that could be invoked as File->Create blank database from current database. It would differ from the Import Lists process in that it would preserve everything from the old database except the people, including sentence template customizations from the old database. The old database would not be deleted, and indeed the old database would not be changed at all. Hence, there would be no bulk delete.
I very much appreciate the new Import Lists feature, but it doesn't completely meet the need to create a new, blank database just like an existing one except with no people. The failure to include sentence template customizations for built-in facts in the Import Lists feature is a real killer for me.