How SmartIMPORT Manages Duplicates and Matching for Continuous Data Flow

How SmartIMPORT Manages Duplicates and Matching for Continuous Data Flow

Duplicates and Matching for Continuous Data Flow

SmartIMPORT uses a flexible, rule-based matching engine designed to keep your data flowing into Raiser’s Edge NXT. Instead of stopping an entire import when a potential duplicate is found,
SmartIMPORT processes every record, giving you full control and visibility without creating data bottlenecks.

Here’s how the matching process works:
  • Blackbaud's Check First: As its first line of defence, SmartIMPORT runs each record through the built-in Blackbaud duplicate check.
  • Cascading Match Rules: If no match is found, SmartIMPORT automatically runs a cascade of custom matching rules that you define. You can choose from our comprehensive suite of over 40 checks (e.g., 'Name + Email', 'Name + Postcode', 'Constituent ID', etc.). The system runs these rules in your preferred order until a match is found.
Handling New Records -
If, and only if, none of your matching rules find an existing record, SmartIMPORT creates a new constituent.
You can configure the import to automatically apply a specific constituent code, like 'NEEDS REVIEW', to all newly created records. This simple flag makes it easy to find and manage them later.

The Benefit: From Manual Import to Simple Review -
This process transforms your team's workflow. Instead of spending hours manually importing data, your work shifts to a simple, periodic review of new records flagged for follow-up. You can then use the built-in RE NXT merge tools or simply update their constituent code.
The primary benefit is that your data is never held up. Gifts, event registrations, and mailing list updates are in Raiser's Edge immediately. Your colleagues can run reports 24/7, knowing the data is accurate and up-to-date, while your team maintains data quality at your own pace without ever disrupting that live data flow.

    • Related Articles

    • SmartIMPORT: Data 'Mappings' Guide

      Understanding Mappings (Dictionaries) Note for Omatic Users: In SmartIMPORT, we use the term Mappings. These are the functional equivalent of the Dictionaries you may be used to in other import tools. Why Map Data? External data is rarely perfect or ...
    • SmartIMPORT: Custom code features

      There are two custom code options within SmartIMPORT. First, the 'Start code' block runs at the start of the import process with the spreadsheet row data available. Second, the 'Search code' which runs just after we have searched for a matching ...
    • SmartSYNC: Correcting data and rerunning a data flow

      Occasionally SmartSYNC will report flow errors. Usually the issue will be something to do with the data that has passed through the flow such as an Invalid address (misspelt country, or other details), invalid phone number format, invalid email ...
    • SmartSYNC: Testing a flow, initial setup hints

      When setting up integrations you may wish to limit the records that cause updates to flow to other applications. Without this you may have more data flowing between the applications before you have properly tested the flows out. You can easily set up ...
    • SmartIMPORT: Working with web forms and applications that support webhooks

      There are tons of applications and web form systems that support webhooks. If in doubt contact your provider to see if they confirm they support webhooks or Google for the answer. If they do then great news - SmartIMPORT can be used to pull that data ...