Hi, I’m Danielle VanHorn and I’m a Product Manager on the Raiser’s Edge NXT team. I’m here to bring you another in the series of Product Update Briefings follow-up Q&A posts. This post attempts to synthesize and respond to your questions about new Import capabilities in web view.
Import is a cornerstone of effective data management, making it faster, easier, and more accurate to bring information into your system. Instead of manually entering records one by one, Import lets you upload, map, and validate data in bulk, saving time, reducing errors, and ensuring data integrity. Whether you’re adding new records or updating existing ones, Import provides flexibility to work at scale so you can manage data efficiently and keep your database clean and reliable.
How will Import in Web View be different from Database View Import?
- Simplified workflow
- Database view import requires selecting specific import types and multiple steps to perform an import.
- Web view consolidates this into a single, intuitive workflow and features a new, modernized user interface. This means fewer steps and less complexity with no need to specify import types. One file can handle adds and updates for multiple record types.
- Performance improvements and scalability
- Faster processing and improved reliability when performing large imports.
- Imports run asynchronously so you can keep working without interruption.
- API Access
- Enables integrations with partner applications through dedicated endpoints.
- Improved error handling
- Import in Web View will generate an exception file for failed rows with clear error messaging.
- Exception files can be edited and re-imported, allowing for targeted retries without reprocessing all data.
When can I start using Import in web view?
Import in Web View is currently in development, beginning with bulk APIs for constituent import and import into gift batch. We’re planning early adopter program (EAP) opportunities in the first half of 2026. General availability is expected toward the end of 2026; we’ll have more information about timing in the next Product Update Briefing in May.
How do I sign up for the Import in web view Early Adopter Program (EAP)?
Thanks to very active interest in the Import EAP following the last Product Update Briefing in November, the program is full. While we’re not enrolling new EAP participants, we’ll continue to share updates and resources in the Raiser’s Edge NXT Community as the new functionality becomes available.
Communications to those who have expressed interest in the Import EAP will go out in the next few weeks.
Will I still be able to use database view Import?
Yes, you can continue using database view Import for now. As we roll out Import in web view, we’ll provide guidance to help you transition smoothly and take advantage of the new functionality.
Will Import in web view replace the need for Partner solutions?
No, our goal is to build out a native import solution in Raiser’s Edge NXT so you can easily perform essential imports directly within the user interface or via API. If you need more robust, customized functionality, partner solutions will still be the way to go. We are working closely with our partners as they build modern solutions to replace their existing plug-ins with capabilities that work with Import in web view.
How will I be able to import data into web view?
You’ll have two options:
- Upload a CSV file through the Raiser’s Edge NXT user interface for a simplified, user-friendly process.
- Via bulk API endpoints for enabling integrations from custom solutions you develop, partner applications, and other external systems.
What types of data will I be able to import in web view?
Import will be introduced in phases to give you the best experience. Early access starts with core functionality for importing Constituents and importing gifts into Gift Batch. Then, we’ll expand to include additional record types along with advanced functionality like bulk add, edit, and delete (global change).
Where will we find the Import functionality in web view?
Import will be located under Data Management, a new option that will be added to the left navigation.
Are you migrating over import history from database view?
While data gets updated in both views regardless of where you initiate the import, the import history is specific to each view. So in web view you will only see import history for imports originating in web view; in database view you will only see import history for imports originating in database view.
Data will update as expected across both views, wherever you initiated the import but you will only see the import history where the import was initiated.
Will Import in web view detect duplicates?
Yes. Import in web view includes duplicate detection and resolution options to maintain clean, accurate data.
Next Steps