Jake Shelton (2/13/2014)
I find it extremely strange that a migration should be estimated to take a week. With enough preparation you could have this done less than a day.
I have completed several hundred migrations, with DTS, SSIS and very large dbs and none of them have taken longer than 4 hours.
We have almost a couple of hundred packages that need to be converted, albeit not too complex (2 connections and 2-3 steps). I have anticipated it'll take considerably longer than my example. I'd be curious to know how to accelerate the process.
That may be true, but DTS to SSIS migration can and should (IMO) be treated as separate migrations to the SQL engine itself.
You can leave the existing DTS migrations as a project which can be tackled in smaller, bitesize chunks and means the SQL Server and related processes are available within hours and not days. The existing DTS packages can be left running against the newly upgraded SQL Server (you may have to change internal connection strings).