Before you replace Wild Apricot, compare the work involved

A dated website can make a platform change look like the only option. If your homepage feels crowded, members struggle to find events or staff hesitate to update pages, replacing everything can sound like a fresh start.

Before committing to that decision, separate the website problems from the membership-system requirements. A redesign may address the way information is presented and how people reach existing tools. A migration changes a wider set of arrangements that also needs to be understood.

The useful comparison is between two defined scopes, with the work, responsibilities and limitations visible on both sides.

Name the requirement behind the frustration

Start with what members or staff need to accomplish. “The website looks old” is a reasonable concern, but it is not yet a scope.

Write down the specific tasks: understanding membership benefits, finding an event, renewing, locating a restricted resource or updating a homepage announcement. Identify where each task becomes difficult.

Then separate presentation problems from requirements the current setup cannot meet. A confusing menu may call for clearer labels and page structure. A required connection to another business system needs a technical assessment. A change in membership rules may affect both the website and the administrative process.

This distinction helps a board evaluate whether the proposed project addresses the actual problem.

Define what improving the current site would involve

A redesign assessment should identify the pages, content and member journeys that need attention. It should also show which Wild Apricot tools stay in use and which areas staff will maintain after launch.

For example, consider a fictional association whose membership administration works adequately but whose events are buried in a crowded menu. One potential scope is clearer event discovery, better mobile presentation and more useful event introductions, leading into the existing registration process.

Review the existing theme, custom code, access rules and content quality to establish the work involved. Include a check of the complete registration journey in the proposed scope.

Some requirements may involve a connection rather than a replacement. Wild Apricot documents options including integrations, APIs and widgets in its integration overview. Whether any option fits your organization depends on the specific workflow and needs to be tested.

Give migration an equally complete scope

A migration proposal should account for more than building the new public pages. Ask the proposed provider to explain:

• Which contact and membership information will transfer, and how it will be checked.

• How member access, permissions and restricted resources will work.

• What happens to payment arrangements and recurring-payment authorization.

• Which events, forms, files, emails and integrations need rebuilding.

• How existing links will be handled and how members will learn the new routes.

• What staff training, launch coordination and ongoing maintenance are included.

Do not assume every record, configuration or payment arrangement can move unchanged. Ask for the actual transfer approach and any member action required. Assign responsibility for checking the result before the old setup is retired.

The answers give the board a clearer picture of the transition and its responsibilities.

Compare the first year of work

Put both proposals beside the same requirements. Include the project fee, subscriptions, custom functionality, staff preparation, review time, training and support arrangements. Distinguish confirmed inclusions from items still awaiting investigation.

Consider who will maintain each version. A lower initial build fee may leave important work outside the scope; a larger project may include requirements the organization does not currently need. Compare the deliverables rather than assuming either price tells the whole story.

If a necessary capability cannot be delivered reliably in the existing setup, that is a legitimate reason to assess alternatives. If the difficulty is primarily presentation and navigation, a focused redesign deserves a fair comparison.

Make the next decision smaller

Tamed Apricot helps organizations investigate what their Wild Apricot website could do better. We can discuss design directions using your own content, native gadgets your staff can edit, and separately scoped custom functionality or automation.

Our AI-assisted production approach aims to reduce repetitive build work while retaining human review. The appropriate scope and fee depend on your site; staying on Wild Apricot is not automatically the less expensive option.

Tell us what is making you consider leaving Wild Apricot. We can discuss the website problem, the requirements that matter and what an improvement project would need to establish.