If I have the option of using .Net
and can do data transformations
just fine in .Net, when would I need SSIS
? Is there a certain task
I have a lot of experience with SSIS from small projects to large, complex ETL. Without going into the details, this is my guidance for you:
If you are a DBA and you are not familiar with .NET, or if you are a developer quite familiar with SSIS, then you can use SSIS for small, simple, fairly straightforward extract, transform, load (ETL) tasks.
SSIS is very quirky and there are many pitfalls, gotchas, and what might be considered outright bugs. It is extremely powerful if you are intimately familiar.
C# now has TPL Dataflow. Simple performance tests put it ahead of SSIS. (eg http://mymemoryleaks.blogspot.cz/2013/10/ssis-vs-tpldataflow.html)
If you want to do anything beyond trivial, and if you can use .NET skills, use .NET instead of SSIS.
Basically SSIS has many advantages like splitting data transfer from point A to point B in smaller blocks and debug them in individually, able to access SQL Server Tables easily, work on XML data, API calls using c# scripts and saving data on DB, Read DB data and FTP on remote server and many more.
Apart from bunch of already existing BI blocks, you can also create your own customized tasks with its own parameters and outputs.
Hope I was able to add some points to the already existing answers.