I agree with everything that Kimberly Harris stated and Laura D and Brenda and Cindy and Elizabeth and everyone. PLUS - no gift type of recurring gift payment, no way to 'apply to' a pledge. NXT batch has to be as efficient as Database batch before you take that away.

Must have the ability to view all fields in a batch in tabular format for proofing before approval.
Need to be able to globally change all fields in a batch (this would include custom fields - especially those configured as dates. Can't wait to get Gift Code. . . even if it was just in the API for now.

I agree. You can not take away valued essential tools when upgrading. While NXT is fabulous for fundraisers, it is currently a nightmare for Data Admin staff that do the bulk of the gift entry, or any mass data changes using Query to pull up move through the appropriate records. Do not forget the admin functions are also important, requiring speed and efficiency. Clicking through takes your hands from the keyboard, another time water. Tab through, short cuts etc. Opening a record in NXT takes at least 3x as long as in DB and often shunts you out of where you are working. Not efficient for users.

Being unable to view database view batches in web view is also a gaping hole. If we are losing our ability to create new queries in dbview in Feb 2026, we need to be able to view and create queries that pull those db view batches in web view prior to that time.

Just adding my 2c in for this post - our org looks through each constituent's record when we process a gift to update and double check our entry and make sure the record is clean. It is SO annoying to do with with web view batch - inside the gift I can't open it at all, and on the greater batch clicking the constituent record closes my batch. In DB view it pops open over the batch - web view should have records pop open in new tabs or windows. The batch process in web view is already so slow compared to DB view but this makes it even worse for me. I find myself having to open records in DB view just to make batch entry work in web view at all according to our org's policies. Should not be this difficult in web view to utilize this practice that keeps our data clean!

It is essential that we have the options available in NXT Gift Batch to add tributes, link gifts to event registrations/donations, etc...

Absolutely correct! I completely agree! My org has multiple database view batch templates we use for various types of gift entry. We have multiple business rules to proved pop-up alerts during gift entry as well.

It is critically important that gift batch entry in database view remains accessible until NXT web view has all the same options, features and a spreadsheet like layout to save time.

In addition, after committing a batch in DB view, we export the Batch Commit Control report. This is vital for the finance department, reconciliation and back-up documentation for annual audits.

We must have NXT be equal to DB in Batch as well as other features and modules or continue access to DB view. This is so important!

I completely agree. Gift batch entry is much easier in database view. I like that I can tab through cells and see all of the gifts in a spreadsheet view similar to excel. It's easier to find any input mistakes in this view because I can compare similar gifts (for instance, type of event ticket sales).

I didn't read through all of the comments, but can see that I'm on the same page with them. Please do not do away with DB view for gift batching, it's not helpful, useful, for what gift processing is used for.

We agree that prefilling in the fields is necessary in order for it to be considered a Batch process. Also please add the ability to modify or delete information entered into NXT that may have been put in incorrectly, once back in database view

Gift codes need to be added to NXT in all places - it is essential for some orgs financials!

WHY is there a lag between entering a new record and being able to match that record to a donor in gift batch? If I can immediately see that record in NXT after creating it (and I can) it should be immediately available as a match. Currently I'm having to wait 5 to 10 minutes after creating a new record before I can match to it in an NXT gift batch.

The inability to add default coding in is very frustrating. If you have a whole batch of gifts that are all going to have many of the same details being able to enter that once and having it apply to all the gifts you then enter into the batch is essential

I completely agree with everything Tracy LeClair outlined about the Speed & Simplicity of DB over NXT!

• Templates are ESSENTIAL!

• I would also like to be able to access a constituent's record while in a gift batch!

• I use pop-ups in DB to alert me to things like, if a donor doesn't want a thank you letter or if they are a recurring donor, but give in an unconventional way. Those don't work in NXT.

• We rely on gift codes to identify where a gift goes, especially if it's restricted, but that isn't required in NXT. I then have to go into DB to enter them.

• Would like to see a way to customize the layout and fields in NXT to make it user friendly for each individual.

Shelby Kock Wah Ng

Need to be able to generate thank you letters (not emails) for the complete batch like we can in Database View

I agree. It is critically important that batch gift entry in NXT is equal to DB. Our org has multiple templates for different gift types that are used to speed gift entry.

Biggest issue with NXT batch is there is no batch template which saves so much time

I totally agree. It's also not as simple as database view you have to go back and forth a lot. And you can't link gifts to an event, so you have to go into database view to do it.

We use recurring gifts to manage specific appeals which in our case are thousands of relationships (Sponsored children matched to their donor). We must have the ability for a recurring gift to populate all of the fields in Web View batch entry for processing