To send automated renewal emails on a 30/60/90/180-day cadence with different email templates based on members' website visits, Pardot is the recommended solution:
Pardot for Email Automation:
Pardot is Salesforce's B2B marketing automation solution that can handle complex email automation requirements.
It allows you to create automated email campaigns based on specific triggers and criteria, such as website visits and renewal dates.
Setting Up Pardot Automation:
Create dynamic lists in Pardot that segment members based on their renewal dates (30/60/90/180 days).
Design and create different email templates for each segment.
Use Pardot's Engagement Studio to build automated workflows that send the appropriate email template to each segment based on the criteria.
Tracking and Reporting:
Pardot provides detailed tracking and reporting on email engagement, allowing you to monitor the effectiveness of your renewal campaigns.
Using Pardot, the nonprofit can create personalized and timely renewal emails, improving member engagement and renewal rates.
Salesforce Pardot Documentation
Trailhead: Automate Marketing to Businesses with Pardot

To create a custom Apex class in the TDTM (Table Driven Trigger Management) framework, follow these steps:
Create the Apex Class:
In Salesforce, go to Setup.
Navigate to "Apex Classes" under "Custom Code".
Click "New" and create your custom Apex class.
Ensure the class implements the TDTM framework correctly.
Create the Test Class:
Create a corresponding test class to ensure your Apex class functions as expected.
This is essential for maintaining code coverage and passing Salesforce deployment requirements.
Create a Trigger Handler Record:
Go to the TDTM Trigger Handlers tab.
Create a new Trigger Handler record and link it to your custom Apex class.
Define the order of execution and the object the trigger applies to.
These steps ensure that your custom Apex class is correctly integrated into the TDTM framework, maintaining organized and manageable trigger logic.
Salesforce NPSP Documentation: TDTM Overview
Salesforce Trailhead: Apex Basics & Database

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.
CertGod Nonprofit Cloud Consultant Guide: Advises on the importance of managing TDTM triggers during large data loads.
Salesforce Documentation on TDTM: Provides instructions on managing and disabling TDTM triggers.

To ensure that the Donor Advised Fund (DAF) receives credit for donations, using Account Soft Credits is the best approach. Here's how to set this up:
Navigate to NPSP Settings:
Go to Setup.
In the Quick Find box, type "NPSP Settings" and select it.
Configure Soft Credits:
In NPSP Settings, navigate to "Donations" -> "Soft Credits".
Ensure that soft credits are enabled for Accounts and Contacts.
Add Soft Credits on Opportunities:
When entering a donation, go to the Opportunity record.
Add a new soft credit for the DAF by selecting the appropriate Account (the financial institution housing the DAF).
Specify the role as "Donor Advised Fund" or similar.
Track and Report:
Use Opportunity reports to track soft credits and generate reports showing the contributions attributed to the DAF.
Using soft credits allows the organization to properly credit the DAF for donations without altering the primary donor records.
"Managing Soft Credits in NPSP" from Salesforce Help: Soft Credits
"Tracking Donor-Advised Funds" from Salesforce.org: Donor-Advised Funds

https://trailhead.salesforce.com/en/content/learn/modules/search_solution_basics/search_solution_basics_optimizing To improve search performance when migrating a large volume of donation data into the Nonprofit Success Pack (NPSP) for a nonprofit, the consultant should consider implementing Skinny Tables and Custom Index. Here is a detailed explanation:
Skinny Tables:
Skinny tables are a performance optimization technique in Salesforce used to improve the performance of read-only operations.
They are highly effective in environments with large volumes of data, such as the scenario described with 20 years of donation data and over 200,000 donations each year.
A skinny table contains frequently accessed fields and can significantly reduce query time.
Skinny tables are maintained by Salesforce and do not require changes to the custom object schema or existing queries.
They are particularly useful for scenarios involving complex reports and list views.
Custom Index:
Custom indexes enhance the performance of search queries in Salesforce.
Creating custom indexes on fields that are frequently used in search filters and conditions can drastically improve search performance.
Salesforce allows up to 25 custom indexes per object, which can be leveraged to optimize searches on key fields such as donor names, donation dates, and amounts.
Custom indexes should be applied to fields involved in frequently used WHERE clauses in SOQL queries.
Salesforce documentation on Skinny Tables: Skinny Tables
Salesforce documentation on Custom Index: Custom Index