Unless the database table structures are changing, switching an SSIS job from one server to another is pretty straight forward. The configuration information for the database connections should be stored either in a config file or in a database, simiply change that connection information to point at the new server.

If the table structures are changing, CDC does not handle that automagically. See the posts on Part 1 article on example of how to update CDC with DDL changes.

CDC does have it's draw backs, to track who is making the changes you have to add user information to your tables and change the data access to save that data. Some people may not need that level of control. But if you are working on aa application that shullfes billions of dollars a year, it is pretty important to be able to answer "who made that change"?

But beyond auditing, there are other uses for CDC like ETL processing for delta updates, load use reports, etc. Still say it's cool.