When an international nonprofit adds a translated Relationship picklist value but both Relationship records are displaying incorrectly, the likely cause is that the reciprocal relationship value is missing in the NPSP Settings tab.
* Reciprocal Relationship Setup:
* In NPSP (Nonprofit Success Pack), relationships between contacts often need to be reciprocal.
For example, if Contact A is listed as "Parent" of Contact B, then Contact B should be automatically listed as "Child" of Contact A.
Reference: CertGod-NONPROFIT-CLOUD-CONSULTANT.pdf - Question 3, mentions that the issue often arises when the reciprocal relationship value is not set correctly in the NPSP Settings tab.
Configuration in NPSP Settings:
The NPSP Settings tab allows administrators to define reciprocal relationship mappings. If these mappings are not correctly defined, relationships may not display as expected.
Ensure the reciprocal relationship is added and mapped correctly in the NPSP Settings under the Relationships section.

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.
References:
Salesforce Nonprofit Success Pack Documentation
Salesforce Trailhead: Import Data for Nonprofits

Before upgrading from version 2 to version 3 of NPSP, the consultant should:
* Run NPSP Health Check: This tool identifies potential issues in the current NPSP configuration, including deprecated fields, custom objects, and other configurations that might cause problems during the upgrade.
Running NPSP Health Check ensures that the upgrade process goes smoothly by addressing any issues beforehand.
References:
Salesforce Nonprofit Success Pack Documentation
Salesforce Trailhead: Upgrading NPSP

Before embarking on a new implementation project, it is crucial to first identify the challenges the nonprofit is currently experiencing. This ensures that the new solution will address the specific needs and pain points of the organization. Understanding these challenges will guide the implementation strategy and help in configuring Salesforce to meet the nonprofit's goals effectively.
Steps:
* Conduct stakeholder interviews to gather information on current processes and challenges.
* Analyze the data collected to identify common themes and pain points.
* Document the identified challenges and prioritize them based on their impact on the organization's mission and operations.
* Use these insights to define the scope and objectives of the new implementation project.
References:
NGO Ebook CRM For Good: Emphasizes the importance of understanding current challenges before starting new projects.
Nonprofit Cloud Implementation Guide: Provides best practices for identifying and documenting challenges to inform implementation strategy.

To identify organizations that have donated to the nonprofit in some year prior to the current year but have not contributed in the current year, the NPSP SYBUNT (Some Year But Unfortunately Not This year) report can be customized. Here's how to do it:
* Navigate to the NPSP SYBUNT Report:
* Go to the Reports tab.
* Find and open the NPSP SYBUNT report template.
* Customize the Date Range:
* Click on the "Filters" pane.
* Adjust the date range filters to include donations from the desired prior years and exclude the current year.
* Modify Report Criteria:
* Ensure the report is filtering by Account to get the organization-level data.
* Add additional filters if necessary to refine the report (e.g., specific campaign or donation types).
* Run the Report:
* Save and run the report to get a list of organizations that have donated in previous years but not in the current year.
By customizing the date range on the NPSP SYBUNT report for Accounts, you can easily identify and target these lapsed donors for re-engagement campaigns.
"Using NPSP Reports" from Salesforce Help: NPSP Reports
"SYBUNT and LYBUNT Reports in NPSP" from Salesforce.org: SYBUNT and LYBUNT