Salesforce Salesforce Certified Nonprofit Cloud Consultant (NPC) NP-Con-102 Nonprofit-Cloud-Consultant Exam Dumps: Updated Questions & Answers (December 2025)

https://trailhead.salesforce.com/en/content/learn/modules/nonprofit-success-pack-administration-basics/understand-the-npsp-data-model

For nonprofits needing to track key information related to grants, such as deadline dates, activity completion dates, and descriptions, Deliverables within Salesforce are the recommended feature. Deliverables allow nonprofits to create and manage detailed records of grant-related activities, set deadlines, and monitor progress directly on the Opportunity object.

Steps:

Enable Deliverables in Salesforce.

Create Deliverable records to track grant-related tasks, deadlines, and activities.

Configure Deliverables to display the next deadline date on the Opportunity.

Use reports and dashboards to monitor the status and progress of grant-related activities.

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.

After using the Conversion Utility tool to convert an NPSP account model from One-to-One to Household, the consultant needs to manually select a Primary Contact for each Household Account. Here’s the detailed process:

Run the Conversion Utility Tool:

Navigate to NPSP Settings.

Under the "Bulk Data Processes" section, find and run the Conversion Utility tool to convert One-to-One Accounts to Household Accounts.

Review Converted Records:

Once the Conversion Utility tool runs successfully, review the newly created Household Accounts.

Each Household Account should have the associated Contacts correctly linked.

Select a Primary Contact for Each Household:

Go to each new Household Account.

Manually select a Primary Contact from the list of related Contacts. This step is crucial as the Conversion Utility does not automatically set the Primary Contact.

The Primary Contact field is used in many NPSP features and reports, so ensuring it is correctly set is important.

By performing this manual action, you ensure that the data integrity and functionality within NPSP are maintained after the conversion.

Salesforce NPSP Documentation: Convert One-to-One Accounts to Household Accounts

Salesforce Trailhead: Manage Households in NPSP

The most efficient way to install NPSP in an existing Salesforce organization is to use the NPSP Installer. Here’s how to do it:

Access the NPSP Installer Page:

Go to the NPSP Installer page: NPSP Installer

This page provides the latest version of NPSP and installation instructions.

Initiate the Installation:

Click on the installation link for the latest NPSP version.

Log in to your Salesforce org where you want to install NPSP.

Follow the Installation Wizard:

Follow the prompts in the installation wizard to complete the installation.

Choose the appropriate options based on your organization’s needs (e.g., data model selection, configurations).

Complete Post-Install Instructions:

After installation, follow the post-install instructions provided in the documentation. This might include configuring NPSP settings, setting up users, and data import processes.

By following these steps, you can ensure that NPSP is correctly installed and configured in your Salesforce organization.

"Installing NPSP" from Salesforce.org: Installing NPSP

"Post-Install Configuration" from Salesforce Help: Post-Install Configuration

When loading a large volume of data, such as 5 million donation history records, into Salesforce, it is essential to temporarily disable TDTM (Trigger Handler Framework) to ensure the data load is successful. TDTM triggers can slow down or interrupt the data load process due to the large volume of records being processed.

Steps:

Go to Setup > Custom Metadata Types.

Select "Trigger Handlers."

For each trigger handler, uncheck the "Active" checkbox to temporarily disable it.

Perform the data load using Data Loader or another data import tool.

Once the data load is complete, re-enable the TDTM Trigger Handlers by checking the "Active" checkbox for each trigger handler.

To avoid manually entering information twice and ensure it appears on both the Opportunity record and the Payment record, follow these steps:

Create Payment Mappings in NPSP Settings:

Navigate to NPSP Settings.

Go to "Donations" and select "Payment Mappings".

Create mappings to ensure that relevant fields from the Opportunity record are automatically populated in the Payment record.

Create Custom Fields on the Payment Object:

Navigate to Setup.

In the Object Manager, select "Payment".

Click on "Fields & Relationships".

Create custom fields that correspond to the Opportunity fields you want to map.

Ensure the field types match those on the Opportunity object to facilitate accurate data transfer.

These steps automate the data transfer between Opportunities and Payments, reducing manual entry and ensuring consistency across records.

Salesforce NPSP Documentation: Payment Mappings

Salesforce Trailhead: Custom Fields

Changes to Engagement Plan Templates in Salesforce only affect newly created Engagement Plans. Here’s why:

Template Changes Application:

When an Engagement Plan Template is modified, the changes are not retroactively applied to existing Engagement Plans. Only new plans created after the modification will reflect the changes.

Create New Engagement Plans:

For the development manager to see the changes, new Engagement Plans need to be created using the updated template. Existing plans will retain the configuration they had at the time of creation.

Communicate Changes:

Inform relevant stakeholders about this behavior to manage expectations and plan accordingly. Consider cloning existing Engagement Plans if updates are necessary, applying the new template configurations.

Review Documentation:

Refer to Salesforce documentation on Engagement Plans for detailed information on how templates and plan instances work.

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 setting up the process for importing lists of Contacts into Salesforce Campaigns using the NPSP Data Import tool, it is essential to consider how Campaign Members are created and matched.

Key Considerations:

Automatic Campaign Member Creation (A):

The NPSP Data Import tool will automatically create Campaign Member records for the imported Contacts with the default Member Status. This helps streamline the process of adding members to campaigns.

Exact Name Matching (D):

Existing Campaigns in Salesforce are matched by exact Name. This means that the names in the CSV files must match the names of the Campaigns in Salesforce exactly for the import process to associate Contacts with the correct Campaigns.

Steps to Set Up:

Prepare CSV Files:

Ensure that the Campaign names in the CSV files exactly match the names of the Campaigns in Salesforce.

Include all necessary fields to map Contacts to Campaign Members.

Configure NPSP Data Import:

Navigate to NPSP Settings -> Data Import.

Ensure the settings align with the import requirements, including handling duplicates and respecting duplicate matching rules if enabled.

Perform Dry Run:

Use the NPSP Data Import Dry Run feature to validate the import configuration and ensure that the Campaign Member Status and other settings are correctly applied.

To send a mailing to all clients and track who was sent the invitation and who responded, you should use Campaigns in NPSP. Here’s how to set it up:

Create a Campaign:

Navigate to the Campaigns tab.

Click "New Campaign" and fill out the necessary details such as Campaign Name (e.g., "Workforce Development Program Invite").

Filter List View for Clients:

Go to the Contacts tab.

Create a new list view or filter an existing one to include only clients. This might include adding filters for criteria that identify clients, such as specific Account Record Types or custom fields.

Add Contacts to Campaign:

Select all the clients in the list view.

Use the "Add to Campaign" button to add these Contacts to the previously created Campaign.

Track Responses:

After sending the invitations, track responses by updating the Campaign Member Status. This can be done manually or through an automated process if you have integrated email tracking.

Create a Campaign Report:

Go to the Reports tab.

Create a new report using the "Campaigns with Campaign Members" report type.

Filter the report to show the specific Campaign and the statuses of the Campaign Members (e.g., "Sent", "Responded").

This process ensures that the nonprofit can track who the invitations were sent to and who has responded, providing a clear view of the engagement for the workforce development program.

"Campaign Management in NPSP" from Salesforce Help: Campaign Management

"Creating and Managing Campaigns" from Salesforce.org: Campaigns Guide