nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

NXT - How long will we have with "full" capability of NXT before sunsetting database

Danielle Lifshitz

Even with all the improvements there are still many things that can't be done yet in NXT. It is important to know how long we will have to practice new things in NXT, while we still have database available. Other than saying that database view will be sunsetted, do we know how long we will have with full NXT capabilities

Find more posts tagged with

Accepted answers

Dariel Dixon

I don't know if there is a way for us to know @Danielle Lifshitz. There's no definition of what full NXT will be as it should always be evolving. I'm not sure if the question is how long will we have both, but making a plan to start doing things in both, and planning on not having database view to fall back on. Right now, there's a lot of blind spots and features that aren't in NXT (ahem, unified view) and while they are working on them, everything won't come over in a 1::1 from database view. Now is the time to start planning on what you need, and the idea bank is more important than ever to let the developers know what features we need before it goes away.

Every year, the timetable changes slightly, so what we know now is subject to change.

Carlene Johnson

Blackbaud has been very consistent about a late summer 2027 sunset for Database View. That date could shift slightly, but I wouldn't bet on any major change to the timeline. Given that, you should be building a plan now to move your processes into Web View.

I'd approach it with a Web View first mindset: try it there, and only drop back to DBV when you truly can't get it done. It's frustrating that not everything works the same way yet, but the sooner you build that habit, the less painful the eventual cutover will be.

I'd also set expectations across your organization that things will take longer for the next year or two. Whether that's hopping back and forth between WV and DBV to finish a task, or just learning new steps in an interface that's slower and organized differently, build extra time into your timelines. Give yourself (and your team) some grace while you rebuild muscle memory. It's a huge shift, not just a little UI change.

If you can, build out some timelines and goals for yourself of which processes you want to move and in which order. Treat this like a true "project" not just something you are doing on top of all the other things you need to do in a given year. Work with leadership to carve out time for this instead of trying to shoehorn in.

Finally, be sure to attend the Product Update Briefings, the Inside Track to the Unified View session, and any Town Halls that Blackbaud schedules. Set aside time on your calendar for Tuesday afternoons or Wednesday mornings to read the "What's New" alerts. I would make all of this mandatory for any significant Raiser's Edge user in an organization.

All comments

Dariel Dixon

Every year, the timetable changes slightly, so what we know now is subject to change.

Carlene Johnson

James Belich

https://community.blackbaud.com/discussion/86460/nxt-how-long-will-we-have-with-full-capability-of-nxt-before-sunsetting-database

100% agree! It's easy for Blackbaud to say we should moving processes away from database view now, but given how much NXT is still changing, it's very difficult to do. And there's so much still missing in NXT, that I end up falling back on DBV for most tasks.

I'm not sure that Blackbaud fully understands that we can't move a lot of processes over to NXT until it's complete. I don't know how long Blackbaud will give us with full NXT functionality before DBV is retired (if any at all), but I think at least 6 to 12 months is necessary.

Joe Moretti

Moving processes away from database view………………………I mean 3/4 of the things me and my co-worker do MUST be done in Database View. Again, I do not quite what the real reason was for creating NXT, which has been in the works for more than 10 years. I just don't get it. Just from a technical aspect, the interface is bad and looks like something for a child.

Devan Bessinger

@Danielle Lifshitz I think I understand what you are saying. It sounds like your question is not necessarily "how long will we have database view," but is more about how long it's going to take them to get all DB view functionality into the web. If they target 9/1/2027 as the sunset date of DB view (which is what I'm guessing, since we've already been told that is the end of life for Online Express), will they still be releasing DB functions into web view on 8/31/2027, giving us little time to test those features out, "practice" with them, and update our internal processes and procedures. That's a concern I have as well. I'm trying my best to get our whole org switched over. We are pushing hard for it. However, it does take time for folks to make the transition. It will be difficult if there are fields or system functionalities that only move over during the last week of August 2027. I'll be frantically showing that stuff to people before we lose the ability to see/do it in DB view. That's stressful for me, and stressful for the users. It also doesn't leave us a ton of time to revise or refine our processes and update our procedural documentation before we're live with a new interface. I hope this is something Blackbaud is taking into consideration and that they either get everything from DB view brought over to web view (everything they are porting over anyway…) prior to end of Q1, or I hope they choose to take a phase-out approach to the sunset of DB view where they gradually turn off features and functionality that is confirmed to exist in web view but leave other things accessible in DB for a period of time. It would be great to get at least six months with a piece of functionality in web view before we lose it in DB. In the meantime, we'll just keep trying our best to educate folks in web view, encourage them to use it, and update our documentation as best we can!

Danielle Lifshitz

Devan explained it much better than I did. Most other program/software changes would include having the original program available for a specified time while using the new program. The frustrating part is that you can't plan or make adjustments to processes if they don't yet exist in NXT or are constantly changing. If NXT is only fully rolled out at the same time they sunset database view, it will be problematic for many.

Heidi Scheuer

