Skip to content
Database ⇄ CRM

InterSystems IRIS to Vitally integration — real-time, two-way sync

Keep InterSystems IRIS and Vitally in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect InterSystems IRIS and Vitally

Treat Vitally like part of your database: its records live in InterSystems IRIS as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in InterSystems IRIS, where it can be queried and joined like everything else.

Stacksync mirrors Conversation, NPS Response, Custom Trait, Account from Vitally into Globals, Namespaces, Stored Procedures, Tables in InterSystems IRIS with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Vitally with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • 01 Push billing and subscription changes from an ERP or billing system into Vitally to keep success playbooks accurate.
  • 02 Keep CS tasks and notes aligned between Vitally and ticketing or project tools.
  • 03 Replicate IRIS tables to Postgres so application teams can build against a familiar database
  • 04 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access

Common sync patterns

Trigger workflows from CRM changes

Field and stage updates in Vitally arrive as row changes in InterSystems IRIS, ready to drive jobs and notifications.

Query the CRM like a database

Accounts, contacts, and custom objects from Vitally become tables in InterSystems IRIS you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to InterSystems IRIS sync onto the matching records in Vitally, giving go-to-market teams live product context.

What you can sync between InterSystems IRIS and Vitally

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

InterSystems IRIS objects Vitally objects How this pairing syncs
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. NPS Response NPS survey responses for account-health reporting. Globals is specific to InterSystems IRIS and NPS Response to Vitally — each maps to any object or custom field on the other side.
Namespaces Namespaces partition databases and determine the connection context for integrations. Custom Trait Custom account and user traits for segmentation. Namespaces is specific to InterSystems IRIS and Custom Trait to Vitally — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Account Core customer account records with health scores and lifecycle traits; created, updated, retrieved, and listed via the REST API. Stored Procedures is specific to InterSystems IRIS and Account to Vitally — each maps to any object or custom field on the other side.
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. User End users tied to accounts, including activity and custom traits. Tables is specific to InterSystems IRIS and User to Vitally — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. Organization Parent organizations for hierarchical B2B account structures. Views is specific to InterSystems IRIS and Organization to Vitally — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Task CS tasks and follow-ups, readable and writable for workflow sync. Schemas is specific to InterSystems IRIS and Task to Vitally — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Vitally

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

InterSystems IRIS Vitally Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

DeliveryEach detected change is written to Vitally through its API, with automatic retries and rate-limit backoff.

Vitally InterSystems IRIS Sub-second propagation

DetectionVitally notifies Stacksync of record changes through webhook events. Incremental polling on updatedAt cursors.

DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
  • Vitally: Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
What ships with InterSystems IRIS ⇄ Vitally

Connect InterSystems IRIS and Vitally for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Vitally connection.

Real-time

Two-way sync

Changes in InterSystems IRIS or Vitally instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever InterSystems IRIS or Vitally data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single InterSystems IRIS or Vitally record.

Observability

Monitoring

Track your InterSystems IRIS ⇄ Vitally sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Vitally.

How the InterSystems IRIS and Vitally connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits

Vitally

Integration surface
REST API with cursor-based pagination (sortable by createdAt/updatedAt)
Authentication
API key via Basic Auth; keys created in Settings -> Integrations -> REST API and individually revocable
Change detection
Incremental polling on updatedAt cursors; playbook-triggered webhooks can push events for near real-time updates
Capabilities
read · write · webhooks
Rate limits
Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
How it works

How to connect InterSystems IRIS to Vitally — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate InterSystems IRIS and Vitally with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    InterSystems IRIS connected
    Vitally connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the InterSystems IRIS and Vitally objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · InterSystems IRIS ⇄ Vitally
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    InterSystems IRIS Vitally
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

InterSystems IRIS and Vitally integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 390 integrations available for InterSystems IRIS and Vitally.

Popular · 8 of 390
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.