Sustaining Fifty-Four Peer Networks: A Member Platform for the Association of Independent Colleges of Art + Design
Fifty-four mailing lists were how deans, registrars and Title IX coordinators at fifty art schools talked to their counterparts. The website around them was a wrapper — and the wrapper was out of road.
The work
The Challenge: Fifty-Four Listservs on a Platform Out of Road
AICAD is a consortium of roughly fifty independent colleges of art and design, and its member site was a website in the way a post office is a building. What members came for was the mail: fifty-four listservs organized by role, each one connecting a dean or a registrar or a Title IX coordinator to the small number of people at other member colleges who do the same job. For a school with a few hundred staff, that list is the entire professional peer group.
The platform underneath had reached the end of its release’s life, and the part that could not simply be upgraded was the part that mattered. List membership was built on Organic Groups, extended by ten custom modules — one of which received inbound email, tried to strip out-of-office replies with a filter of mail-client-specific regular expressions, and minted tokens that let an attachment download skip an access check. Organic Groups has no successor. The module that inherited the concept in later releases had gone to security-only maintenance, which is not a foundation to move a working community onto.
It was also, in places, not working. Attachment links arrived broken. Auto-responders posted into threads. Approving a member added them to a group and told them nothing, so someone sent the welcome by hand. And because there was no way to post one message to several lists, the administrator sent from Gmail instead — which failed above five lists, and failed by delivering to none.
The Strategy: Rebuild the Listservs, Keep Everything Else Still
Rebuild the thing members use. Keep everything else still.
- Workbench Access in place of Organic Groups, the same route taken when the Lifespan intranet met the identical wall — a second time makes it precedent rather than a hunch.
- The content architecture moved across unchanged, because redesigning the model and migrating it in one pass is two risks on a budget for one.
- Ten custom modules audited down to the ones with logic in them, since most turned out to be configuration exported as code by a tool Drupal has since replaced with real configuration management.
- Olivero, the platform’s own theme, as the front-end base, with the design hours concentrated on the homepage where they would show.
The Outcomes: 6,700 Memberships Moved Without a Password Reset
A membership community moved without asking its members to notice.
- Engagement | Fifty-four lists rebuilt and reconciled group by group, around 6,700 memberships in all | Over 9,000 forum threads moved across, so the archive of what the profession asked its peers survived the move
- Trust | Credentials and roles migrated intact, so no member met the new site through a password-reset email | Twelve weeks from kickoff to completion, and still the platform three years later, under continuous support
The detail
What the site was actually for
- Fifty-four lists, one per job. Chief Academic Officers. Admissions Directors. Library Directors. Title IX Coordinators. Campus Safety. Mental Health. Each list put a person in touch with the handful of people at other member colleges who do the same job — the peer group an art school of a few hundred staff does not have in-house.
- The lists were the reason to log in. Around 6,700 memberships across the fifty-four, and members who belonged to several. Beyond the lists there were documents, a school directory and a job board; the traffic was the mail.
- And the mail was not working properly. Discovery found attachment links arriving broken, out-of-office replies posting into threads that a filter of mail-client-specific regular expressions was supposed to catch, and approvals that added a member to a group without telling them — so an administrator sent the welcome note by hand, every time.
- The workaround had a hard ceiling. Posting one message to several lists at once was not a feature, so it was done from Gmail instead. Past five lists the send failed, and it failed by delivering to none of them.
Why the upgrade was not routine
- The membership model had no successor. List membership ran on Organic Groups, and Organic Groups has no upgrade path — the module that inherited the idea in later releases was in security-only maintenance, which is a poor thing to move a live community onto. This was the decision the engagement turned on, not the platform version.
- The answer came from another build. Workbench Access, the same route taken when the Lifespan intranet hit the identical wall. A second time is evidence rather than a hunch.
- Ten custom modules, and most of them were sediment. The audit sorted them: several were configuration exported as code by a tool the platform has since replaced with real configuration management, so they went. What remained was the part that mattered — the module handling inbound email, list subscriptions and the tokens that let an attachment download bypass an access check.
- The architecture was kept still on purpose. Content types, taxonomies and field structure moved across as they were. Redesigning the model and migrating it in the same pass is two risks priced as one, and the budget was for one.
The move
- Nine thousand threads, and the history mattered. Forum topics are the archive of what a profession asked its peers. Over 9,000 came across, with roughly 250 documents and about 50 school records.
- No one had to reset a password. Accounts migrated with credentials, field data and role assignments intact, so a member’s first encounter with the new site was the site — not a password-reset mail they had to be persuaded was legitimate.
- Membership was reconciled list by list. All fifty-four lists were counted on both sides and compared, group by group, rather than checking a total and calling it even. The gaps that remained were accounts the cleanup had already removed.
- Some of it was left behind, on purpose. A job content type of over 9,000 nodes retired in favor of a job board, events with nothing newer than 2018 dropped, and empty taxonomies — steering committees, professional interests — pruned rather than moved.
- A core theme instead of a bespoke one. The front end was built on Olivero, the platform’s own theme, with the design work concentrated on the homepage. On a lean engagement that is where the hours were worth spending.
Where it stands
- Twelve weeks, kickoff to completion. Technical audit in week two, information architecture and design through week four, development weeks five to eight, user acceptance testing weeks nine and ten.
- Still the platform, three years on. An upgrade-readiness review filed in August 2025 shows the site being assessed for the next major release — 26 of its projects already clear — which is the ordinary maintenance of something in service rather than something parked.
- And still supported. AICAD has kept a support retainer with the firm continuously since launch.
Community platform migration questions
How do you migrate an online community without losing members?
Move the accounts whole and count both sides. AICAD’s roughly 6,700 list memberships migrated with credentials, field data and role assignments intact — so no member met the new site through a password-reset email they had to be persuaded was legitimate — and all fifty-four lists were reconciled group by group rather than checked as a total.
Can listservs move to a new platform with their history?
Yes, and the history is the point. Forum topics are the archive of what a profession asked its peers, so over 9,000 threads came across, with roughly 250 documents and about 50 school records — while the mail itself was rebuilt to fix what discovery found broken: attachment links, auto-responders posting into threads, and silent approvals.
What should be left behind in a platform migration?
Whatever the community stopped using. AICAD’s migration retired a job content type of over 9,000 nodes in favor of a job board, dropped events with nothing newer than 2018 and pruned empty taxonomies — while a ten-module audit kept only the code with real logic in it. Migration is an editorial decision, not a transfer.
How long does a community platform migration take?
AICAD’s ran twelve weeks from kickoff to completion: technical audit in week two, information architecture and design through week four, development in weeks five to eight, user acceptance testing in weeks nine and ten.
What does a successful listserv migration look like?
For the AICAD platform by Pare & Co: fifty-four listservs rebuilt and reconciled, around 6,700 memberships and over 9,000 threads moved with no password reset asked of anyone, in twelve weeks — and the platform is still in service three years later, under a support retainer the association has kept continuously since launch.