I agree. Many of us are trying to do our day-to-day functions and trying to learn NXT blindly is not time efficient. Also, it is difficult to establish processes and procedures for data entry staff and others when we do not have a full grasp on what we can and can not to in NXT. Lastly, I find training courses for the Webview lacking. I need more than just an overview.

JoAnn Strommen

So agree @Danielle, there needs to be time to work in web view, discover what functions are glitching, missing, changed; have time for BB programmers to fix and start the process again.

I know gifts and gift batches is a huge programming area but there have been so many issues identified that are on the schedule for upcoming release. Hopefully, they will all be resolved but they can't be identified until folks are in using the functions.

Lori Hill

I know this reiterates many of the other comments. The thought of the database view going away next summer is tremendously stressful, because there are a lot of more advanced data management functions still not available - imports, global changes, advanced exports, mail, salutations/addressee formats management - that will take time to get accustomed to. Not to mention, I'm going to have to redesign or create new queries, exports or reports to replace the reports that aren't coming over, now that I'm aware of what's not transferring.

I'm the only superuser in my organization and all of these things fall on me. Trying to adapt and test functionality as things are released is not always feasible. I do what I can and add ideas to the bank when I find an issue; however, I also need to keep up with my day-to-day responsibilities. Thinking about how these advanced data tool releases will supposedly come out in quick order between now and next summer is intimidating. I'm not sure how I'm going to find the time to test new functionality, re-write procedures and protocols, and keep up with everything else I need to do.

It would be nice if the sunset of the database view was pushed out for at least Supervisor level users, so it gives database managers like me a little breathing room to get everything transferred over, new procedures and protocols tested, and workarounds in place where necessary. Unfortunately, those workarounds may entail needing to become familiar with using and programming in Microsoft Power Platform applications - something I have NOT had time to do in the last several years, nor the financial resources to hire a consultant to design things for me.

I'm not sure if someone from Blackbaud will review these comments; however, please take database managers/administrators for smaller shops into consideration when it comes to sunsetting the database view. I accept that it has to go away, but having a 12-month gap between when the last updated NXT functionality is released and when it closes would be extremely helpful.

Kim O'Brien Green

@Lori Hill I agree 100%! And I agree with all of the other comments. I am in the same boat - the only super user at a small shop and it is extremely stressful and exhausting keeping a foot in both systems and trying to keep up with day to day activities. Not to mention keeping up with all of the product updates, webinars, roadmaps, chats, etc. All we are asking for is an overlap period for when NXT is fully functional - to be able to test and make sure all of the functionality is working. And to have time to try the new systems that are not available now as it feels as though they are pushing out most of the functionality very close to the sunsetting of database view. And our fiscal year closes on 6/30 so we have to get tons of reporting done to close the year and for the audit in late August which is going to coincide with the end of database view.

Pam Moloney

Suzie Capps

I agree with many of the comments above - I am excited for functionality to shift to webview, but if Blackbaud want to 'sunset' database view mid-2027, then all the work in the feature map must be completed by the end of 2026 to allow testing / full transition (and the fixing of bugs)! At the moment there are some critical features not planned until 2027 e.g., Volunteer Management.

JoAnn Strommen

With the email that just came stating "On September 15, 2027, support for Raiser’s Edge NXT database view and related database view-dependent functionality will end."

It doesn't look like there will be much of an overlap to work out glitches in the changes/functions that are coming Q2-3.

JoAnn Strommen

Joe Moretti

Let's see what is NOT in RE NXT:

Proper Exporting Functions

RE Mail Functions

Action Reminders

Deleting Phones (in the Plug In) and not going to happen according to the recent email stating NO PLUGINS

Import

Global Everything

No proper Home Page like DB View

Feel free to mention items that I have not.

…………………………..and let's not forget that awful interface of RE NXT.

So I will be sticking with the work horse DB View till I no longer have a choice.

Jennifer Baer

Add to the list . . .

Seating in NXT events.

I've been using the "event seating setup wizard" in RE database for years. I works beautifully. I think my head will explode if I can't seat 550 people at annual fundraising event directly from RE NXT.

I might have to move up my retirement date!

Suzie Capps

Adding all things related to Managing Volunteers to the list of what is missing!

James Belich

The Queue function is another big one (related to Exports).

Not to mention it's still not possible to fully edit/delete all records in web view as you can in database view (I run into this one all the time).

Allison Dickerson

Carlene, that is the MOST helpful information I've received regarding this whole transition. Thank you!

Crystal Bruce

Just tagging @Carlene Johnson here so she sees the reply. :)

Livia Ramos

New customer here in the middle of implementation and feeling frustrated with the differences between database view and WebView. They are pushing hard for WebView with us but it does not have the functionality. Although the database view looks terrible and is not what we would like to train our internal end users on but looks like we have no choice. Any tips on things we should be doing/not doing as we move forward? One of our biggest frustrations is that we would love to rename some of the fields to input data we actually want which can be done in database view but won't carry over in WebView.