Real-time
Two-way sync
Changes in InterSystems IRIS or MongoDB instantly reflect in both systems. No stale data, no manual imports.
Database
InterSystems IRIS to MongoDB integration — real-time, two-way sync
Keep InterSystems IRIS and MongoDB 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 MongoDB
Keep InterSystems IRIS and MongoDB synchronized in real time, across engines, regions, or services, in one or both directions.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between InterSystems IRIS and MongoDB continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Common use cases
- 01 Replicate IRIS tables to Postgres so application teams can build against a familiar database
- 02 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
- 03 Consolidate documents from multiple clusters or tenants into a single warehouse-facing store.
- 04 Sync MongoDB collections with a CRM so customer documents written by the application appear as CRM records, and CRM edits flow back as document updates.
Common sync patterns
Migration with zero-downtime cutover
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Shared reference data between services
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
What you can sync between InterSystems IRIS and MongoDB
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 | MongoDB objects | How this pairing syncs | |
|---|---|---|---|
| Views SQL views expose curated slices of data for outbound replication. | Views Read-only aggregation-defined sources for filtered sync datasets. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Documents BSON records created, updated, and deleted during syncs, keyed by _id. | Namespaces is specific to InterSystems IRIS and Documents to MongoDB — 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. | Embedded documents and arrays Nested structures that syncs flatten or map to related records in relational targets. | Stored Procedures is specific to InterSystems IRIS and Embedded documents and arrays to MongoDB — 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. | Indexes Keep lookups by sync key fast on large collections. | Tables is specific to InterSystems IRIS and Indexes to MongoDB — each maps to any object or custom field on the other side. | |
| Schemas Schema organization scopes which tables a sync connection can see. | Change streams The oplog-backed event feed that powers real-time change capture. | Schemas is specific to InterSystems IRIS and Change streams to MongoDB — each maps to any object or custom field on the other side. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | GridFS files Chunked file storage whose metadata can be referenced by synced documents. | Persistent Classes is specific to InterSystems IRIS and GridFS files to MongoDB — each maps to any object or custom field on the other side. |
How changes propagate between InterSystems IRIS and MongoDB
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 MongoDB 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 applied to MongoDB as a row-level write, with types converted between the two schemas.
MongoDB InterSystems IRIS Sub-second propagation
DetectionChanges in MongoDB are captured at the source via change data capture — no polling loop against its API. MongoDB oplog and change streams (requires the database to run as a replica set — even single-node).
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.
What ships with InterSystems IRIS ⇄ MongoDB
Connect InterSystems IRIS and MongoDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–MongoDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever InterSystems IRIS or MongoDB 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 MongoDB record.
Observability
Monitoring
Track your InterSystems IRIS ⇄ MongoDB 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 MongoDB.
How the InterSystems IRIS and MongoDB 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
MongoDB
- Integration surface
- MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management
- Authentication
- Database credentials (username/password) or TLS/SSL X.509 certificate (.pem upload), entered individually or via a MongoDB connection string (SRV or standard); Stacksync IP allowlisting required
- Change detection
- MongoDB oplog and change streams (requires the database to run as a replica set — even single-node); Stacksync leverages these built-in tools to track changes in real time
- Capabilities
- read · write · CDC
How it works
How to connect InterSystems IRIS to MongoDB — 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.
- 01
Connect your apps
Authenticate InterSystems IRIS and MongoDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
InterSystems IRIS
connected
MongoDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the InterSystems IRIS and MongoDB 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.
objects · InterSystems IRIS ⇄ MongoDBCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
InterSystems IRIS MongoDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
InterSystems IRIS and MongoDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between InterSystems IRIS and MongoDB: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Views and Namespaces), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
InterSystems IRIS: InterSystems positions IRIS as the successor to Caché, and it is widely deployed under healthcare and financial applications. MongoDB: Replica set configuration is required even for a single node — standalone MongoDB cannot be change-tracked. Stacksync's field mapping accounts for these differences between InterSystems IRIS and MongoDB 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 MongoDB 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 MongoDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom InterSystems IRIS–MongoDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both InterSystems IRIS and MongoDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. On MongoDB: MongoDB oplog and change streams (requires the database to run as a replica set — even single-node); Stacksync leverages these built-in tools to track changes in real time. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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
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 501 integrations available for InterSystems IRIS and MongoDB.
Popular · 6 of 501
-
InterSystems IRIS ⇄ Airtable -
InterSystems IRIS ⇄ AWS Aurora MySQL -
MongoDB ⇄ SAP ASE (Sybase) -
MongoDB ⇄ Scaleway Postgres -
MongoDB ⇄ TiDB -
MongoDB ⇄ TimescaleDB
No integrations match .
