title: Best Strategy or tools for migrating from VB6 to .NET/.NET Core
body: <p>My company has tons of <em>legacy</em> applications that are written in VB6.</p>
  
  <p>We are in transitions from moving VB6 applications to .NET (3.5 specifically).</p>
  
  <p>What would be the best strategy for moving form VB6 to .NET?</p>
  
  <p><br />
  <br />
  <strong>NOTE</strong>: Below update should go to "Project Management" and has nothing to do with the main question.</p>
  
  <blockquote>
    <p><strong>[UPDATE]</strong>: Thank you for your feedback so far<br /> Now there are
    more question that pop up are </p>
    
    <ol>
    <li>how would you assign developers to develop new applications?</li>
    <li>Should there be a special one-time upgrade division that will convert
    legacy apps to new ones? Or should
    every developer participate on
    conversion process?</li>
    <li>Should only senior developers participate on conversion?  Junior
    developers? or mixed?</li>
    </ol>
    
    <p>It seems like, the more I think about
    this problem, more questions just show
    up.</p>
  </blockquote>