Move active and historical commitments into Planning Center so a campaign in progress keeps running — and so last year's numbers still mean something.
Pledges are the data type with the shortest fuse. Giving history can be imported a month after launch without much harm. Notes can wait a week. A capital campaign cannot pause while somebody retypes four hundred commitments — and the cost of getting it wrong is not an internal inconvenience, it is asking a family to complete a pledge they finished paying last spring.
Planning Center now imports donations, and it has always imported people by CSV. Pledges have no equivalent path. Without a tool, a church mid-campaign is choosing between recreating every commitment by hand and running two systems in parallel until the campaign closes — which in practice means the old system stays alive, and paid for, months longer than planned.
This is the one sequencing recommendation worth insisting on. A pledge is only meaningful next to the giving that fulfils it. Import pledges alone and every commitment in Planning Center reads as outstanding, regardless of what was actually paid.
So move giving history and pledges in the same migration, then verify progress against a handful of donors you know well before any statement, reminder, or campaign update goes out. Imports are unlimited within your access window, so that verification step costs nothing but an afternoon.
Churches doing both usually find the Everything Bundle cheaper than buying giving and pledges separately — and it coversgroup memberships andnotes as well.
Not natively. Planning Center’s donation import tool covers giving, and people import by CSV, but pledges — the commitments behind a campaign — have no built-in import path. Without a tool they have to be recreated by hand or abandoned mid-campaign.
Both. Active commitments move so a campaign in progress keeps running, and historical commitments move so that prior campaigns still report correctly. Dropping fulfilled pledges makes every year-over-year comparison wrong from the migration date onwards.
Pledges are only meaningful next to the giving that fulfils them, which is why most churches import pledges and giving history together. A pledge that arrives without its donations reads as unfulfilled, and a donor being asked to complete a commitment they already completed is the kind of error that costs more than the migration did.
Yes, though the sequence matters. Import giving history and pledges together, then verify progress against a handful of known donors before you send anything to anyone. Imports are unlimited within your access window, so verifying costs nothing.
Port charges $99 for unlimited pledge imports with 180 days of access — the lowest-priced of the four data types. There are no per-record fees and no volume tiers.
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.
