Skills-based training systems tend to be standalone systems, or are networked to a small number of like platforms through reflective memory or Scramnet-like devices. Architecturally, skills-based and collective training systems share several attributes, some of which can conflict with attributes required to migrate to a distributed collective training environment. Emerging programs are rapidly moving away from expensive, proprietary hardware solutions to commercial-off-the-shelf solutions based on commodity PC-based products. This paper examines the architectural differences between existing, tightly coupled skills-based training systems and loosely coupled distributed collective training systems. In addition, the approach used to migrate an existing skills-based simulation system to a distributed infrastructure environment and the attendant lessons learned are reviewed.