Nonprofit-Cloud-Consultant VCE Exam Download

To transition from Person Accounts to the Household Account model in NPSP and avoid interacting with Person Accounts, the recommended approach is to migrate to a new Salesforce NPSP org. Here’s how:

Apply for a New Salesforce NPSP Org:

Contact Salesforce to apply for a new NPSP org.

Ensure the organization qualifies for the NPSP and request the necessary licenses.

Request License Transfer:

Work with Salesforce support to transfer existing licenses from the current org to the new NPSP org.

Export Data from Current Org:

Export all Person Account data, including Contacts, Accounts, Opportunities, and any other relevant records.

Use Salesforce Data Loader or another export tool to ensure a complete data export.

Prepare Data for Import:

Clean and prepare the exported data for import into the new org.

Map Person Account data to the appropriate fields in the Household Account model.

Import Data into New NPSP Org:

Use the NPSP Data Importer or Data Loader to import the cleaned data into the new org.

Ensure that all relationships and references are correctly mapped and maintained during the import process.

This method ensures a clean transition to the Household Account model without the complications of dealing with Person Accounts in the original org.

Salesforce NPSP Documentation: Account Models

Salesforce Trailhead: Data Import Strategies

When using NPSP (Nonprofit Success Pack) with the default account model and a new Contact is created without specifying an Account Name, NPSP automatically creates an Account with a household name.

Default Account Model in NPSP:

NPSP typically uses the Household Account Model by default.

This model groups individuals into households, making it easier to manage and report on donor families.

Automatic Account Creation:

If a Contact is created without an Account Name, NPSP automatically generates a Household Account.

The name of the Household Account is usually derived from the Contact’s last name, formatted as "The [LastName] Household."

Process:

Step 1: A user creates a new Contact record, leaving the Account Name field blank.

Step 2: Upon saving the Contact, NPSP checks for an existing Household Account.

Step 3: If no Household Account exists, NPSP creates a new Household Account using the Contact’s last name.

Benefits:

Organization: Ensures that all Contacts are associated with an Account, maintaining data integrity.

Reporting: Facilitates household-level reporting and analytics.

To ensure that the status for a Campaign Member on a fundraising campaign is automatically updated when a donation is received from that Contact, the Automatic Campaign Member Management feature in NPSP can be used. Here’s how to enable and configure it:

Navigate to NPSP Settings:

Go to Setup.

In the Quick Find box, type "NPSP Settings" and select it.

Enable Automatic Campaign Member Management:

In the NPSP Settings, navigate to "Donations".

Find the "Automatic Campaign Member Management" section.

Enable this feature by checking the corresponding box.

Configure the Settings:

Define the criteria for when and how Campaign Member statuses should be updated. For example, you can specify that the status should change to "Responded" when a donation is received.

Save Settings:

Save the changes to activate the automatic updates.

This setup ensures that Campaign Member statuses are updated automatically based on the criteria defined, reducing manual effort and improving accuracy.

"Automatic Campaign Member Management" from Salesforce Help: Automatic Campaign Member Management

"NPSP Settings Overview" from Salesforce.org: NPSP Settings

To find the NPSP version number for a specific field, the consultant should reference the NPSP Public Data Dictionary. This resource provides detailed information about the fields and features introduced in different versions of NPSP.

Access NPSP Public Data Dictionary:

Go to the Power of Us Hub or the Salesforce.org website.

Navigate to the NPSP documentation section.

Search for the Field:

Use the Data Dictionary to search for the specific field in question.

Review the information provided, including the version number when the field was introduced.

Verify Field Information:

Confirm the details about the field, including any associated metadata and historical changes.

Using the NPSP Public Data Dictionary ensures accurate information about the field's history and version details.