How an association that runs membership, dues, events and certification in iMIS can bring members, organizations, renewal dates and engagement into HubSpot, so renewal and recruitment campaigns run on current membership data and contact preferences stay in step in both systems.
iMIS is where an association keeps its members, organizations, dues, events, committees and certifications. HubSpot is where it runs marketing, recruitment and member communication. Connecting the two lets renewal campaigns start from the real paid-through date, lets recruitment target lapsed and prospective members, and gives staff one engagement view of each member.
Public documentation, but production access needs vendor approval, certification, a paid license or a specific plan.
Open with conditions. The iMIS REST API is documented publicly. A dedicated API account is requested from ASI and may carry a license cost, and Change Notifications need additional licensing.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
iMIS exposes parties, groups, events and association-built queries through a documented REST API, with change events on top, so HubSpot can run renewal and recruitment on live membership data while iMIS stays the membership record.
Campaign Creators assessment
We found no HubSpot-built or ASI-built HubSpot app for iMIS, so this is a direct build on the iMIS REST API. CC's build reads people, organizations, membership and dues status, event registrations, committee and chapter roles, and certification credits into HubSpot. Communication preferences sync both ways. Dues collection, payments and member self-service stay in iMIS.
Ratings are CC judgments from ASI's public developer and help documentation. Licensing for the API user and Change Notifications is confirmed with ASI and the association during discovery.
The REST API covers Party, Person, Organization, GroupMember, Event and EventRegistration, and the IQA and Query endpoint returns any query the association builds. Change Notifications push person, organization, membership joined and renewed, and event registration events.
ASI asks integrations to run single-threaded, filter by UpdatedOn, avoid full-dataset pulls and poll no more than once an hour. The sync is designed around deltas and events from day one.
API access uses an account with the RemoteService role. ASI notes a dedicated API account may carry a cost, and Change Notifications need additional licensing. Both are confirmed before the SOW is signed.
Seven parts of iMIS matter to HubSpot. Most are read into HubSpot; communication preferences sync both ways; payments stay in iMIS.
Every individual and organization in iMIS. Each becomes a HubSpot contact or company, matched on the iMIS ID first and email second, with the employer link kept as an association.
Member type, member status, join date and paid-through date drive every renewal and recruitment campaign. They land on the contact, or on a membership custom object where an association tracks several memberships per person.
Conferences, webinars and meetings with each person's registration and status. Registrations become HubSpot records associated with the contact, so attendance feeds engagement scoring and follow-up.
Volunteer and geographic structure. Committee seats, chapter membership and section membership come from iMIS group membership and become HubSpot properties and lists.
Data the association already models in IQA, such as certification status, CE credit totals and gift summaries, is read through the query endpoint. The association owns the query; the integration reads its result.
Each association defines its own preference list in iMIS. The build maps each one to a HubSpot subscription type and keeps opt-ins and opt-outs in step in both directions.
Dues invoices and payments are processed in iMIS. ASI documents that credit card payments cannot be submitted through the REST API, so HubSpot renewal emails link members to iMIS to pay.
iMIS Change Notifications send events to a CC-hosted webhook endpoint. The integration layer fetches each changed record from the REST API, resolves it to one HubSpot contact or company, and writes in batches. An hourly delta job filtered by update time covers anything events do not send, and preference changes in HubSpot are written back to iMIS.
Membership, dues, payments and certification are recorded in iMIS. HubSpot holds what marketing needs to reach and segment members, and the history of that outreach.
Following ASI's guidelines, the sync reads only changed records and runs one job at a time. A full load happens once, at backfill, and is agreed with ASI.
An opt-out in either system reaches the other. HubSpot's global unsubscribe is never overwritten by a sync.
Each phase ends on a gate the association signs off before the next begins.
Confirm the iMIS edition and hosting, the membership model, event and certification use, and the preference list. Request the API user from ASI and confirm Change Notifications licensing.
Decide whether membership lives on the contact or on a custom object, and map member types, statuses, chapters and committees to HubSpot properties.
Map each iMIS communication preference to a HubSpot subscription type and agree which system wins in a conflict.
Create the custom properties, membership and registration objects, subscription types and property groups in a HubSpot sandbox.
Build the webhook receiver, delta scheduler, IQA reads, identity resolver, preference write-back and the error replay queue.
Load current members, organizations and an agreed history window in paced, single-threaded batches scheduled with ASI.
Run for two weeks with workflows paused, review data daily, then switch on renewal and recruitment workflows.
Entity names follow ASI's developer documentation. Fields described in plain words, such as paid-through date and member type, are confirmed against the association's iMIS data and queries during discovery.
| iMIS field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| People & organizations | ||||
| Party ID (iMIS ID) | im_imis_id | Contact | iM → HS | Primary match key. Unique. |
| Person name | firstname, lastname | Contact | iM → HS | iMIS-owned. |
| Primary email | Contact | ↔ Both | Match key #2. New HubSpot prospects create iMIS records only where agreed. | |
| Primary phone, address | phone, address, city, state, zip | Contact | iM → HS | |
| Organization ID and name | im_org_id, name | Company | iM → HS | Member organizations and employers. |
| Person's primary organization | Contact to company association | Contact | iM → HS | Employer link. |
| Membership & dues | ||||
| Member type | im_member_type | Contact | iM → HS | From the member type group (MT- prefix). Confirm in discovery. |
| Member status | im_member_status | Contact | iM → HS | Active, lapsed and so on. Values confirmed in discovery. |
| Join date | im_join_date | Contact | iM → HS | Confirm field in discovery. |
| Paid-through date | im_paid_through | Contact | iM → HS | Drives renewal workflows. Confirm field in discovery. |
| Membership joined event | im_last_join_event | Contact | iM → HS | From Change Notifications. |
| Membership renewed event | im_last_renewal_date | Contact | iM → HS | From Change Notifications. |
| Dues group (DUES) | Membership record | Membership | iM → HS | Where several memberships per person are tracked. |
| Events & registrations | ||||
| Event code and title | event name | Event registration | iM → HS | From the Event entity. |
| Event start date | im_event_start | Event registration | iM → HS | |
| Registration status | im_registration_status | Event registration | iM → HS | EventRegistration status values. |
| Registrant party | Registration to contact association | Event registration | iM → HS | |
| Events attended (count) | im_events_attended | Contact | iM → HS | Rolled up for engagement scoring. |
| Groups & credits | ||||
| Committee memberships (COMMITTEE) | im_committees | Contact | iM → HS | Multi-select of committee names. |
| Chapter (CHAPT) | im_chapter | Contact | iM → HS | Drives local campaigns. |
| Section memberships (SEC) | im_sections | Contact | iM → HS | |
| Certification status | im_certification_status | Contact | iM → HS | Read from an IQA query. Confirm in discovery. |
| CE credits earned in cycle | im_ce_credits | Contact | iM → HS | Read from an IQA query. Confirm in discovery. |
| Communication preferences | ||||
| Each iMIS communication preference | HubSpot subscription type status | Contact | ↔ Both | One-to-one map agreed in discovery. |
| Preference change | Subscription status change | Contact | ↔ Both | Most recent change wins; logged. |
| HubSpot global unsubscribe | Matching iMIS preferences set to opt out | Contact | HS → iM | Never reversed by the sync. |
| Do-not-contact flags | im_do_not_contact | Contact | iM → HS | Confirm field in discovery. |
Values below come from ASI's public developer and help documentation. Items without a published value are confirmed with ASI.
| Topic | iMIS | HubSpot |
|---|---|---|
| Access model | An account with the RemoteService role. A dedicated API account is requested from ASI Technical Support and may carry a license cost. | Private app access token or OAuth 2.0 public app, scoped per object. Custom objects need an Enterprise hub. |
| Interfaces | REST API at the site's /api/ path, JSON over HTTPS. Party, Person, Organization, GroupMember, Event and EventRegistration entities, plus the IQA and Query endpoint for association-built queries. | REST APIs: CRM objects, custom objects, associations, subscription preferences. |
| Authentication | POST to the site's /token endpoint for an access token, then send it as a Bearer token. Token lifetime: not published. Confirm with ASI. | Bearer token on every call. |
| Paging | Results arrive as a paged result with Offset, Limit, Count, TotalCount, HasNext and NextOffset. The default page is 100 results. | Cursor paging on search and list endpoints. |
| Rate limits | ASI's usage guidelines set a soft limit of about 5,000 requests per hour per client, one sync thread per client, polling no more than hourly, and UpdatedOn filters instead of full pulls. | Per-10-second burst and daily limits by subscription tier. |
| Change events | Change Notifications deliver events through Azure Event Grid to a webhook endpoint after a validation handshake. Events include Person, Organization and Party created or updated, Membership joined or renewed, and Event Registration created, updated or cancelled. Additional licensing applies. | Writes are immediate; HubSpot workflows trigger preference write-back. |
| Payments | Credit card payments cannot be submitted through the REST API. | HubSpot does not collect dues; renewal emails link to iMIS. |
Severity reflects impact on the SOW, not technical difficulty alone.
The dedicated API user and Change Notifications may each carry a cost. Without Change Notifications, the build relies on the hourly delta job, which is slower but complete.
Single-threaded jobs, hourly polling and no bulk downloads shape the design and the backfill plan. The backfill is scheduled with ASI.
Member types, status values and paid-through logic differ between associations. The membership model is signed before any field is built.
Two systems can change the same preference. The rule is agreed up front, and HubSpot's global unsubscribe always holds.
Certification and credit data often live in association-built queries. If a query changes, the sync breaks, so query names and columns are under change control.
Members can appear twice in iMIS or HubSpot. Matching on iMIS ID first and email second, with a review queue, prevents new duplicates.
Renewal sequences start from the paid-through date and stop the moment iMIS records the renewal, so paid members stop getting reminders.
Members who lapse move into a win-back track automatically, segmented by member type and chapter.
Event attendees, certification candidates and newsletter subscribers who are not members become a recruitment audience.
Events attended, committee seats, credits earned and email activity combine into one HubSpot score that flags at-risk members before renewal.
Chapter leaders and committee staff send to accurate lists without exporting from iMIS.
Members set preferences once, in either system, and both respect them.
The core flow follows a member through renewal. iMIS records the membership and payment; HubSpot handles the outreach around it.
All custom properties use the im_ prefix in an iMIS property group. Membership properties sit on the contact, or on a membership custom object if the association tracks several memberships per person.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| im_imis_id | iMIS ID | Contact | Single-line text | iMIS Party ID; unique |
| im_org_id | iMIS Organization ID | Company | Single-line text | iMIS Party ID of the organization; unique |
| im_member_type | Member Type | Contact | Dropdown | iMIS member type |
| im_member_status | Member Status | Contact | Dropdown | iMIS member status |
| im_join_date | Join Date | Contact | Date | iMIS join date |
| im_paid_through | Paid-Through Date | Contact | Date | iMIS paid-through date |
| im_last_renewal_date | Last Renewal Date | Contact | Date | Membership renewed event |
| im_chapter | Chapter | Contact | Dropdown | CHAPT group membership |
| im_committees | Committees | Contact | Multiple checkboxes | COMMITTEE group memberships |
| im_events_attended | Events Attended | Contact | Number | Count of attended registrations |
| im_certification_status | Certification Status | Contact | Dropdown | IQA query result |
| im_ce_credits | CE Credits This Cycle | Contact | Number | IQA query result |
Choose the areas and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation. Items marked for confirmation are checked against the association's iMIS site and licenses during discovery.
Yes, but access is open with conditions: ASI publishes iMIS's REST API documentation, but a dedicated API account must be requested from ASI and may carry a license cost, and Change Notifications need additional licensing. Campaign Creators builds a custom integration layer on Party, Person, Organization, GroupMember, Event and EventRegistration, plus the IQA and Query endpoint, once that account is in place.
Members, organizations, member type and status, join and paid-through dates, event registrations, committee and chapter roles, section memberships, certification status and CE credits sync from iMIS into HubSpot contacts, companies, and membership and event registration custom objects. Communication preferences sync both ways, and new HubSpot prospects can flow back to iMIS as Person records where agreed.
iMIS owns membership operations: dues invoices, card payments, certification records and member status are worked there, and ASI's API does not accept card payments, so HubSpot never collects or stores dues. HubSpot owns marketing and outreach, holding renewal and recruitment campaigns, engagement scoring and communication preferences, with HubSpot's global unsubscribe always honored over an iMIS preference.
Seven phases, each closed by a client sign-off: discovery that confirms the iMIS edition and requests the API user and Change Notifications licensing from ASI, mapping the membership model's types, statuses, chapters and committees, mapping communication preferences to HubSpot subscription types, building the HubSpot schema in a sandbox, the custom build of the webhook receiver and delta scheduler, a paced single-threaded backfill scheduled with ASI, and a two-week parallel run before renewal and recruitment workflows go live.
Timeline and cost depend on the association's membership model, how many chapters and committees are in scope, whether Change Notifications licensing is needed, and how many IQA queries drive certification and credit data. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.