Switching from Membership Toolkit to Golbi
A PTA, PTO, or booster migration off Membership Toolkit: which directory, membership, and dues records import cleanly, what happens to your store and fundraising history, and where paid hands-on migration takes over.
One place for the public website, private admin work, and safer member workflows.
What can come across, and how you get it here.
There is no automatic import from Membership Toolkit, and we will not market one. Each record type below names the rung of our migration ladder it is reached from — the self-serve rungs are free to do yourself, and the hands-on rungs are a paid, quoted service.
Directory contacts and families
Rung 1 — self-serve CSV import. Parent and student records with families linked together, imported with member-only visibility applied rather than published.
Membership records
Rung 1 — self-serve CSV import. Who is a member, at what level, and when that lapses.
Committees and volunteer groups
Rung 1 — self-serve CSV import. Standing committees and their members, imported as groups with role labels.
Dues balances
Rung 2 — guided migration kit. Paid and unpaid state with external payment references, as the starting point of your private ledger.
A directory exported as a formatted document
Rung 3 or 4 — assisted or white-glove, a paid service. Where the only export is a formatted directory rather than a data file, records are reconstructed from what you supply.
What stays behind — and why we say so up front.
How boards usually sequence the move.
Volunteer boards move over the summer, between school years. Import the directory and membership records first while the year is quiet, rebuild forms and public pages next, then hand the new workspace to the incoming board with dues balances loaded. Directory-only exports need a mapping conversation before the school year restarts.
Switching from Membership Toolkit: common questions.
What happens to our online store and fundraisers?
They do not transfer, and Golbi does not offer online donations, so treat that as a separate decision rather than part of the migration. Membership dues are different: those are tracked in a private ledger, with online collection gated on your plan and on connecting your organization's own payment account.
Is our family directory published publicly?
No. Directory records import with member-only visibility, and Golbi keeps a strict separation between public pages and member-only pages. Household, guardian, and child data stay explicitly scoped rather than being published by default.
Our export is a formatted directory, not a data file. Now what?
That is what the paid assisted and white-glove rungs handle. You supply what you have, we reconstruct the records and rebuild households, and you approve a preview before anything is written. It is a real project, not a button, and we price it that way.
How do we hand this to next year's board?
That is the argument for moving in the summer. Import the records, rebuild the pages, then hand over a workspace with scoped admin roles rather than a shared login — which is usually the actual problem a volunteer board is trying to solve.
Keep reading.
Pricing a move off Membership Toolkit?
Tell us what you're on and how messy the export is. We'll point you at the right rung of the ladder — self-serve, or a paid, hands-on migration.