The procedure explained here would not precisely work this way. Also, I would highly advise to shut down the old Tiki into Maintenance Mode first, so that no "last minute changes" would get lost when the DB gets transferred.
After you transferred the files and the DB, you will see a seemingly (!) fully operational Tiki under the new URL, but beware, this is because the new Tiki will reach into the old DB, because it has server/user name and password to do so, and unless your ISP provides some protection against cross-accessing (or you switched ISPs) you get the illusion (!) that it works. It does, but it will continue to use the old DB.
The transfer of a working Tiki means pointing to /tiki will not bring up the installation, because it gets disabled when Tiki goes into operational mode! So either you have to re-activate the install script (which gets deactivated for a VERY good reason: Security!) or you have to enter the new DB access data in the "working" Tiki...
The procedure explained here would not precisely work this way. Also, I would highly advise to shut down the old Tiki into Maintenance Mode first, so that no "last minute changes" would get lost when the DB gets transferred.
After you transferred the files and the DB, you will see a seemingly (!) fully operational Tiki under the new URL, but beware, this is because the new Tiki will reach into the old DB, because it has server/user name and password to do so, and unless your ISP provides some protection against cross-accessing (or you switched ISPs) you get the illusion (!) that it works. It does, but it will continue to use the old DB.
The transfer of a working Tiki means pointing to /tiki will not bring up the installation, because it gets disabled when Tiki goes into operational mode! So either you have to re-activate the install script (which gets deactivated for a VERY good reason: Security!) or you have to enter the new DB access data in the "working" Tiki...