Skip to main content

Jordan Leopold: Should Sabres keep or move him?

by Adam Kimelman

Defenseman Jordan Leopold had been a solid contributor in his first seven NHL seasons, but hit a new gear when he signed with the Buffalo Sabres in July 2010.

Never a big offensive performer previously, he had 13 goals in 2010-11 and followed that with 10 goals last season.

However, injuries and a coaching change have limited Leopold's opportunities this season. Could it be time for the Sabres to find a new home for Leopold? examines the pros and cons to the Sabres making Leopold available to move prior to the April 3, 2013 NHL Trade Deadline:


Position: Defenseman

Age: 32

Statistics: 20 games, 1 goal, 5 assists, 6 points, minus-6

Salary status: Leopold is in the final season of a three-year, $9 million contract and can become an unrestricted free agent on July 1.

Keep him: This season's Sabres have the look of the Montreal Canadiens of last season -- a team hurt by injuries and down seasons from a number of key performers. The Canadiens have rebounded this season to become a contender for the top spot in the Eastern Conference, and Sabres general manager Darcy Regier could hope his team has the same bounce-back next season. In addition to having important core players Jason Pominville, Thomas Vanek, Ryan Miller, Tyler Myers and Tyler Ennis locked in long-term, keeping high-quality complementary parts like Leopold only will assist in the turnaround.

Move him: With the Sabres mired near the bottom of the Eastern Conference, it could be time for a full-scale overhaul. When that scenario arrives, the first players usually dealt are the ones approaching free agency. If the Sabres don't envision Leopold as part of their future, the time has come to make a deal and get something in return for a player who could help a number of teams as a second- or third-pair blueliner.


View More

The NHL uses cookies, web beacons, and other similar technologies. By using NHL websites or other online services, you consent to the practices described in our Privacy Policy and Terms of Service, including our Cookie Policy.