I did that way too but when I am upgrading the packages are failing because of Konesans. by default konesans are not upgrading to 2008 konesans.
You have to contact Konesans people and ask them to include the so-called upgrade manifest. It is very simple document, used by the SSIS framework to map the old component version to the new. You may also try to define the manifest by yourself. For example the Trash Destination manifest looks like this:
<?xml version="1.0" ?>
Konesans SQL Server Integration Services Upgrade Mappings
Copyright © 2008 Konesans Limited
%ProgramFiles%\Microsoft SQL Server\100\DTS\UpgradeMappings\
Upgrade mapping for SQL Server 2005 to SQL Server 2008.
tag="Konesans Trash Destination"
oldAssemblyStrongName="Konesans.Dts.Pipeline.TrashDestination.Trash, Konesans.Dts.Pipeline.TrashDestination, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b8351fe7752642cc"
newAssemblyStrongName="Konesans.Dts.Pipeline.TrashDestination.Trash, Konesans.Dts.Pipeline.TrashDestination, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b2ab4a111192992b"
The manifest has to be deployed in this folder:
\Microsoft SQL Server\100\DTS\UpgradeMappings
and the file must have .xml
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/