Three realistic ways to get your data into Planning Center: Port, PCOMVP, and Planning Center's own donation import. Here is what each one actually handles — including where we are not the right answer.
We sell one of these, so read this with that in mind. What we have tried to do is make every claim checkable: everything stated about Planning Center's native import and about PCOMVP is drawn from their own public documentation and linked at the bottom of this page.
The short version: if you are only moving donations and your data is already clean, use Planning Center's own tool — it is free and it works. The other two exist for everything that sits outside that case.
| Port | PCOMVP | Planning Center native | |
|---|---|---|---|
| Giving / donation history | Yes | Yes | Yes |
| Group memberships | Yes | No | No |
| Pastoral notes | Yes | Yes | No |
| Pledges | Yes | Yes | No |
| In-kind donations | Yes — dedicated provider | Not stated | No — explicitly unsupported |
| Check records with routing / account fields | Yes — Check provider | Yes — RDC import | Payment method only |
| Pricing model | Flat, unlimited per data type | Tiered by record volume | Included with Planning Center |
| Cost to move 65,000 donations | $499 — same as any volume | Highest volume band | Free, if your CSV is already correct |
| Fund mapping | Magic Map proposes matches | Manual | Funds must exist beforehand |
| Source systems with a built-in parser | 21, plus Open Import for anything else | "Over 30" systems, plus any CSV | One prescribed CSV format |
| How you run it | Guided web app | Downloaded desktop app | Inside Planning Center |
| Undo window | Re-run within your access window | Not stated | Two weeks |
Competitor details verified 27 July 2026 from public documentation. "Not stated" means we could not find a published answer, not that the feature is absent.
Planning Center added a donation import tool, and for a straightforward giving migration it is genuinely the right answer — it is included, it is supported by the people who built the platform, and there is no third party in the loop.
Its published limits define where it stops:
Most importantly, it covers donations only. Group memberships, pastoral notes, and pledges have no native import path at all.
PCOMVP is the established third-party option and aPlanning Center integrations directory partner. It imports donations, notes, pledges, and check data via RDC, works with a stated "over 30" systems, and offers both one-time migration pricing and low monthly subscriptions for ongoing imports.
Two structural differences from Port:
If what you want is a cheap monthly subscription to keep pushing small donation batches into Planning Center on an ongoing basis, PCOMVP is built for that and Port is not. Port is built for the migration itself.
Port covers all four data types, including the group memberships neither other option handles, and prices each one flat and unlimited: Giving $499, Group Memberships $249, Notes $249, Pledges $99, or $999 for all four. It ships purpose-built parsers for 21 source systems plus Open Import for anything that produces a CSV, and dedicated In-Kind and Check providers for the records the native tool rejects.
The flat pricing matters in one specific case: large or long-established churches. At 2,000 donations most tools cost about the same. At 65,000 records across fifteen years, unlimited and volume-banded produce very different invoices.
Tell us what you are coming from and what you need to keep. If the honest answer is that Planning Center's own import will do it, we will tell you that.
Supported systems
Port ships a purpose-built parser for each of these, so your export is understood on upload instead of reshaped by hand. Coming from something else? Open Import handles any system that produces a CSV.
