I assume that you're on a fairly Agile project if you're into continuous integration and automation.
The move from VSS to SVN will already make you very popular with the kind of developers you want to keep on your team. Do it. My developer friends will kick me if I don't mention Mercurial and Git too, but honestly, SVN's pretty simple and a really good start. TortoiseSVN is a useful graphical interface.
For keeping track of ongoing work and bugs, electronic boards like Rally's and Version One's are very popular (Rally aims to be useful for developers, while PMs seem to like the control that comes with Version One, so it depends who you're using it for). This could either be stand-alone or mirror a physical board for the team. They can also be useful for keeping track of whole project portfolios, and I believe both provide free trial licences for single teams.
You'll need a different tool if you also have to triage user complaints / bugs, etc., and if it suits your context better it's perfectly OK to play a bug-tracking tool alongside a board. Trac is fine. I've used Jira. Others who've tried to use the Grasshopper plugin as a project management tool / electronic board have struggled, so I can't advise doing that.
For continuous integration, TFS hasn't had the best reviews from developers. You may want to try something like CruiseControl.NET, TeamCity, or even start with something lightweight like Jenkins. Move to a more powerful build tool if you really need to - most of the learning devs do here is about what needs to go where in what form, rather than the build tool itself, so it should be reasonably quick to change if required.
Another good thing about most of the tools I've mentioned here is that they're free. As with any big movement to a new tool set, I recommend that the developers try some different things out on a typical project and see which one suits them best. You also avoid tying yourself to a single platform, so if any one aspect of this doesn't work out for you, you can change it later. You may also be able to play some of these into TFS if you choose to go down that path.
As a note to yourself and anyone else reading this, please try to help the developers pick the tools which suit them, and ask their advice about this too (you may also want to try this question on programmers.stackexchange.com). If you have to work around their tools a bit to get the information you need, at least you know they'll be more effective as a result.