What would be the best practice for transferring from flat file to sql? : So, I have recently been tasked with transferring an old Flat File System Scheduling system into a SQL Database using C#.

The main issue I am finding is the fact that the tasks (See snippet below) use a List of strings (Created using GUIDs) has made me unsure of how to structure the database.

    public class Task
    {
          private string TaskID;

          private string TaskName;
          private string TaskDescription;

          private bool IsComplete;

          private DateTime EstimatedStartDate;
          private DateTime ActualStartDate;

          private DateTime EstimatedCompletionDate;
          private DateTime ActualCompletionDate;

          private string TeamLead;
          private List<string> TeamMembers = new List<string>();

          private TaskType TaskType;
          private string ParentID;
          private List<string> ChildIDs = new List<string>();
    }

When it comes to SQL I know that using list that can only be contained in a single Cell are generally a nono, the real question is should I be having this in a list where the query will only have to query the taskID or parentID to find the requested task OR to have it split into different tables for each Category in the system (This works in 4 different Categories) and then dependant on the task's type and taskID to choose the correct table it will need to query for its children.