Folder export/import will round trip many objects from a folder or a tree of folders, but its not sufficient to replicate an entire LabKey Server. You need to use database backup/restore to round trip all data in the labkey database, so that every module's data is copied to your new system. Also, if you have important data in the file system (assay results, file uploads, etc.) you'll need to replicate that to the new system as well.

By "vLabKey15.2-39071.18-bin" I assume you're referring to a LabKey Server distribution file (typically it would end in .zip or .tar.gz). This is a single, binary distribution that includes a specific set of modules and no source at all. A couple options, once you've replicated the database and the files to the new system:

• If the vLabKey15.2-39071.18-bin distribution includes all the modules you care about, simply deploy it on the new system.
• If you need additional modules, you could deploy vLabKey15.2-39071.18-bin and then add the extra modules to externalModules.
• Build an official distribution from source. As we discussed, you can create and build custom distributions from source. Sync up to the release15.2 branch, copy one of the existing xml files in $LABKEY_HOME/server/distributions to "lewis.xml", edit the file to add/remove modules and specify the desired format, and then run "ant dist -Dname=lewis". You now have a standard distribution you can use on every server, ensuring a consistent set of deployed modules. (As a convenience, the /distributions directory can appear inside a custom module directory as well.)

Adam