Is your AMS the problem? A guide to deciding whether it's time to switch

Most associations do not arrive at an AMS selection process by choice. They arrive because something broke, or finally stopped working well enough to ignore, or because a deadline appeared on the horizon that made deferring the question no longer feasible. But platform end-of-life is just one version of the pressure. Board frustration, staff turnover that exposes how much institutional knowledge lived outside the system, a renewal cycle that takes three people to manage, a report request the system can't answer: all of these are the same question in different clothing.

The question is: is the AMS actually the problem?

It is worth sitting with that for a moment. Because sometimes it isn't. And starting a selection process when the real constraint is something else entirely is one of the more expensive mistakes an association can make, in money, staff time, and organizational disruption.

This section of our guide is designed to help you answer that question with some rigor before you go further. Not to talk you out of switching if a switch is genuinely needed, but to make sure you're solving the right problem.

When the AMS isn't the culprit

There is a pattern that experienced AMS vendors recognize quickly in early sales conversations, and it is uncomfortable to say out loud: the association sometimes is the problem, not the platform. Staff who have never been trained properly on the current system. Processes that were built around workarounds so long ago that no one remembers the underlying logic. Data that has never been cleaned, consolidated, or governed. A new executive director who arrived with strong opinions about the previous platform and made “new AMS” a proxy for “new direction.”

None of this means the current platform is necessarily right for the organization. But it does mean that replacing it without addressing these underlying issues will reproduce them in the new system, often faster, because the new platform will be configured around the same broken processes with the same people running them.

Before concluding that the AMS is the problem

Before concluding that the AMS is the problem, audit the following honestly.

If the honest answer to these questions is that the problems are real and the current platform cannot solve them even with investment in training, process redesign, and vendor engagement, then you are in the right place.

The signs that the platform genuinely is the limiting factor

There is a meaningful difference between a system that is underused and a system that cannot do what you need, even when used well. Here is what the latter looks like in practice.

You are building a parallel stack to compensate

The most reliable indicator that an AMS has reached its limits is the number of other tools that have grown up around it to fill the gaps. A separate email platform because the built-in communications are inadequate. An external event system because the AMS can’t handle delegate management at the scale you need. A learning management system with a fragile integration that breaks every time either platform updates. A spreadsheet that someone runs every Monday morning to reconcile data between systems.

AAPL, the national association for land professionals, recognized this pattern clearly when it began building the case for a switch. The organization was running six separate platforms alongside its core AMS, each filling a gap the primary system couldn’t address, and paying more than $200,000 a year for the privilege. “It wasn’t even working,” recalls Andrea Spencer, Director of Communications. “We were literally hemorrhaging money to make it work, and it still didn’t work.” Every gap-filling tool added another integration to maintain, another login for staff to manage, another data silo that required manual reconciliation.

Your reporting requires manual assembly

If the answer to “how many members do we have right now?” involves pulling a spreadsheet, running a query, or waiting until tomorrow for an overnight sync, that is a structural problem. Real-time reporting should be a baseline capability. When AAPL was on its legacy platform, basic membership figures required custom SQL queries from a systems analyst. As Spencer describes it: “We always had to do it manually and add it to our reports. We never could pull a number out about a segment of our membership. Never, ever, ever.”

The switch to a unified platform changed this entirely. “When our president calls and asks how many members we have, I don’t have to say ‘let me pull a report’. I can just look up the live number.”

Every change costs money or time you don’t have

A platform that requires vendor involvement for minor configuration changes, at significant cost, is not a sustainable long-term investment. AAPL’s experience with its previous vendor is representative of a wider pattern: “We wanted an add-on for a question in the renewal process, and that was basically a $30,000 add-on.” If your current system has made even small improvements prohibitively expensive, the total cost of staying is higher than the annual license fee suggests.

Your core member-facing processes are friction-heavy

If members frequently abandon the renewal journey, struggle to book event places, or require staff assistance to complete tasks they should be able to handle independently, the member experience problem is likely a platform problem. NACA, the national campus activities association, found that its events booking process required members to contact staff directly because the system was too heavily customized to be self-service. After switching to a unified platform, the organization recovered 32 hours a week in staff time and reduced its renewals team from three people to one. The staff time didn’t disappear; it was redirected to work that actually required human judgment.

You can no longer update to the latest version due to over-customization

Over years of bespoke development, a platform can quietly drift from the product the vendor actually supports. Every custom field bolted on, every workflow rewired to suit a particular process, every report rebuilt against a non-standard data model makes the next upgrade harder to swallow. Eventually you reach a point where moving to the current release means redoing much of what you have, and so the upgrade is deferred again. Meanwhile, the gap widens. New features are released to other associations that are unavailable to you. Security patches require careful regression testing against your customizations. Support becomes harder because your version is no longer one the vendor team works with day-to-day.

