Two-way sync
Changes in Box or SAP Business ByDesign instantly reflect in both systems. No stale data, no manual imports.
Keep Box and SAP Business ByDesign in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
SAP Business ByDesign runs the business on structured records: Opportunities, Projects, Employees, Business Partners (Accounts). Box holds files and the metadata that describes them: Events, Files, Folders, Metadata. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record SAP Business ByDesign 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 SAP Business ByDesign 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 Opportunities, Projects, Employees, Business Partners (Accounts) in SAP Business ByDesign and Events, Files, Folders, Metadata 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 SAP Business ByDesign. 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 SAP Business ByDesign and the file in Box never describe two different versions of the same document.
Files that SAP Business ByDesign produces land in Box labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.
Record fields from SAP Business ByDesign, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Box, so storage stays organized without anyone tagging by hand.
A contract, vendor bill, or receipt added to Box with its details can create or update the matching record in SAP Business ByDesign, so a document captured outside the finance system still reaches the books.
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 | SAP Business ByDesign objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Sales Orders Order documents created from external channels and read for status. | Collaborations is specific to Box and Sales Orders to SAP Business ByDesign — 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. | Customer Invoices Billing documents synced outward for collections and CRM visibility. | Users is specific to Box and Customer Invoices to SAP Business ByDesign — 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. | Materials / Products Item master data aligned with e-commerce and inventory systems. | Groups is specific to Box and Materials / Products to SAP Business ByDesign — 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. | Purchase Orders Procurement documents exchanged with supplier systems. | Tasks is specific to Box and Purchase Orders to SAP Business ByDesign — 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. | Opportunities Built-in CRM records synced with external sales tools when both are in use. | Events is specific to Box and Opportunities to SAP Business ByDesign — each maps to any object or custom field on the other side. | |
| Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. | Projects Project structures and tasks read for time and billing integrations. | Files is specific to Box and Projects to SAP Business ByDesign — 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.
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 written to SAP Business ByDesign through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls SAP Business ByDesign for changes on an incremental schedule, reading only records changed since the previous pass. Polling on last-changed timestamps.
DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–SAP Business ByDesign connection.
Changes in Box or SAP Business ByDesign instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Box or SAP Business ByDesign data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Box or SAP Business ByDesign record.
Track your Box ⇄ SAP Business ByDesign sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Box and SAP Business ByDesign.
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 Box and SAP Business ByDesign 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 Box and SAP Business ByDesign 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 Box and SAP Business ByDesign: authenticate both systems, choose the objects to sync (such as Box's Collaborations and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the SAP Business ByDesign side: Opportunities, Projects, Employees, Business Partners (Accounts), plus custom fields where SAP Business ByDesign exposes them. On the Box side: Events, Files, Folders, Metadata. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Box and SAP Business ByDesign: Documents filed with their context; Metadata that files itself; Where Box captures inbound files: details reach the record. Files that SAP Business ByDesign produces land in Box labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.
Box: 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. SAP Business ByDesign: SOAP web services plus OData services for analytical and custom data access. Authentication: Basic authentication over TLS for service users; OAuth-based options exist for certain scenarios. Stacksync manages authentication, retries, and rate limits on both sides.
SAP Business ByDesign: Documents follow ERP posting semantics: released and posted documents are corrected through follow-on documents, not in-place edits, which syncs must respect. Box: Server-auth apps (JWT or CCG) act through a service account and only see content that account owns or is collaborated on, unless enterprise as-user or admin scopes are granted. Stacksync's field mapping accounts for these differences between Box and SAP Business ByDesign without custom code.
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 507 integrations available for Box and SAP Business ByDesign.