Contribution Import Utility experience

Hi All,

I'm starting to read up on the Contribution Import utility, seeing how we might get that up and running here. Of course the documentation is good, but I'm very interested in how well this is working for organizations currently. Most of the forum posts I've seen are a little dated so I thought I'd start asking here. Any input is helpful: like it, don't like it, tips, cautions, etc.

Thanks for sharing your thought!

Jenny O'Neill-Englund

Parents
  • Take infinite care getting your xml set up to your desired spec and document to the user who will be creating the import files. I provided a sample excel template with the details in a second tab (pretty much copied from here https://www.tessituranetwork.com/Help_System/Tessitura.htm#Contribution%20Import/Preparing%20the%20Import%20Data.htm). We had a few hiccups at first, but it's been working great once everyone got the hang of it.  It's especially been a boon for regular paycheck or giving day contributions that are provided in a spreadsheet format to the organization that uses it most, and the user's figured out how to take advantage of that to simplify their process and make it more efficient. 

    We're on RAMP, and one thing that helped was to place the data file in LIVE, but map to there in TEST for review run. That way there are no oopsies getting the correct updated file in place for LIVE since it's the exact same file that was used in TEST.

Reply
  • Take infinite care getting your xml set up to your desired spec and document to the user who will be creating the import files. I provided a sample excel template with the details in a second tab (pretty much copied from here https://www.tessituranetwork.com/Help_System/Tessitura.htm#Contribution%20Import/Preparing%20the%20Import%20Data.htm). We had a few hiccups at first, but it's been working great once everyone got the hang of it.  It's especially been a boon for regular paycheck or giving day contributions that are provided in a spreadsheet format to the organization that uses it most, and the user's figured out how to take advantage of that to simplify their process and make it more efficient. 

    We're on RAMP, and one thing that helped was to place the data file in LIVE, but map to there in TEST for review run. That way there are no oopsies getting the correct updated file in place for LIVE since it's the exact same file that was used in TEST.

Children
No Data