The platform you are paying for is not the platform you are running, and the difference grows each year. Associations in this position often discover that the cost of catching up has crept past the cost of switching entirely, and that the customizations protecting them from the upgrade are the very things keeping them on a version the vendor no longer fully supports.

Your certification, credentialing, or CEU processes are managed outside the system

For associations whose core member benefit is a professional credential, a certification program, or a continuing education record, running these processes through manual workarounds is a specific and serious risk. Paper-based processes introduce errors, create compliance exposure, and produce a member experience that reflects badly on the credential itself. AAPL’s certification program, which manages a three-tier credentialing system covering thousands of active candidates, had become an administrative ordeal. Processing a single applicant’s documents required a certification administrator to navigate ten steps just to verify that sponsor forms were completed correctly. “A lot of people wouldn’t even go through it. It was just such a pain,” Spencer recalls. After the switch, end-to-end certification review, approval, and exam setup went from four to six weeks to two weeks or less.

A note on association type

The signs above apply broadly, but how much weight you give each one depends on what kind of association you are running.

Trade associations tend to feel the reporting and segmentation problems most acutely. Complex membership hierarchies, with corporate members of varying sizes and different contact relationships within each organization, create data management challenges that simple CRM tools weren’t built for.

Professional societies are often most constrained by the credentialing and CEU limitations. If your platform can’t manage the certification lifecycle natively, you are either running manual workarounds or paying for a specialist integration that adds cost and fragility.

Medical and scientific societies sit at the intersection of both: complex credentialing requirements alongside high expectations for data accuracy, given the professional and regulatory context members operate in.

AMC-managed organizations have an additional consideration. If your association management company runs your platform on behalf of multiple clients, your individual needs have to be weighed against what that shared environment can accommodate. A constraint that looks like a platform limitation may actually be a contract or configuration limitation within a multi-tenant setup.

Small-staff associations (five or fewer full-time equivalents) should apply a different primary filter than larger organizations. For small teams, the question is not “what can the platform do?” but “what can our team actually operate?” A feature-rich platform that requires significant technical capacity to configure and maintain is a poor choice for a team that doesn’t have that capacity. Prioritize operability over functionality breadth.

The cost of staying: what "doing nothing" actually looks like

One of the more reliable patterns in AMS selection is that the financial case for switching is framed around the cost of the new platform, while the cost of staying on the current one is treated as a baseline. It isn’t.

The cost of staying includes the visible line items (annual license fees and any ongoing customization costs) and also the less visible ones. Staff time spent on manual processes that a better-configured system would automate. The portion of a systems analyst’s week consumed by writing SQL queries that shouldn’t need to exist. The event registrations that don’t complete because the booking journey is too slow or complicated. The members who don’t renew because the process is too hard. The leadership time spent in board meetings explaining data discrepancies that come from reconciling two systems that don’t sync in real time.

These costs are real. They are also rarely calculated, which means the business case for switching is typically underestimated and the case for staying is implicitly overstated.

If you are building the case for a switch, or anticipating the conversation with your board, start by quantifying one or two of these. Not every one. One concrete number, grounded in how your organization actually works, carries more weight than a theoretical total cost of ownership model. AAPL’s $200,000-a-year technology bill for a stack that still didn’t work was that number. NACA’s 32 hours a week in recoverable staff time was another version of it.
 

What comes next

If you have worked through this section and concluded that a switch is genuinely warranted, the next step is not finding a vendor. It is getting your own house in order: documenting your requirements, cleaning your data, and building the internal case for the investment. That is what the rest of this guide covers.

Download the AMS selection checklist before you go further. It covers building the board case, assessing staff readiness, gathering requirements, and scoring vendors, and is designed to be used as a working reference throughout the process rather than read once at the start.

When you are ready to begin formal evaluation, Part 2 covers the selection process in full: how to write an effective RFP, how to run a demo that tells you what you actually need to know, how to evaluate total cost of ownership across vendors, and what a realistic implementation timeline looks like.

Want to read more from the AMS buying guide?

31 Jul 2026

Choosing and switching your AMS: AMS evaluation checklist

A four-section checklist to guide your AMS selection process from building the board case through to scoring vendors.

Guides

31 Jul 2026

How to select the right AMS: a guide to running a rigorous evaluation process

A step-by-step guide to running an AMS selection process that produces a reliable outcome; covering RFP structure, demo scripting, vendor reference calls, and five-year cost modelling.

Guides

31 Jul 2026

Preparing for your ReadyMembership implementation: what to expect and how to get ready

A practical guide to what a ReadyMembership implementation actually involves; the phases, the timeline, data migration, and the internal readiness work that decides whether it goes smoothly.

Guides