"we need a professional tool"
oh dear. Let me tell you about the time we scrapped our perfectly working SVN system and replaced it with an 'enterprise' tool that came highly recommended by a consultant and the management. .. actually, no I can't bring myself to document the horror that we endured for the year it was in place before we scrapped it and reverted to the perfectly good SVN system we had before.
Martin Fowler did a quick survey amongst the technophiles reading his blog. The results are very interesting.
The good ones are the 'unprofessional' ones. These are the ones the techies like and are much more productive with. The crpa ones are the ones that have a lot of 'administration' and 'lockdown control' associated with them, stuff like management-inspired workflows. (oh, ok, we had workflows and rules in this 'tool', to the point where you had to get a team lead to create/authorise a new design part that you could then use to checkin your code against - you could not just checkin your code or it would get lost in the mass of requirement tasks that were also associated with design parts, the idea was that we could properly control releases... never happened, total disaster, and that was when all the TLs were in the office and available to create the damn tasks!)
You can do a lot better than the features in TFS by looking around, and many of the OSS tools out there are very very good. Pick the ones you like, I recommend SVN with Jenkins build server, and redmine for task tracking. You might like Jira or CruiseControl with Mercurial.