InsideTrack Scoop: Import for Impact Highlights

Tanya Fitzgerald

The InsideTrack to the Unified View  for Blackbaud Raiser’s Edge NXT® webinar series is designed to give you clear, reliable updates from our product management team that help you plan and adapt your processes to use current web view features. 

Our April InsideTrack session focused on Import in web view that will be released later this year. While we couldn’t address every question during the live discussion, we’ve gathered the most common ones to keep you informed and ready.  

Key questions and answers:  

File Size and Supported File Formats 

What file formats can I use to import data?  
You can import data using either a CSV file or a JSON file. 

How large can my import file be?  
As we get closer to general availability, we’ll provide clear guidance on recommended file sizes and best practices. Our goal is to reduce the need for you to manage file limits yourself. You’ll be able to upload your file in full, and we’ll handle batching and processing in the background to get your data into the system efficiently. 

Creating and Updating Data 

Can I import both new records and updates in the same file?  
Yes. A single import can include both new records and updates to existing records. 

Can I import multiple types of data in one file (for example, constituents and gifts)? 
Yes. You’ll be able to import multiple record types in a single file. 

Can I import multiple attributes for a constituent in one import?  
Yes. You can include multiple attributes for a single constituent within a single import. 

Identifying Records, Duplicate Management and Matching 

Which IDs can I use to match existing records?  
You can match existing records using System Record ID, Constituent ID, or Import ID. You’ll be able to choose which identifier to use to match existing records as part of the web view import process. 

Will the web view import process handle duplicate detection? How will it work? 

Yes. Duplicate management is being built into web view Import. Here’s how matching will work: 

• If a System Record ID is provided, the existing record is updated. 
• If an Import ID or Constituent ID is provided, the system checks for a match. If a match is found → the record is updated. 
• If no ID match is found → fuzzy matching is used, which looks at a combination of details like constituent name, email, phone, and address to identify potential matches. 

From there: 

• If a likely match is found → the incoming data is added to the existing constituent (for example, as a related or child record). 
• If no match is found → a new record is created, and any provided ID is assigned. 

At the initial release, there won’t be a manual review step for fuzzy matches. We know that more control and transparency are important here, so we’re actively exploring future enhancements to give you more visibility and control. 

Validation and Error Handling 

Will there be a “validate only” option?  
Yes. Thanks to all your feedback, validate only will now be included as part of web view import so you can review and catch issues before committing data. 

Field Mapping 

Will fields be automatically mapped? Can I override mapping?  
The initial experience focuses on automatic field mapping based on your file headers, but the ability to manually map fields is also planned as part of web view Import.  

Creating Import Templates & Accessing Existing Templates 

Will Import templates be available? 
Our current focus is on delivering core import functionality first, with template support planned as a follow-up capability. We’re actively exploring: 

• The ability to create Import templates/providing downloadable header files 
• Bringing over existing templates from database view 

Will my existing database view Import templates be available? 
We’re actively exploring options to bring existing import templates from database view into web view Import. Our goal is to make it easy for you to reuse the templates you’ve already created to streamline your transition to web view. 

While this capability isn’t finalized yet, it’s an area of active discovery and could evolve based on what we learn through ongoing feedback and development. 

Will I still be able to create import files?  
We’re planning to align the import experience with Query and Export in web view to support the creation of import files. 

We’re working to carry forward the key functionality you rely on today, but the exact experience is still being defined. This functionality is also currently in discovery, so details may evolve, and we’ll share updates as plans become more concrete. 

Naming and Managing Imports 

Will I be able to name my imports?  
Yes. You’ll be able to assign names to your imports to help manage and track them more easily. 

Table Entries 

Can I create table entries as part of an import? 
Not initially; however, we know that creating table entries is an important part of your workflows, so we’re actively planning for it. This capability is on the roadmap for Import in web view. 

Global Changes/Bulk Update 

Will Global Change functionality be available? 
Yes. Global add, update, and delete (also referred to as Bulk Updates) is planned for web view. 

Partner Solutions 

What does web view import mean for Partner tools?  
Web view import is not intended to replace Partner solutions. Our focus is to provide a native import experience so you can handle everyday import needs more easily through the import user interface or import API. Partner tools will continue to provide added value, especially for organizations that need advanced automation and highly customized workflows 

Learn More 

For a deeper look at how Import is evolving you can review the session recording: InsideTrack to the Unified View-Import for Impact.  

Don't miss our June InsideTrack session on next level gift management.