In 2007 the decision to broaden the adoption of Scrum to all development teams forced Kelley Blue Book (KBB) to seek out a more efficient and effective Scrum tool. KBBpsilas use of SharePoint was nascent at the time and was a fine tool for several small Scrum teams. However with the total number of teams now at fifteen, SharePoint alone was just not keeping pace with the needs of the organization. Deciding to move to a more robust tool to promote agility while keeping up with product release plans can be a complicated challenge. KBB chose VersionOne to replace SharePoint. Migration to VersionOne involved numerous departments and two offshore facilities. With KBB sharing their experience of this common situation, other companies can learn about and adopt proven techniques to ensure a successful tool migration. This paper will cover KBBpsilas Scrum implementation, goals of tool migration, the selection process, migration approach, and results.