Two-way sync
Changes in Acumatica or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica and Iterable in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. Acumatica holds exactly that: Invoices, Purchase Orders, Stock Items, Shipments that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.
Stacksync syncs Invoices, Purchase Orders, Stock Items, Shipments in Acumatica with Lists, Catalogs, Commerce / Purchases, Export data in Iterable in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Iterable works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Iterable flow back onto the record in Acumatica.
The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.
Orders, invoices, and revenue totals from Acumatica land on the matching contact or account in Iterable, so audiences are built from what customers actually bought and spent rather than from guesses.
Because Acumatica knows who is already a paying customer, Iterable can exclude them from acquisition campaigns or single them out for renewal and cross-sell.
A person or company's contact details corrected in either system update the other, so marketing and the back office stop maintaining separate versions of the same record.
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.
| Acumatica objects | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. | Opportunities and Cases is specific to Acumatica and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side. | |
| Customers AR master data synced with CRMs and billing tools. | Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. | Customers is specific to Acumatica and Export data to Iterable — each maps to any object or custom field on the other side. | |
| Vendors Supplier records aligned with procurement and AP automation. | Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. | Vendors is specific to Acumatica and Users to Iterable — each maps to any object or custom field on the other side. | |
| Sales Orders Order documents created from e-commerce and CRM systems, read back for fulfillment status. | Events Custom and system events tracked via /api/events/track and /api/events/trackBulk (up to 1000 events per call); a single user's event history is read via GET /api/events/{email}. | Sales Orders is specific to Acumatica and Events to Iterable — each maps to any object or custom field on the other side. | |
| Invoices AR and AP billing documents synced for payment tracking and CRM visibility. | Campaigns Email, SMS, push, and in-app sends; metadata and metrics read via GET /api/campaigns and /api/campaigns/metrics, created and sent via /api/campaigns/create and /api/campaigns/trigger. | Invoices is specific to Acumatica and Campaigns to Iterable — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. | Purchase Orders is specific to Acumatica and Templates to Iterable — 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.
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.
DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.
DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.
DeliveryEach detected change is written to Acumatica through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Iterable connection.
Changes in Acumatica or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or Iterable data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Acumatica or Iterable record.
Track your Acumatica ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and Iterable.
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 Acumatica and Iterable 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 Acumatica and Iterable 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 Acumatica and Iterable: authenticate both systems, choose the objects to sync (such as Acumatica's Opportunities and Cases and Customers), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Acumatica and Iterable records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Acumatica and Iterable connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Acumatica–Iterable integration in-house.
Yes — Stacksync ships production-grade connectors for both Acumatica and Iterable. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Acumatica: Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields. On Iterable: System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Acumatica side: Invoices, Purchase Orders, Stock Items, Shipments, plus custom fields where Acumatica exposes them. On the Iterable side: Lists, Catalogs, Commerce / Purchases, Export data. Stacksync auto-detects both schemas and converts types between the two systems.
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 476 integrations available for Acumatica and Iterable.