Is anyone else confused about why this is happening? Do you have a plan for February?
https://fundraiseup.com/docs/nxt/
Lee – I’m interpreting this change as FundraiseUp partnering with Omatic to provide an official connector rather than continuing to maintain their own.
From what I can tell:
It would be wise to reach out directly to FundraiseUp for clarity on whether the integration will be disabled entirely or just unsupported after January 30. You may also want to contact Omatic to understand pricing for their connector, and consider exploring other solutions such as:
So in short, the integration will run through January, but February may depend on whether Omatic’s connector (or another solution) is in place for your organization.
There’s a wide variety of pricing across these solutions, so it’s worth comparing costs alongside functionality to find the best fit for your organization.
Here's the response we have received from our account rep from FundraiseUp:
Thanks for reaching out — I know this announcement raises real concerns for your team. To answer your question directly: the decision to end support for the native Raiser’s Edge NXT integration is the result of changes on Blackbaud’s side that materially affect how our connection can operate. Specifically, Blackbaud now enforces very limited API connection allowances for developers and has not approved the expanded access we requested. Because of these restrictions, continuing to maintain the native integration at the standard our customers expect is no longer feasible.
We are "piloting" Fundraise Up (FRU) as well and looking likely it will stay. We opt-ed to do not use the FRU integration with RE NXT since we were already told of the "end of support".
That said, I find it odd that other company/app is able to continue their operation (i.e. Omatic Cloud, SMARTSync, etc). Does it have to do with Blackbaud having limit, or having limit that needs to be paid for.
I tried to set up the native integration and it was far too limiting for our needs. I ended up creating multiple Omatic imports with tons of dictionaries and it works great. BUT this isn't a cost that every organization can take on; it just happened that we already had ImportOmatic so it wasn't difficult to set up profiles for FRU.
Hopefully you can find a quick and somewhat easy way to import your data.
@Alex Wong their comment made me think it was a request to BB and it was denied in order to meet FRU's needs/standards. 🤷♂️
Sounds like it is related to the api limit that BB imposed for all non-customer (i.e. developer) accounts - a tied-customer account get 25K/day and a non-customer account gets much less. It is odd that FRU was not approved for an increase - may have been the BB cost was just too much. Either way, it is decisions such as this that may be driving BB customers to other platforms.
3rd party integration with Blackbaud will best go the route of being a partner. Partner gets much more API quota, so unless it cause too much to be a partner, I cannot understand why FRU would just drop the integration.
Hello all,
Does anyone have any further info on this, we are creating an API to continue our link with FUP and RENXT, it isn't turned on yet and we are still receiving donations via FUP… any news on the hard cut off?
We're seeing the same thing, but glad to have Importacular ready to go if needed. I notice that it does mention no "new" clients can onboard with it. Maybe that is the case? Would not account for all the issues over the past six months or so from the API, but Sky's been off for a while.
Thanks Lee! I've been in touch with Fundraise Up and they have extended the switch off until July … phew
Very glad to see this post. We just onboarded with FRU. We hadn't planned on integrating, and instead using Importacular. Still, good to see others out there using the FRU/RENXT combo. Makes me feel like I've made the right choice.
