Integration Products | Campaign Creators

iMIS HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 19, 2026, 6:37:02 AM
Integration Assessment
Integration Assessment · Associations

iMIS × HubSpot

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 REST APIBearer token authIQA and Query endpointChange NotificationsMembers, dues and eventsTwo-way preferences
Platform ownerASI (Advanced Solutions International)
Integration typeCustom build on the iMIS REST API
Primary directioniMIS → HubSpot, preferences both ways
FeasibilityStrong fit
API accessOpen with conditions
01 — Summary

Does iMIS integrate with HubSpot?

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.

API access
Open APIOpen with conditionsGated API

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.

Scorecard
API accessDedicated API user
Public docsGood, some gaps
Call budget~5,000/hour soft
Build complexityModerate

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.

Strength

Documented REST API with change events

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.

Plan for

ASI's usage guidelines

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.

Gate

API user and licensing

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.

02 — API modules

Which iMIS APIs does the integration use?

Seven parts of iMIS matter to HubSpot. Most are read into HubSpot; communication preferences sync both ways; payments stay in iMIS.

Core

Parties: people & organizations

/api/Party · Person · Organization

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.

  • Person and Organization are subclasses of Party
  • iMIS ID stored on every HubSpot record
  • Paged results with Offset, Limit and NextOffset
Core

Membership & dues

Member type groups · DUES · Subscription

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.

  • Member type groups use the MT- prefix
  • Dues and subscriptions sit in DUES and SUBS groups
  • Membership joined and renewed events
Core

Events & registrations

Event · EventRegistration

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.

  • Event registration created, updated and canceled events
  • Registration status from the EventRegistration entity
  • Registrant groups use the EVENT- prefix
Core

Committees & chapters

GroupMember · COMMITTEE · CHAPT · SEC

Volunteer and geographic structure. Committee seats, chapter membership and section membership come from iMIS group membership and become HubSpot properties and lists.

  • Group roles kept with each membership
  • Chapter drives local event and dues campaigns
  • Committee members excluded from recruitment sends
Flexible read

IQA & Query endpoint

Association-built queries via REST

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.

  • Default 100 results per page
  • ASI is moving IQA calls to the Query endpoint
  • Query names and columns agreed in discovery
Two-way

Communication preferences

Settings › Contacts › Communication preferences

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.

  • One iMIS preference to one HubSpot subscription type
  • Most recent change wins, with an audit trail
  • Global unsubscribes in HubSpot are always honored
Stays in iMIS

Payments & dues collection

Commerce · invoices · card payments

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.

  • HubSpot never collects or stores card data
  • Paid-through date returns to HubSpot after payment
  • Gift detail only by summary, where approved
03 — Framework

How does the iMIS HubSpot integration work?

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.

iMIS
iMIS REST APIParty, Person, Organization, GroupMember, Event, EventRegistration
IQA and Query endpointassociation-built queries: credits, certification, gifts
Change Notificationsperson, organization, membership and registration events
Communication preferencesper-contact opt-in and opt-out
CC integration layer
Event receiverhandles validation, fetches each event subject
Delta schedulerUpdatedOn filters, single-threaded, hourly
Identity resolveriMIS ID · email
Preference reconcilermost recent change wins, audit log
HubSpot writerbatch upserts, associations, replay
HubSpot
Contactsmembers, nonmembers, preferences
Companiesmember organizations, employers
Memberships (custom object or contact properties)type, status, join and paid-through dates
Event registrations (custom object)event, status, attendance
Lists, workflows & scoresrenewal, recruitment, engagement
iMIS → HubSpot (people, organizations, membership, events, groups and credits)HubSpot → iMIS (communication preference changes, new prospects where agreed)
Principle

iMIS owns the member, HubSpot runs the outreach

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.

Principle

Deltas and events, never full pulls

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.

Principle

Preferences are shared, consent is respected

An opt-out in either system reaches the other. HubSpot's global unsubscribe is never overwritten by a sync.

04 — Process

What does iMIS HubSpot integration setup involve?

Each phase ends on a gate the association signs off before the next begins.

1

Discovery & access

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.

Gate to next phaseSigned system map and API access confirmed
2

Membership model

Decide whether membership lives on the contact or on a custom object, and map member types, statuses, chapters and committees to HubSpot properties.

Gate to next phaseSigned membership model and value tables
3

Preference mapping

Map each iMIS communication preference to a HubSpot subscription type and agree which system wins in a conflict.

Gate to next phaseSigned preference map
4

HubSpot setup

Create the custom properties, membership and registration objects, subscription types and property groups in a HubSpot sandbox.

Gate to next phaseSchema approved in sandbox
5

Custom build

Build the webhook receiver, delta scheduler, IQA reads, identity resolver, preference write-back and the error replay queue.

Gate to next phaseAll agreed areas syncing in sandbox
6

Backfill

Load current members, organizations and an agreed history window in paced, single-threaded batches scheduled with ASI.

Gate to next phaseMember counts and paid-through dates reconcile to iMIS
7

Parallel run & launch

