I've never used Perl, but the parent makes a very good point. Why move unless you have a problem?
This topic is already full of fanboys touting thir favourite tool, but one man's meat is another's poison. You already know the options (Perl, Java, PHP, Python, C#, etc) - if you don't, you're not ready to make a decision yet - so what you really need is a decision-making process.
List out all of the things that might matter to you: team skills, staff availability, platform dependence, maturity of platform, speed of development, ease of maintenace, cost, execution speed, availability of hosting, etc. You should know what those things are; if you don't you're not yet ready to make a decision. Give each attribute a weighting from 1-5 that reflects your business priorities.
Now score each language against each attribute. Sometimes you'll have to guess, but that's not going to be too much of a problem. 1-5 is a good scale; anything else will be spurious accuracy.
Now total the scores and weight them. Keep the top 3 options and look at them more closely. Was your scoring accurate? Do you trust the result? This is where your professional judgement takes over: a scoring model can only get you so far.
Do this, and you'll find out what _you_ really need, and not what some random guy on