This page contains the setup guide and reference information for the iMIS integrations.

Prerequisites

An active iMIS account with credentials that have access to run Instant Queries
The iMIS host URL (e.g., your-org.imis.com)
The Instant Query name provided by your iMIS administrator (e.g., $/YourOrg/QueryName)
(Optional) An OpenWater Client Key and API Key for attendee enrichment

Setup guide

Step 1: Set up the iMIS integration in Swapcard

Sign in to your Swapcard account.
Navigate to your Event page within the Communities section.
In the left navigation bar, go to Event Builder, then select Integrations.
On the integration selection page, choose iMIS from the list of integrations.
To activate the integration, you will need three parameters:
1. Username — iMIS username with access to run the query
2. Password — iMIS password
3. Host — your iMIS instance URL (e.g., your-org.imis.com)
Once connected, configure the Instant Query name — this is the path to the query your iMIS administrator has set up (e.g., $/YourOrg/QueryName).
(Optional) To enable OpenWater enrichment, provide the following additional parameters:
1. OpenWater Client Key
2. OpenWater API Key
Enable the Attendees object and configure field mappings — choosing which provider fields map to which Swapcard fields or custom fields.

Your iMIS event has been successfully linked with your Swapcard event.

You have the flexibility to adjust your integration settings according to the specific data requirements. It's crucial to highlight that the synchronization will only begin when you manually start the integration process and finish the necessary mapping.

Supported sync modes

The iMIS integration supports the following sync modes :

Feature	Supported?
Full Refresh	Yes

The iMIS integration does not support incremental sync. All registrants are fetched on every sync run — there is no delta query or date filter sent to iMIS.

Supported streams

This integration supports one stream: Attendees.

Data is exported from iMIS via Instant Queries (IQA) — named query templates built by the organization's iMIS administrator. Each query returns a flat list of records with named fields. The columns returned depend entirely on how the query was configured in iMIS.

Capturing deleted records

The iMIS integration does NOT capture deletions for records. When a record is deleted on iMIS, it needs to be MANUALLY deleted on Swapcard accordingly.

Stream Dependencies

The iMIS integration utilizes the Registrant ID field from the Attendees stream as the primary identifier.

Client ID format: IMIS-{Registrant ID}

These linked records are stored within the Client Id field on the People record on the Swapcard side.

Streams supporting fields

Attendees

These fields come directly from the iMIS Instant Query response. Their availability depends on what columns are included in the query template.

Attendee Field	Mapping Label	Type
`Registrant ID`	Registrant ID	`string`
`FirstName`	First Name	`string`
`LastName`	Last Name	`string`
`Email`	Email	`string`
`Company`	Company	`string`
`Status`	Status	`string`

The exact set of available fields is determined by the Instant Query definition in iMIS — additional columns can be added by the iMIS administrator and will automatically become available as provider fields in the integration.

Default Swapcard mappings:

Provider Field	Swapcard Field
`Registrant ID`	client_id
`FirstName`	first_name
`LastName`	last_name
`Email`	email
`Company`	company

OpenWater Enrichment

When OpenWater credentials are provided alongside the iMIS credentials, attendee records are enriched with profile data from OpenWater. The integration matches iMIS attendees to OpenWater users by comparing the Registrant ID (iMIS) with the thirdPartyUniqueId field on the OpenWater user account.

Matched attendees receive additional fields from the OpenWater User Profile Form Template, available under the OpenWater. prefix.

The firstName, lastName, and emailAddress OpenWater profile fields are intentionally excluded — these are already covered by the iMIS standard fields FirstName, LastName, and Email.

If an iMIS attendee has no matching OpenWater user, they are synced with iMIS standard fields only. OpenWater enrichment is additive — it never blocks the sync.

Enhancement

Please be aware that any enhancements to this integration, which encompass any requirements not covered by the existing integration state, will be subject to custom development processes and associated costs.