It will require you starting with one of the appliances and then adding/installing the funcionality of the others. There is no tutorial on how to do this, and without doing it myself I can not guide you. You are on your own if you wish to go down that path (although I am more than happy to help where I can). Where this becomes particularly painful is Zimbra; as it is only available as a TKL legacy applliance. The others are all available in the latest v11.x. You could start with the Zimbra appliance and add the others, but that will only give you ~12mths of support left, so you will need to do it all again in the near future. The main reason the devs haven't released an updated Zimbra appliance AFAIK is because Zimbra no longer supports 32bit OS (which TKL currently is - 64bit builds, along with an updated Zimbra should come next release).

So assuming you are planning to use your own hardware, a much. much beter way to go IMO is to install a hypervisor OS (such as ProxmoxVE) to your hardware. Then you can install the various appliances as separate VMs. There are a number of advantages to going this direction. Some of the ones that spring to mind are:

• Portability - The VMs are easily migrated from VM to hardware, or to alternative hardware hypervisor (using TKLBAM). You could migrate just one, or all of them...
• Reduced backup size and complexity - Assuming you were to use TKLBAM, backups will be smaller (in total - as only data & config for each specific appliance needs to be stored).
• Scalability - Resources can be matched to each VM according to it's needs and one app won't be able to  rob resources from another. Ie resources can be formally allocated to each VM.
• Easily tweak and tune each app - without negative or unintended impact on others.
• Redundancy - If one app chokes/crashes/breaks etc, it won't drag all the others down too.
• Upgrade/update path - You can update each appliance indivudally thus spread out your workflow and ensure that each one is working well before going to the next.
• Opportunity to test other appliances on the same hardware similtaneously (assuming you have left over resources).

Obviously there are some downsides too (many of the above points have inherant counter points) although personally I think the good outweighs the bad. The only one that I think may be a deal breaker were if you are planning on using AWS. Using VMs is not supported on AWS, so were you to migrate your appliances to AWS, then each would need to be independant, thus increasing the cost.

If you go for ProxmoxVE then you can set it up so it can download TKL OVZ templates directly from within the WebUI. Have a look here. Zimbra is the only one that isn't available as an OVZ template (because it's legacy) but you can download the ISO and install from that.

I like your idea of running TKL appliances as VMs from a base OS, but Proxmox VE requires a 64-bit processor and 1 GB of RAM. My system is 32 bit w/ only 512 MB RAM. Any suggestions?