Run for two weeks with workflows paused, review data daily, then switch on renewal and recruitment workflows.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the iMIS HubSpot integration sync?

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 fieldHubSpot propertyObjectDirectionNotes
People & organizations
Party ID (iMIS ID)im_imis_idContactiM → HSPrimary match key. Unique.
Person namefirstname, lastnameContactiM → HSiMIS-owned.
Primary emailemailContact↔ BothMatch key #2. New HubSpot prospects create iMIS records only where agreed.
Primary phone, addressphone, address, city, state, zipContactiM → HS
Organization ID and nameim_org_id, nameCompanyiM → HSMember organizations and employers.
Person's primary organizationContact to company associationContactiM → HSEmployer link.
Membership & dues
Member typeim_member_typeContactiM → HSFrom the member type group (MT- prefix). Confirm in discovery.
Member statusim_member_statusContactiM → HSActive, lapsed and so on. Values confirmed in discovery.
Join dateim_join_dateContactiM → HSConfirm field in discovery.
Paid-through dateim_paid_throughContactiM → HSDrives renewal workflows. Confirm field in discovery.
Membership joined eventim_last_join_eventContactiM → HSFrom Change Notifications.
Membership renewed eventim_last_renewal_dateContactiM → HSFrom Change Notifications.
Dues group (DUES)Membership recordMembershipiM → HSWhere several memberships per person are tracked.
Events & registrations
Event code and titleevent nameEvent registrationiM → HSFrom the Event entity.
Event start dateim_event_startEvent registrationiM → HS
Registration statusim_registration_statusEvent registrationiM → HSEventRegistration status values.
Registrant partyRegistration to contact associationEvent registrationiM → HS
Events attended (count)im_events_attendedContactiM → HSRolled up for engagement scoring.
Groups & credits
Committee memberships (COMMITTEE)im_committeesContactiM → HSMulti-select of committee names.
Chapter (CHAPT)im_chapterContactiM → HSDrives local campaigns.
Section memberships (SEC)im_sectionsContactiM → HS
Certification statusim_certification_statusContactiM → HSRead from an IQA query. Confirm in discovery.
CE credits earned in cycleim_ce_creditsContactiM → HSRead from an IQA query. Confirm in discovery.
Communication preferences
Each iMIS communication preferenceHubSpot subscription type statusContact↔ BothOne-to-one map agreed in discovery.
Preference changeSubscription status changeContact↔ BothMost recent change wins; logged.
HubSpot global unsubscribeMatching iMIS preferences set to opt outContactHS → iMNever reversed by the sync.
Do-not-contact flagsim_do_not_contactContactiM → HSConfirm field in discovery.
06 — Auth & API

How are authentication and API limits handled?

Values below come from ASI's public developer and help documentation. Items without a published value are confirmed with ASI.

TopiciMISHubSpot
Access modelAn 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.
InterfacesREST 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.
AuthenticationPOST 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.
PagingResults 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 limitsASI'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 eventsChange 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.
PaymentsCredit card payments cannot be submitted through the REST API.HubSpot does not collect dues; renewal emails link to iMIS.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Licensing for API access and eventsHigh

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.

ASI usage guidelinesHigh

Single-threaded jobs, hourly polling and no bulk downloads shape the design and the backfill plan. The backfill is scheduled with ASI.

Membership model varies by associationMedium

Member types, status values and paid-through logic differ between associations. The membership model is signed before any field is built.

Preference conflictsMedium

Two systems can change the same preference. The rule is agreed up front, and HubSpot's global unsubscribe always holds.

Data held in IQA queriesMedium

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.

Duplicate recordsLow

Members can appear twice in iMIS or HubSpot. Matching on iMIS ID first and email second, with a review queue, prevents new duplicates.

Opportunities in HubSpot

Renewal campaigns on real datesHigh value

Renewal sequences start from the paid-through date and stop the moment iMIS records the renewal, so paid members stop getting reminders.

Lapsed member win-backHigh value

Members who lapse move into a win-back track automatically, segmented by member type and chapter.

Recruitment from nonmembersHigh value

Event attendees, certification candidates and newsletter subscribers who are not members become a recruitment audience.

Member engagement scoreMedium value

Events attended, committee seats, credits earned and email activity combine into one HubSpot score that flags at-risk members before renewal.

Chapter and committee outreachMedium value

Chapter leaders and committee staff send to accurate lists without exporting from iMIS.

One preference recordMedium value

Members set preferences once, in either system, and both respect them.

Renewal cycle

From renewal notice to paid-through date, in one loop.

The core flow follows a member through renewal. iMIS records the membership and payment; HubSpot handles the outreach around it.

  1. The paid-through date syncs from iMIS; HubSpot starts the renewal sequence for the member's type and chapter.
  2. Emails link the member to iMIS to renew and pay. HubSpot never touches payment.
  3. iMIS records the renewal; the event reaches HubSpot and the sequence stops.
  4. Members who pass the paid-through date without renewing move to win-back, and the engagement score flags who to call first.
08 — Property schema

Which HubSpot properties does the integration create?

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 nameLabelObjectTypeSource / logic
im_imis_idiMIS IDContactSingle-line textiMIS Party ID; unique
im_org_idiMIS Organization IDCompanySingle-line textiMIS Party ID of the organization; unique
im_member_typeMember TypeContactDropdowniMIS member type
im_member_statusMember StatusContactDropdowniMIS member status
im_join_dateJoin DateContactDateiMIS join date
im_paid_throughPaid-Through DateContactDateiMIS paid-through date
im_last_renewal_dateLast Renewal DateContactDateMembership renewed event
im_chapterChapterContactDropdownCHAPT group membership
im_committeesCommitteesContactMultiple checkboxesCOMMITTEE group memberships
im_events_attendedEvents AttendedContactNumberCount of attended registrations
im_certification_statusCertification StatusContactDropdownIQA query result
im_ce_creditsCE Credits This CycleContactNumberIQA query result
09 — Scope builder

Interactive scope builder

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.

Scope summary

0Fields
0Inbound
0Write-back
iMIS × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

iMIS HubSpot integration FAQ

Does iMIS integrate with HubSpot?

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.

What data syncs between iMIS and HubSpot?

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.

Which system owns which data?

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.

What does setting up the iMIS HubSpot integration involve?

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.

How long does the integration take and what does it cost?

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.