Firstly migration from v11.x to v12.x using TKLBAM should be relatively straight forward although I haven't used it recently (for migration purposes) so can't be too sure whether my experience is still relevant. With some of the other appliances \ (particularly ones that include upstream software) there can be unaccounted differences eg DB schema changes that require extra tweaks, but you should be fairly safe with LAMP.
As for what changes TKLBAM 'tracks', actually it doesn't 'track' any changes. What it does is makes comparisons against the stock standard appliance. For example:
Installed packages - On restore it will install apps that were installed by apt-get BUT only if they come from the default TKL appliance repos - any from third party repos will need to be installed manually afterwards.
Configuration - It does copy across many config settings, but it ignores most hardware relevant config (such as network settings). This is pretty important as it allows you to migrate from VM to bare metal, bare metal to AWS, AWS to alternative VPS, etc.
Databases - DBs are simply 'dumped' complete and restored to the new appliance.
Files stored in 'user editable' places eg /var/www are automatically included.
So generally it should suit your purposes, as long as you don't put things in 'naughty places' - ie places that are meant to be handled by package management under the Debian FHS. My suggestion would be to read up in the docs about TKLBAM and give it a test run. I have had pretty good experience with it and some users swear by it. OTOH others have reported problems. So have a look and see what you think... If nothing else it should be enough to get you started on your new v12.x appliance as soon as your host supports it...
TKLBAM questions
Firstly migration from v11.x to v12.x using TKLBAM should be relatively straight forward although I haven't used it recently (for migration purposes) so can't be too sure whether my experience is still relevant. With some of the other appliances \ (particularly ones that include upstream software) there can be unaccounted differences eg DB schema changes that require extra tweaks, but you should be fairly safe with LAMP.
As for what changes TKLBAM 'tracks', actually it doesn't 'track' any changes. What it does is makes comparisons against the stock standard appliance. For example:
So generally it should suit your purposes, as long as you don't put things in 'naughty places' - ie places that are meant to be handled by package management under the Debian FHS. My suggestion would be to read up in the docs about TKLBAM and give it a test run. I have had pretty good experience with it and some users swear by it. OTOH others have reported problems. So have a look and see what you think... If nothing else it should be enough to get you started on your new v12.x appliance as soon as your host supports it...