Skip to content
Resources

Move Your Church to ChurchFoundry

Bring your records across with a preview, a clear scope and time to check the result.

30 days free · No credit card · No sales call

Actual ChurchFoundry screen. Fictional Christ Church demo data; tools depend on plan, permissions and configuration.

People directory in the fictional Christ Church demonstration workspace

People directory in the fictional Christ Church demonstration workspace

Actual ChurchFoundry screen. Fictional Christ Church demo data; tools depend on plan, permissions and configuration.

Choose the source you use today

Each source has its own scope. Review the import screen for the supported fields and any skipped records before confirming.

Import methods and scope
SourceMethodWhat to review
Planning CenterConnect an access token, or upload a People CSV exportThe connected importer supports multiple modules. People CSV is a narrower directory import; review the selected modules and preview.
BreezeConnect a Breeze API keyPeople, families and giving held in Breeze. Giving held separately in Tithe.ly needs its own import.
Tithe.lyUpload transactions and optionally people exportsDonor matching, dates, funds and giving totals.
ChurchTracUpload people and giving CSV reportsColumn mapping, households, people and giving totals.

Prepare, preview, then import

  1. Keep a backup or export from your current system and identify the source of truth.
  2. Choose the source in Import and supply the requested connection or files.
  3. Review the preview, mappings and skipped records. Nothing changes until confirmation.
  4. Confirm the import, then check representative families, dates, funds and totals.
  5. Introduce the new workflow to a small staff group before the wider rollout.

Know what needs separate setup

An import does not connect your payment processor, publish a branded app or copy every setting from another platform. Re-establish provider connections and review permissions. Do not assume recurring payment arrangements move with historical giving records.

Keep the transition manageable

The import tools support reruns using their source matching. Review the preview each time, keep your original files, and ask support about unclear results before creating a second set of records.

By Moriah LLC, makers of ChurchFoundry · Reviewed

Keep exploring

Related reading

Church Software Migration Checklist

A church software migration is a controlled move of records and responsibilities. Inventory what you have, confirm what the destination can import, test a small sample, reconcile the result, and name an owner for the transition before inviting everyone.

YOUR NEXT CHAPTER STARTS HERE

Make room for more ministry.

Bring your people. We’ll bring the tools.

Start your free trial 30 days free. No credit card required.