Page MenuHomePhabricator

Chariot import mapping template - 2 soft credits
Open, Needs TriagePublic

Description

I am building a new DAF import template for Chariot gifts that will need two soft credits (one individual (SC type = Donor Advised Fund) and one organization (SC type = banking institution)). Do you know how I can add the second soft credit for the organization (banking institution)? It will not be the same for all gifts so it will need to map to the information in the file. I know we have that for fidelity import, but all gifts in those files have the same banking institution soft credit.

[Discussion about adding / sharing addresses between individuals and DAFs has been moved to T411639: Share address and email between DAF and DAF owner when importing donations]

I have started a template draft #3685. We are hoping to get this running as soon as we can to use in the DAF emails going out Dec 11th and Dec 26th. For now I am manually adding the second soft credit to the gift by hand as well as manually creating new Org records where needed.

Details

Related Changes in Gerrit:

Event Timeline

@MDemosWMF Just want to make sure I understand this correctly:

For the individual contacts, you'll select the contact or create them yourself in the import process, but then you would like the email and address from the DAF to be added to the individual contact (only if the individual contact does not already have email and/or address or would you want to add or overwrite?). Presumably we'd also add a relationship at the same time.

We'll have to look at the two soft credits. We currently add the second one for Fidelity with a hook, so it's not really part of the import; it's just tagged on afterwards. So just want to set expectations that this won't be a super simple change and your timeline might be challenging.

@Lars good to know about the second soft credit difficulty level. It's great having that feature in batch data entry and was hoping there could be something similar for imports where we can map two different soft credits and soft credit types to the contribution for importing DAFs. We are hoping to utilized DAFpay more especially in 2026 so it would be great to have this on a roadmap for an early 2026 timeframe if we can. Let me know how that sounds. I think we are planning to use this payment method in Direct Mail down the road as well and we will need this capability if we are going to be able to scale on this payment method.

For the other piece it is an issue where the gift isn't importing because it is looking for an exact name match to that Organization record for the gifts going onto a Fund record. I'm wondering why if it doesn't find a match it does not create a new record with any email or address listed in the file? I had to go in and create those records myself. Most of them actually don't have any address or email present, but if they did would be nice to record when it creates a new record. I have the rules set to create new contact if not found so I thought that would do the trick.

Screenshot 2025-12-02 at 4.53.04 PM.png (736×2 px, 150 KB)

I have saved an example file here in case you want to take a look. https://drive.google.com/file/d/1C3biaBzGtCaEPzcl8VStvMPlSUbsQVSD/view?usp=drive_link

@MDemosWMF Yes, we'll aim for early 2026.

For the contact matching, are we looking at Import template 3685? I think the issue there is that we would need to import the address fields twice if we want them to apply to both the organization contact and the individual (soft credit) contact. So what you could do is duplicate those fields in your file and then map Contact - Street Address and so on for the organization and Soft Credit Contact - Street Address for the individual. Same for the email field, you'd need two of them.
If that's something we need to automate away, we could look at that as a future project.

@Lars Ah I think I understand, yes it would be ideal to automate this if we can! Perhaps alongside the 2026 work.

@Lars Was wondering if in the meantime we would be able to create two import templates for linked payers we are getting majority of gifts through currently: Groundswell and Daffy. Or is that too much work? Depending on the lift this could help cover our needs between now and getting the double soft credit feature for imports. Otherwise we are having to add that banking institution to each contribution manually since I don't think adding a soft credit/type is available as a mass update field in Civi (if we were to try and add the soft credit in bulk after import).

Let me know what you think - is this feasible or do we need to wait until the double soft credit feature is built?

@Lars @SBurnett-WMF Hi Lars, Stacey indicated that you had a timeline around this need. Are we still talking January or sooner? Many thanks.

@EMartin Apologies for the delay on this. It turned out to be one of those ones that needed to be done to be estimated as there was some additional complexity that wasn't anticipated. Here is an upstream PR that will allow us to add soft credits in bulk from Searchkit results, which is more general solution that we can use until we are able to tackle the more complex task of adding two soft credits directly to the import.

Lars moved this task from Sprint +1 to Current Sprint on the Fundraising-Backlog board.

@MDemosWMF Can you provide the contact ids for the two linked payers?

@Lars Yes, here are the current two we get the most volume through currently:

CID 56689204
CID 52743157

Thanks Lars! So it sounds like there will need to be a fix for the time being that would mean pulling the imported gifts into a searchkit and then mass adding the soft credit? It would be great to have help building that SK out as well to pull in the imported gifts.

As far as the more complex task of importing/mapping to 2 soft credits, around when could we expect to have that work complete? This will tie directly to what we are able to do with the Chariot rollout. Thanks for your help thinking this through!

Also to circle back on the issue of the Organization import not creating new records when a Fund name isn't found - I think the current Fidelity import (2446) does this? Let me know if I'm wrong there. Maybe we could copy the settings on that one for the Chariot Org import so it would create a new record with any address and/or email present in the file if a match isn't found in Civi.

Thanks @MDemosWMF. Yes, I can put together a SK/Form so we can just filter the contributions by batch (or any other criteria you like) and then add the soft credits in bulk. We should have this in a couple days.

For the more complex work, I haven't had a chance to get back into it, so I'm not sure I can provide a meaningful update right now. Let's get the above in place and see how much work it is on your end to handle it that way — and then we can revisit the priority of creating the two soft credits directly from the import and where that sits in our list of priorities in that context.

For the organization not being created issue, was it all of the ones in your example file above that weren't being created? Or just a specific one?

@MDemosWMF Also for the organization not being imported issue, I've tried locally and it seems to work as expected. So there must be something specific going on here. Could you provide me with the status message you get for these rows when you try to do the import?

Change #1227467 had a related patch set uploaded (by Lars SG; author: Lars SG):

[wikimedia/fundraising/crm@master] Add Soft Credit search task

https://gerrit.wikimedia.org/r/1227467

Change #1227467 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Add Soft Credit search task

https://gerrit.wikimedia.org/r/1227467

@Lars I don't have the error on hand at the moment, but basically it says there was no match found for that Organization name. Then I have to go in and create the record by hand before I can continue to import those gifts. This is using import template ID 3685. I will have more to import later in the week so I can get screenshots then.

@MDemosWMF Great, if you can get a screenshot and share the import before you manually create the org, that will make tracking this issue down easier.