title: Database architecture customer management
body: <p>I have developed a working mvc asp.net application (using EF).
  I have a Database Table Customer with relationship to Person table
  Person table has a field AdditionalContactInfo and Demographics</p>
  
  <p>A new feature to implement issome kind of marketing system with Leads and Prospects.</p>
  
  <p>My question : 
  - Do i put Leads and Prospect in the Customer Table and use a flag for CustomerType or is it better to create two new Tables Leads and Prospects?</p>
  
  <ul>
  <li>In case of second option how to convert lead/prospect to customer </li>
  </ul>
  
  <p>Maybe there's a better option i didn't thought of.
  Some UML or database diagrams of customer management would also be great</p>
  
  <p>Thx</p>