I have seen this occur. It's usually in queries that were problematic, but barely adequate, in the older version of SQL Server. The newer optimizer in 2012 just isn't always very forgiving of poor code choices. Many of the suggestions around statistics and indexes are good, but it's probably going to require fundamental query tuning and a rewrite to address whatever in the code is causing issues.