Skip to content

Integrations & migration

Move your support data without losing the details that matter.

Bring existing donor information into Koala with a review-first import process, then connect supported systems based on your organization’s setup.

Direct sync, today

Two processors connect directly today, with more coming. Everything else comes in by CSV — which works well, and is a different thing.

Fundraise Up

connected sync

Donation forms, recurring plans, and donor records, synced to Koala.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Stripe

connected sync

Charges and subscriptions taken directly through Stripe.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Pushpay

coming soon

Church and ministry giving, including recurring gifts and funds.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Tithe.ly

coming soon

Church giving, with funds that usually map to a staff member.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Planning Center Giving

coming soon

Giving inside Planning Center, with its own funds and donor records.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Subsplash Giving

coming soon

Giving through a Subsplash app or site.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Givelify

coming soon

Mobile giving for churches and faith-based organizations.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Donorbox

coming soon

Donation forms and recurring plans for smaller teams.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Givebutter

coming soon

Donation pages, campaigns and peer-to-peer fundraising.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Classy

coming soon

Campaign and event fundraising, now part of GoFundMe.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Anedot

coming soon

Payments for nonprofits and faith-based organizations.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

PayPal

coming soon

Donations taken through PayPal, including Giving Fund payouts.

  • · Donations become gifts, designated to the right staff member
  • · Recurring plans become pledges with an expected next date
  • · Declined payments arrive with the reason and the amount
  • · A reconciliation view compares Koala against the processor

Everything else, for now

There are two direct integrations today, and more are on the way. Other payment processors, church management systems and accounting tools are not connected — their data comes in by CSV like any other source. If a direct connection to a particular system would decide this for your organization, say so on a demo and we will tell you honestly where it sits.

A review step before anything is written

The risk in a migration is not the upload. It is discovering afterwards that two hundred partners were duplicated, or that a year of gifts landed against the wrong staff member.

  1. Prepare

    Export your donors and giving history as CSV. Any column order works — you map them in the next step — and you need an administrator or finance login to run an import.

  2. Preview

    Koala reports what it would do: rows ready, records that look like existing partners, designations it could not match to a staff member, and rows with errors. Nothing has been saved at this point.

  3. Resolve

    Work through the rows that need a decision. Pick the right partner where several share an email, choose a designation, or mark a row to skip.

  4. Import

    Commit the rows you have settled. Imported gifts are tagged as having come from an import, so they can be told apart from processor-synced ones later.

An import dry run · example data

1,284 rows reviewed — nothing written yet

Ready to import1,197
Possible duplicates to review61
Unmatched designations26

You decide what happens to each one before anything is saved.

Coming from another system?

Most organizations arrive from a spreadsheet or an existing CRM. Either way the route in is the same: export what you have as CSV, map the columns, and review the preview before committing.

From spreadsheets

The most common starting point, and the easiest — one row per donor, one per gift.

From another CRM

Export donors and giving history separately and import them in that order, so gifts have partners to attach to.

What we do not claim

There is no purpose-built migration tool for any specific product, and no guaranteed migration service. Ask on a demo what your export actually looks like.

Questions worth asking

Can we undo an import?
Not as a single action. The preview exists so that decisions are made before anything is written; individual gifts can be corrected or deleted afterwards, and every change is recorded.
What happens to duplicate partners?
The preview flags rows matching an existing record and shows what distinguishes the candidates — when each was added, what has been given, whose team they are on — so you can pick the right one.
What if a gift's designation does not match a staff member?
It is held as unmatched rather than guessed at. You map the designation, and the mapping is remembered for subsequent imports.
Can we export again later?
Yes. Donors, donations, funding over time, donor acquisition and the change log all export as CSV.
Do imported and synced gifts get mixed up?
No. Each gift records how it arrived, so a donation that came from the processor can be told apart from one that came from a spreadsheet.

Discuss your migration

Tell us what system you are on and what your export looks like, and we will tell you what moving would actually involve.