When performing large-scale data migrations-specifically loading millions of records-performance and system limits become the primary concern. In the Nonprofit Success Pack (NPSP), almost all automation is governed by the Table-Driven Trigger Management (TDTM) framework.
The Logic of Disabling TDTM:
* Reducing Overhead: By default, TDTM triggers a series of complex operations every time an Opportunity (donation) is inserted, such as calculating rollups, creating recurring donation installments, and managing household naming. For a historical data load of 5 million records, running these processes in real-time would likely hit Salesforce governor limits and significantly slow down the migration.
* Sequential Execution: Disabling the Trigger Handlers allows the data to be loaded in its "raw" state.
The consultant can then run specialized batch jobs (like Customizable Rollups) after the load is complete to calculate the totals all at once.
* Process: To do this, the consultant navigates to the Trigger Handlers tab in NPSP and unchecks the
"Active" box for specific handlers (like OPP_Rollup_TDTM or REL_Relationships_TDTM) or uses the NPSP Settings to disable the entire framework for the migration user.
While Validation Rules (Option B) might also need to be disabled if the legacy data is messy, the most critical step for a high-volume load to prevent "Apex CPU time limit exceeded" errors is managing the TDTM framework. Option C and D are development tasks that do not assist in the immediate efficiency of a data load.