How to Select the Correct Data Structure in Salesforce for your Nonprofit: Account to Contact
Salesforce is an extremely pliable database, which allows for a number of different configurations across multiple industries. This is the first in a series of three blog posts that will take an in depth look outlining your options and what selecting each will mean for your nonprofit. Like any database, Salesforce has limitations which are dictated by the architectural “structure” you choose. In the simplest terms, there are three structures that Salesforce provides: Account to Contact, Individual Account and Person Accounts. The challenge is to select the right structure for your organization. It is important to note that there is no perfect structure, but some choices are better than others. The selection of data structure is significantly important as it relates to the nonprofit space. This series will cover all three structures with a brief breakdown of their respective strengths and weaknesses.
Account to Contact (Household and Organization):
This structure is primarily utilized for the private sector and is the original structure installed by Salesforce. As NPOs start to see the benefits of this structure, more and more organizations are adopting it.
Data Entry and Usability
Data entry is a bit slower for NPOs due to the need to create a Household and a Contact with every record. Salesforce Help and Support is much easier to utilize since the tables have not been adjusted.
The simplest of the three structures. This is due to the fact that it has not deviated from the original structure installed by Salesforce.
Includes the simplest data migration requirements of the three Structures. Usually reduces data migration time by about 15% over other structures. This is largely due to the fact that there is no need to migrate data to the Household custom object. Moreover, the data import wizard can be utilized by the client as long as there are not donations or custom objects that require migration.
100% integration with applications. In other words, all applications on the AppExchange can integrate with this Structure.
This structure is the friendliest for integration with third party solutions. Due to its architecture, you cannot link a Contact to an Organization AND a Household at the same time. This can cause challenges with physical mailings resulting in a longer process to produce reports for mailing houses.
NOTE: Account to Contact with Apex Modification:
This structure is utilized for the Nonprofit Starter Pack (NPSP) designed by Salesforce. This is a hybrid structure that blends the Person Accounts and the Account to Contact structure. Essentially it has all the same benefits as the Account to Contact structure but it does recognize individual records within a household. In other words the household bundles all the contacts into a single record (i.e. John and Susie Smith rather than John Smith and Susie Smith of the Smith Household). This is advantageous for data entry but it does not allow the user to recognize individual emails, snail mail and phone numbers for campaign functionality.
What questions do you have about this data structure or what to look for when selecting an option in Salesforce? Let us know in the comments below!