Skip to content

iMIS integration

Change it once in iMIS. Every other system follows.

We connect iMIS to your website, email tool, payments and reporting so your team stops keying the same record into four places. iMIS stays your system of record.

The problem iMIS sites share

The record is right in iMIS and out of date everywhere else

An event is set up in iMIS with its dates, pricing and venue, then typed again into the website. A list is exported from iMIS and uploaded to the email tool, and the people who unsubscribed last month have to be removed by hand. A card payment fails and the only detail anyone can find is that it was declined.

None of that is a fault in iMIS. It is the gap between iMIS and the other systems an association runs, and in most offices a staff member fills it every week.

What changes

The systems around iMIS read from it and write back to it

Set up
once

Events and courses publish from iMIS to the website

Our Kentico and iMIS synchronisation bridge links website page types to iMIS fields. Dates, pricing and venue come from iMIS; the web team adds the content iMIS doesn’t hold.

Two
way

Email lists come from the member database

A saved query becomes an email group, a contact change reaches the email tool within minutes, and an unsubscribe is written back to the member record.

No
login

Members renew and register from a personal link

1-Click renewal and event registration send each member a link that opens their own renewal or offer, so a forgotten password doesn’t stop a renewal.

The
reason

Failed payments say why they failed

Our gateway provider sits between iMIS and the card gateway and records the rejection reason, so finance can sort declines by cause instead of chasing each one.

Over
time

Reports show trends, not only today

iMIS keeps each member’s current status. We save the membership counts every night and show the trend in Power BI, so you can say how many financial members a branch had three months ago.

Over
night

Rules that someone applied by hand run on their own

Regions, groupings and flags that follow from other fields are set by a scheduled update in iMIS rather than by a staff member working through a list.

What doesn't change

iMIS stays, and so does your iMIS partner

Nothing is replaced. The integrations work with the iMIS you already run, alongside whoever already supports it, and your staff keep working in iMIS the way they do now.

When we need realistic data to build and test against, we run our anonymisation scripts over a copy of the database first, so the copy we work on has no real names, addresses or payment details in it.

Proof

Legal Practice Board of Western Australia

The Board’s renewal checks CPD compliance, conditions, trust account approvals and PII declarations. Practitioners see one guided flow with a single submit. iMIS holds the records, ProcessMaker runs the validation, Kentico carries the renewal pages, Howler sends the notifications and Power BI gives management a live view.

We have also connected iMIS to Kentico websites for the Australian Dental Association, the Royal Australian College of General Practitioners and AIM WA.

Read how the Board's renewal works · See an email sync, step by step · Membership trends from a system that only knows today

Five things to check on your own iMIS

Answer these about last month

1

When an event changed in iMIS, how many other places did someone update by hand?

2

How does your email tool find out that a member has lapsed or unsubscribed?

3

When a card payment failed, could anyone see why?

4

Can you say how many financial members you had on this date last year?

5

Which of your regular reports starts with an export to a spreadsheet?

If one of those took a staff member an afternoon, we'd like to hear about it.

Send a note about where your team re-keys data today. It comes straight to Jay McCormack, co-founder.