ContributionsMost RecentMost LikesSolutionsInput on best approachBackground: I want to create a CRM that flows well between the tables Companies, Contacts, Opportunities, and Activities. When for example a new opportunity is created, I'd like to choose the associated company, and have it auto-populate the contact fields First Name, Last Name, Phone (direct), Phone (mobile), and Website. So maybe I'm making this too complicated, but I was wondering if there's a good argument for choosing one vs. the other ways of structuring this as described below: Option 1 Companies is Parent table, all other tables are children of this table. Opportunities and Activities are also children of Contacts. Option 2 Companies is Parent table. Contacts is child of Companies. Opportunities and Activities are each children of Contacts, and any relevant Company details are pulled through from Companies to Contacts to Activities or Opportunities. Option 2 seems to work well, but I can see that a potential challenge is if a Company has more than one contact, that it would not know which contact to pick from, so maybe Option 1 is best and then create a conditional dropdown filtering the Contact selection based on the chosen company?