Even if we exported the SSIS package with Integration services and edited the XMl to point to the new server name?

Its weird because the new instance name is the same as the old one in everyway. We even have a CNAME entry in DNS so we can refer to it via its old clustered name so we didn't have to reconfigure every client application.

The connection on the new instance is still pointing to the correct name (in this case the CNAME in DNS)

Let me clarify. We moved from a clustered instance to a single instance. The old virtual network name for the instance was something like 'sqldb1vs1\instance' so we installed SQL on a new box and migrated everything across, we then renamed the old clustered instance network name to 'oldsqldb1vs1' and added a CNAME DNS entry to point 'sqldb1vs1' at the new server. This works fine and all client applications are now being directed to the new install. We exported the maintenance plans with integration services and made sure the connection string was still correct and imported them to the new instance. Backups work, just email is a little off. Its sending me the email from the old instance to 1 email address but when it sends to me i get the correct message (with the updated email body)

So to summarise the connection string is correct as backups are being made on the new instance. Just emails are confused.