We've just gone through a cluster migration project and used the approach you outline. One thing you may find is that if you change the startup parameters of SQL Server via Configuration Manager, e.g. change the location of where master.mdf resides, the Config Manager information and the Registry information on each cluster node can get out of synch.
This can be prevented by following the instructions in this link: http://support.microsoft.com/kb/912397
We were migrating to a new server so we also had the problem of the new server containing the old server name when 'SELECT @@servername' was executed. We had to drop the old server name and add a new one.
Another issue is that the msdb subsystems may now be in a different physical location so the contents of the msdb.dbo.syssubsystems table must be deleted and the susbsystems reinitialised using 'EXEC dbo.sp_verify_subsystems 1'
Lastly, if you are moving servers, be sure to backup the Service Master Key and then restore it using the FORCE option on the new server.