Do duplicate and matching rules run while the migration loads?

The principle underneath this one: identity should be decided exactly once, by humans, before the load — not re-litigated row by row, mid-load, by a matching rule. Nonprofit data makes the point sharply: spouses sharing an e-mail address, families giving through one account, generations of slightly-different name spellings. The pre-load identity review resolves each of those groups — same person, or different people — with the context a rule cannot have. If the target’s duplicate rules then run against the migration user, they second-guess that finished review: legitimate records get blocked or flagged mid-load, a load step stops without reconciling, and the team ends up doing identity twice under worse conditions.

Hence the standard choreography: duplicate and matching rules bypassed for the migration user only, loads run against a settled identity map, and the rules switched on — tuned for Person Accounts — before real users start entering records. The honest exception is an unfinished review: if shared-e-mail groups are still unresolved when the load window arrives, rules-on is the safety net you chose by not finishing — slower and noisier, but safer than loading unreviewed identities at speed. The better plan is simply to finish the review first; it is also the item on the critical path most often underestimated.

When Horus Eye assesses an NPSP org, this question is raised with the evidence the scan saw — the record types, fields and settings behind it — its recommendation marked, and the reasons stated. Accept records the recommendation; Change opens the options. Recording an answer writes nothing to Salesforce: it is captured in the decision register, with who decided and when, and the migration plan, mappings and documents are kept consistent with what your organization actually decided. Horus Eye recommends; your organization decides.

• 1. Salesforce · Agentforce Nonprofit Migration Guide v2.0 (PDF) — The official guide this content follows: platform differences, migration recommendations, and how NPSP features map to Agentforce Nonprofit. ↩︎
• 2. Salesforce Help · Enable Person Accounts for Fundraising — The enablement step — and why it is planned, not casual: Person Accounts cannot be disabled once enabled. ↩︎

“Salesforce”, “Agentforce” and related marks are the property of Salesforce, Inc. Horus Eye is an independent product and is not affiliated with, endorsed, or sponsored by Salesforce, Inc.