Skip to content
Database ⇄ Accounting and finance

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

Keep InterSystems IRIS and Pigment 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 Pigment

Work with Pigment's financial data straight from InterSystems IRIS: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Users and permissions, Applications, Metrics, Dimension lists from Pigment into Schemas, Persistent Classes, Globals, Namespaces in InterSystems IRIS and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against InterSystems IRIS, and rows your code writes or updates flow back into Pigment with validation, so the finance system stays the system of record.

Common use cases

  • 01 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • 03 Consolidate IRIS data with other databases in an analytics warehouse for cross-system reporting
  • 04 Keep reference data consistent between an IRIS-based clinical or financial application and downstream SaaS tools

Common sync patterns

Write back safely

Updates written to the synced tables in InterSystems IRIS propagate into Pigment, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Pigment appear in InterSystems IRIS as row changes, so you can trigger downstream logic with the database tooling you already use.

Query finance data like any other data

Customers, invoices, and payments from Pigment live in InterSystems IRIS as regular tables or collections your team can join, index, and query.

What you can sync between InterSystems IRIS and Pigment

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 Pigment objects How this pairing syncs
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Tables Row-based transactional data loaded into models from source systems Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Dimension lists Master data like accounts, products, or employees that metrics are sliced by Stored Procedures is specific to InterSystems IRIS and Dimension lists to Pigment — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Views is specific to InterSystems IRIS and Scenarios to Pigment — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Schemas is specific to InterSystems IRIS and Data imports to Pigment — 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. Users and permissions Access controls governing which model areas a sync can touch Persistent Classes is specific to InterSystems IRIS and Users and permissions to Pigment — each maps to any object or custom field on the other side.
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Applications Planning models organized by domain such as finance, sales, or workforce Globals is specific to InterSystems IRIS and Applications to Pigment — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Pigment

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 Pigment 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 Pigment through its API, with automatic retries and rate-limit backoff.

Pigment InterSystems IRIS Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

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.
  • Pigment: Subject to the platform's API rate limits.
What ships with InterSystems IRIS ⇄ Pigment

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever InterSystems IRIS or Pigment 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 Pigment record.

Observability

Monitoring

Track your InterSystems IRIS ⇄ Pigment 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 Pigment.

How the InterSystems IRIS and Pigment 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

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

How to connect InterSystems IRIS to Pigment — 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 Pigment 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
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the InterSystems IRIS and Pigment 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 ⇄ Pigment
    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 Pigment
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

InterSystems IRIS and Pigment 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

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

Popular · 4 of 374
All InterSystems IRIS integrations All Pigment integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own