How a 35-school California PTA council centralized email for 47,000 families.

The setup they had

A council of PTAs in California supports 35 school PTAs and reaches roughly 47,000 families. Each school runs its own newsletter, and the council sends district-wide communications on top of that.

On paper, everything ran through one Constant Contact account. In practice:

• 35 school editors shared 5 logins, passing two-factor authentication codes around by text message every newsletter cycle.
• The council-wide list and the per-school lists lived side by side in one account, so any editor could touch any school's audience.
• Every June, board turnover meant hunting down whoever held the passwords, and hoping the outgoing editor remembered to hand off.
• At peak, the council's schools send close to 280,000 emails in a single month. That volume ran through infrastructure nobody on the board actually controlled day to day.

None of this was anyone's fault. It is what happens when a volunteer organization grows one school at a time on tooling designed for a single sender.

What they actually needed

The council's requirements were structural, not feature-driven:

1. Every school sends independently with its own audience and its own look.
2. The council keeps centralized administration: one bill, one contact structure, one place to manage the annual district list refresh.
3. Every editor gets their own login. No shared passwords, no authenticator relay.
4. Newsletters keep sending from the organization's own domains, fully authenticated, so deliverability does not depend on any volunteer's personal address.
5. The migration could not fall on volunteers, and no school could miss a newsletter cycle during the switch.
6. Nonprofit pricing, with invoicing and purchase orders for the treasurer's records.

How the transition worked

The work fell on Mailsoftly, not on the board:

• A head start before day one. Migration work began ahead of the subscription start date: account setup, domain authentication, contact import, and the per-school list structure.
• Templates rebuilt for every school. Email templates cannot be exported from Constant Contact, so each school's current newsletter layout was recreated in Mailsoftly from recent copies. Every editor logged in for the first time and found their own newsletter waiting.
• Lists moved cleanly, unsubscribes included. Contacts exported from Constant Contact as standard spreadsheets and imported with the council-wide and per-school structure intact, including unsubscribe records, so the council stayed compliant from the first send.
• No gap in service. The old account stayed active until every school had sent successfully from the new one.

Training matched how volunteer organizations actually work: a live working session for council admins covering the annual district list refresh and per-school administration, plus a recorded walkthrough for school editors that next year's volunteers can watch when they take over.

The structure now

• One council-wide list plus a list for each of the 35 schools, about 47,000 contacts in total, with capacity to 50,000.
• An individual login for every school editor and council admin.
• Every sending domain in the structure fully authenticated with SPF, DKIM, and DMARC, on a dedicated IP pool.
• Peak months of close to 280,000 emails, with comfortable headroom above that.
• Editor turnover is planned for, not feared: a new volunteer's first newsletter is open template, edit, send, with the recorded training permanently available to the council.

This story is published anonymized. The structure, the numbers, and the transition steps are drawn directly from the council's migration records.