<p>My team has been using SVN for a few years. We now have the option of switching to Perforce.</p>

<p>What would be the benefits (and pitfalls) of making such a switch?</p>

I currently use both on different projects.
The perforce branching mechanism is superior.
The perforce conflict resolve tool is better.
I really like perforce's strong notion of a changelist.
Perforce seems faster.
It's easier to set up and get running.
Some of our members really like the MS Office plugin for perforce, I'm on a Mac so I can't use it.
But
The SVN clients are better, especially the eclipse plugin.
Perforce is more expensive.
These are merely opinions, so perhaps this is a poor answer :)
If I was already using one or the other, I'd be very hard pressed to switch since neither seems to offer really significant benefits over the other, but the disruption in switching could be large.
Update: Since writing this, I've completely switched to using GIT for both personal and commercial purposes.  I would pick it over either SVN or Perforce any day.