Most association website projects don’t fail because of the code. They fail because of a breakdown in the relationship between the humans involved.
There are many ways the wheels can fall off. Maybe your current agency lacks the specific association expertise you need. Maybe the technical debt has become unmanageable. Or maybe the communication has simply stalled.
But you still need them. They have the keys to your server. They understand the quirks of your AMS integration. They are the ones you call when the site goes down at 5:00 PM on a Friday.
So, with that, the thought of telling them you’re moving can be stressful. It’s not uncommon for associations to wait too long to say anything. Or they try to hide the new project until the very last minute.
The Risk of the "Silent" Transition
Avoiding the conversation creates a massive operational risk for your association.
When an agency feels blindsided, their motivation to help with the transition drops. You might see slower response times on critical tickets. Previously simple tasks suddenly require a formal request. Things like that.
Worse, your new partner is left flying blind. They need to know how the current site is hosted, where the API keys are stored, and what workarounds are keeping the member portal running. If the outgoing agency isn't looped in, your new team will waste dozens of hours—and a ton of your budget—trying to reverse-engineer a system that someone else already understands.
And if a security patch is needed during the six-month redesign period? You need both teams to cooperate. A cold relationship makes that simple task a nightmare.
A Practical Timeline for the Conversation
You don’t need to announce your search the moment you write the RFP. But you shouldn't wait until the new site is ready to launch.
The right time to talk is usually right after you have signed the contract with your new partner.
At this stage, the project is real. You have a timeline. You have a new team ready to ask questions. This is when you should schedule a brief, professional call with your current account manager.
Don't do this over email if you can avoid it. A ten-minute conversation preserves the professional bridge.
How to Frame the News
Keep it direct. Avoid making it personal or listing a grievance of past mistakes. This is a business decision based on the future needs of the association, not a trial of the agency’s past performance.
Focus on the shift in your requirements. You might say:
"We’ve decided to move in a different direction for the upcoming redesign to align with some specific member experience goals and new integration requirements. We’ve selected a new partner to lead the build, but we value the work you’ve done to keep us running. We want to make sure this transition is handled professionally for both sides."
This approach does three things:
1. It establishes that the decision is final.
2. It acknowledges their contribution.
3. It sets the expectation for a professional handoff.
Setting the Ground Rules for the Handoff
Once the news is out, you need to define the "Maintenance Period." This is the time between the announcement and the launch of the new site.
Ask for a transition document or a "technical exit interview." Your new agency should provide a list of specific questions. They’ll need to know about:
* Hosting environments and server access.
* Third-party plugin licenses and ownership.
* Documentation for custom-coded integrations with your CRM or AMS.
* A list of scheduled cron jobs or automated tasks.
Be prepared to pay for this time. Transitioning a site is a service. If you treat it as a billable project, the outgoing agency is much more likely to provide high-quality documentation.
Managing the Two-Agency Dynamic
For a few months, you will be managing two vendors. This requires clear boundaries.
Let your current agency know they are still responsible for the "uptime" and security of the current site. They are the stewards of the legacy system.
Let the new agency know they are responsible for the "future" state. They should not be making changes to the live site without coordinating with the current team.
And if there is a conflict? You are the lead. You decide which team handles what. Don't let the agencies debate technical specs in a vacuum. Bring them together once or twice to ensure the handoff of data and assets is clear.
The Outcome of a Clean Break
When you handle the transition with solid communication, the project moves faster. Your new partner gets the information they need without the guesswork. Your current partner feels respected and stays responsive to your support needs.
Most importantly, your staff stays focused on the member experience instead of refereeing vendor disputes.
A website redesign is a major investment. Don't let a messy breakup with an old partner get in the way of a successful launch with a new one.
If you’re planning a redesign and need a partner who knows how to navigate the technical and professional realities of a transition, let’s chat.
