Key takeaways
- Blackbaud ends Raiser's Edge NXT database view on September 15, 2027. After that date, fundraising runs only in web view.
- Online Express, NetCommunity, and database view-based plug-ins, integrations, and customizations end on the same date.
- Your data stays in Raiser's Edge NXT. What changes is how your team queries, exports, imports, and processes gifts.
- Inventory every database view workflow now, and check each one against Blackbaud's Feature Map before your renewal date.
Blackbaud ends Raiser’s Edge NXT database view on September 15, 2027. Its help documentation says that “database view-related solutions and functionality will end” on that date, and after it your team works only in web view. If your queries, exports, imports, batch gift entry, or mailings run in database view today, each of those workflows changes before the deadline. Your data does not move. The way your team works with it does.
What is Raiser’s Edge database view, and how is it different from web view?
Database view is the Windows interface that Raiser’s Edge 7 users know, which Blackbaud’s help documentation describes as accessed through Citrix. Web view is the browser interface of Raiser’s Edge NXT. Both read the same database, but they do not show the same fields. Blackbaud’s transition guide lists data that exists only in web view, such as email history, opportunity status history, and solicit code dates. It also renames many database view features, so a few everyday terms change:
| Database view | Web view |
|---|---|
| Annotations | Alerts |
| Cash gifts | One-time gifts |
| Solicit codes | Communication preferences |
| Media | Attachments |
Our Raiser’s Edge migration guide covers the rest of the record types.
What stops working when database view ends?
Blackbaud’s September 2026 announcement says support ends on the same date for three groups:
- Raiser’s Edge NXT database view itself.
- Blackbaud Online Express and Blackbaud NetCommunity.
- Database view-based plug-ins, integrations, and customizations.
The same post says “there is no data migration.” Your constituent records and gift history stay in place. The risk sits in the workflows your team built in database view over many years: saved queries, export definitions, import routines, batch templates, mail and receipt setups, and any tool that reads from or writes to database view.
What is still coming to web view?
Not every database view workflow is in web view yet. These are the dates Blackbaud listed for the remaining work in its September 3, 2026 announcement:
| Area | What Blackbaud lists | When |
|---|---|---|
| Gift processing | Batch defaults and the rest of core gift processing | October 2026 |
| Communications | Mail, receipts, acknowledgements, pledge reminders | By December 2026 |
| Data management | Export and import of constituents and gifts | By December 2026 |
| Constituent management | Remaining constituent fields from database view | By March 2027 |
| Events | Copy, custom fields, seating | By April 2027 |
| Data management | Global Change and more import types | Through June 2027 |
Part of the gift processing work has already shipped. Blackbaud’s release notes show adjustments to existing gifts, and links from gifts to tributes, events, benefits, and matching gifts, reaching web view in September 2026. Check the Feature Map for the current status of each item before you plan around it.
The last items arrive less than three months before the deadline. That gap worries some administrators. One Blackbaud Community member put it plainly in the comments: “only having 80%, then 90%, then 98% of needed functions and having to work in two systems, train new staff, develop procedure guidelines continues to just take so much time.” Blackbaud’s Feature Map shows what is available, what is coming, and what is not planned.
What should you do before September 2027?
Start with an inventory, because it serves either choice.
- List every database view workflow. Saved queries, exports, imports, batch templates, global changes, mail and receipt setups, reports, and scheduled jobs. Name the person who runs each one.
- List every connected tool. Online giving, event registration, wealth screening, payment processing, and any plug-in that depends on database view.
- Check each item against the Feature Map. Mark it as available in web view, coming with a date, or not planned.
- Put your renewal date beside the roadmap dates. If a workflow you depend on arrives after your renewal, you are signing the next term before you can test it.
- Clean the data now. Merge duplicates and retire unused attributes and codes while the team still knows database view. Our database cleanup tips cover the basics.
Should you move to web view or leave Raiser’s Edge?
For some teams, staying is the right call. If the workflows you rely on are already in web view and your staff are comfortable there, moving to web view is the shorter path, and Blackbaud publishes checklists and training for it.
Other teams find that the inventory changes the question. When key workflows are still on the roadmap, or when your renewal falls before they arrive, you are choosing a new way of working either way. That is the moment to compare Raiser’s Edge NXT web view with other CRMs on the same list of workflows. Our comparison of the Ignite Active Intelligence Platform and Raiser’s Edge NXT goes capability by capability, and our Raiser’s Edge alternative page makes the case for a move.
How do you get your data out while database view is still there?
Database view Query and Export is the usual route for full constituent and gift extracts today. Take a complete archive export while you still have it, whatever you decide. If you leave, plan one export per record type and map each one before anything loads. Our Raiser’s Edge migration guide has the field-by-field map, the four export routes, and the steps in order.
Where to start
If your inventory points to a move, we built Ignite so fundraising, finance, and marketing share one constituent record. Our team converts your Raiser’s Edge exports, loads them into a test environment, and reconciles counts and totals with you before you cut over. For a first read on how ready your data is, take the Migration Readiness Scorecard.
Frequently asked questions
When does Raiser's Edge database view end?
Blackbaud's help documentation says database view-related solutions and functionality end on September 15, 2027. Blackbaud's community announcement from September 2026 gives the same date. Some older third-party articles cite June 30, 2027, which was an earlier estimate. Plan against September 15, 2027, and confirm the date with your Blackbaud account team before you set your own timeline.
Do I need to migrate my data to web view?
No. Blackbaud says there is no data migration. Database view and web view are two ways into the same Raiser's Edge NXT database, so your constituent records and gift history stay where they are. What changes is the screens and tools your team uses to query, export, import, and process that data, so every workflow built in database view needs a web view equivalent or a new home.
What else ends with database view?
Blackbaud says support also ends for Blackbaud Online Express, Blackbaud NetCommunity, and database view-based plug-ins, integrations, and customizations. If your online giving, event registration, or a third-party tool depends on any of these, it needs its own plan before September 2027. Ask each vendor in writing whether its product depends on database view and what replaces it.
Should we move to web view or leave Raiser's Edge?
Base the decision on your inventory, not on habit. If the workflows you rely on are already in web view and your staff are comfortable there, staying is the shorter path. If key workflows are still on Blackbaud's roadmap, or your renewal falls before they arrive, compare other CRMs on the same list of workflows.