Two-way sync
Changes in InterSystems IRIS or Vitally instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Field and stage updates in Vitally arrive as row changes in InterSystems IRIS, ready to drive jobs and notifications.
Accounts, contacts, and custom objects from Vitally become tables in InterSystems IRIS you can join with application data directly.
Signup, usage, or lifecycle changes written to InterSystems IRIS sync onto the matching records in Vitally, giving go-to-market teams live product context.
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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Vitally connection.
Changes in InterSystems IRIS or Vitally instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS or Vitally data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single InterSystems IRIS or Vitally record.
Track your InterSystems IRIS ⇄ Vitally sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Vitally.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between InterSystems IRIS and Vitally: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Globals and Namespaces), map fields visually, and changes propagate both ways in milliseconds — no code required.
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Vitally: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Vitally: No native change-data-capture stream; incremental sync relies on updatedAt-sorted cursor pagination. InterSystems IRIS: Standard JDBC and ODBC drivers are available, which lets IRIS participate in database-style sync pipelines without a vendor-specific client. Stacksync's field mapping accounts for these differences between InterSystems IRIS and Vitally without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means InterSystems IRIS and Vitally records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed InterSystems IRIS and Vitally connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom InterSystems IRIS–Vitally integration in-house.
Yes — Stacksync ships production-grade connectors for both InterSystems IRIS and Vitally. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 390 integrations available for InterSystems IRIS and Vitally.