Real-time
Two-way sync
Changes in Box or Sage X3 instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ ERP
Box to Sage X3 integration — real-time, two-way sync
Keep Box and Sage X3 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 Box and Sage X3
Move the documents and data that Sage X3 produces into Box as files, and let files stored in Box update the records they belong to in Sage X3, continuously and without exports or manual filing.
Sage X3 runs the business on structured records: Purchase Orders, Work Orders, Stock / Inventory by site, Bills of Material. Box holds files and the metadata that describes them: Metadata, Collaborations, Users, Groups. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Sage X3 touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Box, from signed contracts to vendor bills to receipts, describe a transaction Sage X3 needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.
Stacksync keeps Purchase Orders, Work Orders, Stock / Inventory by site, Bills of Material in Sage X3 and Metadata, Collaborations, Users, Groups in Box in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Box already labeled and filed, and metadata captured against a stored file can create or update the matching record in Sage X3. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.
The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Sage X3 and the file in Box never describe two different versions of the same document.
Common use cases
- 01 Publish per-site stock levels to storefronts and a WMS on a schedule.
- 02 Replicate GL journals and sales history to a warehouse for multi-company, multi-legislation reporting.
- 03 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
- 04 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
Common sync patterns
Where Box captures inbound files: details reach the record
A contract, vendor bill, or receipt added to Box with its details can create or update the matching record in Sage X3, so a document captured outside the finance system still reaches the books.
An archive that stays current
As records change in Sage X3, the corresponding files and metadata in Box are kept in step, so a stored document reflects the latest version rather than a stale one-time export.
Audit-ready retention
Every transaction's supporting file lives in Box beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Sage X3.
What you can sync between Box and Sage X3
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.
| Box objects | Sage X3 objects | How this pairing syncs | |
|---|---|---|---|
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Sales Orders Order documents written from external channels and read for fulfillment status. | Metadata is specific to Box and Sales Orders to Sage X3 — each maps to any object or custom field on the other side. | |
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Purchase Orders Procurement documents synced with supplier-facing systems. | Collaborations is specific to Box and Purchase Orders to Sage X3 — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Work Orders Production orders read by MES and scheduling integrations. | Users is specific to Box and Work Orders to Sage X3 — each maps to any object or custom field on the other side. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Stock / Inventory by site On-hand and allocated quantities per site, synced to storefronts and WMS. | Groups is specific to Box and Stock / Inventory by site to Sage X3 — each maps to any object or custom field on the other side. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Bills of Material Product structures read for planning and costing. | Tasks is specific to Box and Bills of Material to Sage X3 — each maps to any object or custom field on the other side. | |
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | GL Journals Financial entries replicated to warehouses for group reporting. | Events is specific to Box and GL Journals to Sage X3 — each maps to any object or custom field on the other side. |
How changes propagate between Box and Sage X3
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.
Box Sage X3 Sub-second propagation
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is applied to Sage X3 as a row-level write, with types converted between the two schemas.
Sage X3 Box Interval-based propagation
DetectionStacksync polls Sage X3 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
What ships with Box ⇄ Sage X3
Connect Box and Sage X3 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Sage X3 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Sage X3 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 Box or Sage X3 record.
Observability
Monitoring
Track your Box ⇄ Sage X3 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Box and Sage X3.
How the Box and Sage X3 connectors work
Box
- Integration surface
- REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
- Authentication
- OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
- Change detection
- V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
- Capabilities
- read · write · webhooks
- Rate limits
- Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
Sage X3
- Integration surface
- SOAP and REST web services published from X3 business objects; direct SQL access to the underlying database on-prem
- Authentication
- Dedicated web-service user credentials (Basic auth) against configured connection pools
- Change detection
- Scheduled polling; no general webhook surface on the classic web services layer
- Capabilities
- read · write
How it works
How to connect Box to Sage X3 — 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 Box and Sage X3 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Box
connected
Sage X3
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Sage X3 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 · Box ⇄ Sage X3Customers 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.
Box Sage X3Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Sage X3 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Sage X3: authenticate both systems, choose the objects to sync (such as Box's Metadata and Collaborations), 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 Box and Sage X3 records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Sage X3 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Sage X3 integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and Sage X3. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Box: V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed. On Sage X3: Scheduled polling; no general webhook surface on the classic web services layer. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Sage X3 side: Purchase Orders, Work Orders, Stock / Inventory by site, Bills of Material, plus custom fields where Sage X3 exposes them. On the Box side: Metadata, Collaborations, Users, Groups. Stacksync auto-detects both schemas and converts types between the two systems.
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 499 integrations available for Box and Sage X3.
Popular · 5 of 499
No integrations match .
