Lock In Your Account Data Model
The article explains how to enforce the NPSP Household Account data model in Salesforce using validation rules to keep contacts correctly associated with household accounts, ensuring clean data for nonprofits. It addresses the challenges of mixing household and organizational account models and offers tips to maintain data integrity even with mixed use cases. Additionally, it provides a practical solution to prevent validation rule errors during lead conversion by mapping lead IDs to contacts. Salesforce admins can use these patterns to maintain consistent data models and avoid common pitfalls in nonprofit orgs.
- Use validation rules to enforce the Household Account model in NPSP orgs.
- Apply separate validation logic when mixing household and organizational account models.
- Map Lead IDs to a Contact field to bypass validation rules during lead conversion.
- Keep contact data clean by preventing direct assignment to incorrect account types.
- Use friendly error messages to guide users on proper account associations.
I love the NPSP Household Account data model . I think it's easy to understand, pretty convenient to work with, and has stood the test of time. It takes maybe two minutes for even brand new Salesforce users to grasp that In Salesforce, all contacts must be on an account (for historical technical reasons that I usually briefly explain). In order to use Salesforce in the nonprofit context (to understand whose money a donation came from), we have the Household Account model. In this model we put all contacts directly on their Household Account. NPSP's triggers handle creating these accounts when you leave the Account field blank. We also have organization accounts (one record type or many) to which we affiliate contacts. Make It Required To keep data clean, I want to ensure that all my records stick with the household account model. So I like to have a validation rule. (You can remind people not to put contacts directly on accounts, but they sometimes forget.