Thanks for reporting this @SHust, I've been able to identify two issues one of which we would have to bring up with Fundraiseup:

1. Fundraiseup seems to be skipping some transactions in the exports, especially those that failed initially and got successful on a later date. This in turn causes civi to mark the recurring contribution as failed.
2. Some imports are missed initially by the audit consumer and as such they get caught up in the job that cancels inactive recurring records.

I'd bring up the first scenario with Fundraiseup to make sure we have data consistency on both sides after the migration.

@Damilare, thanks for sharing your findings! Did you happen to come across any other cases similar to the one I flagged? As we plan for the transition away from FRU, it would be helpful to know if this was a one-off or just one of a few.

Yes @SHust, definitely not a one off as I found some that are still been charged in Fundraiseup but are cancelled on Civi. The ones I saw were related to the first issue I listed in my previous comment. I think Fundraiseup exports them on a later date, I'd have to confirm that.

However for the transition, we would need to make the request for a large export containing all donation records to ensure data consistency.

Thanks for confirming! If there's no way to cancel the ones you found automatically on the FRU console, please let me know (share a list if possible) so we can make arrangements to take care of them. Thanks again for working on this!

Hi @SHust,

Here's a list of fundraise up subscription IDs that I found are cancelled on Civi but not on Fundraiseup. I'd update this ticket if I find any more

RAHTKFBC
RFLRTVJQ
RNCQXKVV
RQYJMHRW
RLCANTYA
RKEGBHUN
RNFJYWAT
RZXKQQXU
RFLRTVJQ
RFXARCWW
RNCQXKVV
RKEGBHUN
RQYJMHRW

Thank you! The active recurring charges have been canceled, and the additional charges refunded.