I was dissappointed that this article didn't touch on the sort of dramas I've experienced with moving DTS packages between servers.
Once you move a DTS package, you might have to change it references to server, database, tables or files, and if it notices anything is (temporarily) invalid, it wants to wipe out the transformations. You cannot edit invalid transformations to figure out what it is supposed to do and fix the real problem.
I thought that saving as Visual Basic (under SQL2000) offered more hope. At least then you have something you can look at if there are inconsistencies. Also, you can do global replace for things like database name.