The outcome
Members don’t see the difference between the website and the AMS. They see one organisation. They expect their member status to be reflected in the price they’re shown. They expect their event registrations to be visible in their account. They expect a profile change on the website to be reflected the next time they log in. They expect the staff member who picks up the phone to see the same record they see.
Inside most associations, the website and the AMS are different products run by different people on different release cycles. Without proper integration, the gaps show up as friction the member experiences directly. They renew online and their member directory entry doesn’t update for two days. They pay for an event and the receipt arrives from a different email address than the rest of the association’s communications. They update their address in the website profile and the magazine still ships to the old one.
The outcome is invisibility. Two systems, one experience. The member never knows there are two systems. The team never types the same data into two places. The data the website shows is the data the AMS holds, in real time, with no overnight sync that catches errors twelve hours after the member’s seen them.
What the integration looks like to the member
Nothing. That’s the point.
The member logs in to the website and sees their current member status, their current CPD points, their current event registrations, their current invoices. They update their email address on the website and it’s their email address everywhere by the time they close the tab. They register for an event on the website and the event is in their account, the registration is in iMIS, the receipt is in their inbox, the calendar invite is in their calendar.
If they call the office about something, the staff member sees what the member sees, plus an audit trail of what the member’s done in the last six months. There’s no “let me check if your renewal went through, I’ll have to look in the other system.”
The absence of friction is the experience.
What the integration looks like to the team
The team stops reconciling. The membership officer doesn’t have to compare website registrations against iMIS records to find the ones that didn’t sync. The communications team doesn’t have to maintain a separate mailing list. The events team doesn’t have to manually mark attendees as paid in iMIS after they’ve paid on the website.
What they do instead is the work the data was supposed to support. Engagement analysis. Targeted communications. Strategic decisions about which content drives renewal. The data is reliable because it’s all coming from the same source, and that means the decisions made from the data are reliable too.
For the development team, integration is no longer a project that consumes a quarter every time something changes. New web services, new pages, new member features can be built quickly because the integration patterns are reusable.
Why this was hard before, and why it isn’t now
iMIS-and-website integration has historically been the place that good projects went to die. Every association has an iMIS implementation with its own customisations, its own custom fields, its own business rules. Every website has its own CMS, its own templating, its own development cycle. Connecting them reliably required either extensive custom development for that specific pair, or a generic integration layer that didn’t actually meet the association’s needs.
What’s changed is a reliable pattern: a standard integration toolkit that lets web services connect Kentico (or another modern CMS) to iMIS in real time, using a single API that’s been built and refined across many implementations. A new web service is now a few days of work, not a few months. A change to one system no longer breaks the other.
The deeper change is structural. When the integration is reliable, the design conversation changes. Teams stop saying we’d like to do X but the systems can’t talk to each other. They start designing member experiences from the member’s point of view and trusting the integration to support whatever they specify.
The proof: associations running this outcome with 3DN
Royal Australian College of General Practitioners, the development-team productivity story
RACGP couldn’t meet their needs through the all-in-one iMIS solution and needed the specialist tools of a best-of-breed website CMS. 3DN provided the Compass Web Services to RACGP’s development team to connect to iMIS and access the member information stored there. When the College moved their website to Kentico, 3DN’s integration suite carried the relationship forward. The development team were up and running with iMIS connectivity with only three days of support. The migration to Kentico was seamless, and the team can now leverage services in both Kentico and the previous platform concurrently for an easy migration.
AIM WA, the data quality story
Previous firms had struggled to integrate with the underlying iMIS AMS, resulting in data quality issues. When 3DN delivered a suite of real-time web services covering event calendars, event pricing, booker registration, invoice payment, and contact management, online registrations boomed and staff time on the phone collecting registration details and improving data quality dropped sharply. The data was right because the systems were finally agreeing about what the data was.
Legal Practice Board of Western Australia, the deep integration story
LPBWA’s Kentico site was integrated to iMIS for roles, authentication, real-time search, and certificate processing. The Howler messaging suite added accountable communications. The result is a website where the public can search for admitted practitioners in real time, where the team can administer content easily, where the Board’s staff spend less time on website maintenance tasks they used to outsource, and where the practitioner-facing experience and the back-of-house data are the same view of the same records.
Kentico | iMIS Synchronisation Bridge, the underlying pattern
The Synchronisation Bridge is the engineering layer underneath several of these stories. Define a content type in Kentico, link properties to iMIS fields, and the structured content fills itself. Create a new event in iMIS and a Kentico stub appears, ready for content. The pattern lets associations build sophisticated member-facing experiences while keeping their authoritative data in iMIS, where it belongs.
Australian Dental Association, the long-term version
ADA manages its online presence through a Kentico website with fully comprehensive, real-time integration to iMIS. The CPD portal, congress sites, and member self-service all rely on the same underlying integration. Years of stable, real-time integration are what make the member-facing products feel coherent.
Where this outcome applies
Every association running a member-facing website with an AMS sitting behind it. The pattern is universal, the implementation differs by stack. Associations using iMIS, especially, have a well-developed set of integration patterns to draw from. Associations using other AMS platforms, Salesforce, Aptify, MemberPro, Microsoft Dynamics, can apply the same principles with different connectors.
The outcome matters most when member-facing experience is a competitive issue. Bodies whose members have a choice about renewing benefit most. Bodies whose members are mandatory will benefit too, but the urgency is different.
Related work and tools
The Royal Australian College of General Practitioners, AIM WA, the Legal Practice Board of Western Australia, and the Australian Dental Association are the four primary proof points for this outcome, each illustrating a different angle: RACGP shows the development-team productivity gain, AIM WA shows the data-quality and registration-conversion gain, LPBWA shows what’s possible when integration runs deep across many systems, and ADA shows the long-term version where stable integration enables a portfolio of member-facing experiences. Adjacent work at the Queensland Law Society shows the website-modernisation companion to AMS integration, and the Kentico/iMIS Synchronisation Bridge is the structured-content pattern that runs underneath several of these stories.
The tools that supported this outcome were Kentico as the CMS, iMIS as the AMS, 3DN’s integration toolkit including Compass Web Services and the Synchronisation Bridge, Howler as the communications channel that benefits from clean integrated data, and Power BI as the visibility layer that becomes possible when the data agrees with itself. The integration outcome is the result of the design philosophy, two systems and one experience, more than any specific tool.
