In the new Nonprofit Cloud, the "Household" concept is managed using the Group (Account) and Account Account Relationship model, underpinned by Person Accounts for individuals. This is a departure from the NPSP "Household Account" model.
To handle complex, modern family structures—such as children living in two separate households (split families) or blended families—the consultant follows a specific workflow:
Individual Representation: Every family member is created as an individual Person Account. This ensures that their data (milestones, benefits, medical records) stays with them regardless of which household they are currently associated with.
The New Group Flow: Salesforce provides a standard, guided flow called the New Group flow. When a consultant or caseworker uses this flow, it automates the creation of a "Business" Account with a record type of Group (representing the Household). It simultaneously creates the Account Account Relationship records that link the individual Person Accounts to that Group.
Handling Split Families: Because the system uses a junction-based relationship model (Account Account Relationship), a single child (Person Account) can be linked to multiple Group Accounts (Household A and Household B). One can be marked as the "Primary" household, while the other is "Secondary."
Role Definition: Within these relationships, you can specify roles (e.g., "Parent," "Dependent," "Step-Parent") using the Party Role Relationship configuration.
Option B is insufficient because while it tracks person-to-person ties, it fails to aggregate the individuals into a "Household" unit (Group) for reporting and program enrollment. Option C is incorrect because it suggests using the legacy Account/Contact model, which is not the recommended best practice for individuals in the modern Nonprofit Cloud.
