Real-time
Two-way sync
Changes in Box or MySQL instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Database
Box to MySQL integration — real-time, two-way sync
Keep Box and MySQL 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 MySQL
Keep MySQL and Box in step: a row in MySQL for every file in Box, with names, paths, metadata, and status staying consistent in real time, in both directions.
A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in MySQL says a file exists and carries its name, location, and status, while Box holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.
Stacksync syncs Tables, Views, Columns, Primary and Unique Keys in MySQL with Metadata, Collaborations, Users, Groups in Box bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.
Common use cases
- 01 Expose SaaS objects as MySQL tables so legacy internal tools built on MySQL can read live business data
- 02 Replicate ERP master data (customers, items, pricing) into the MySQL databases behind storefronts and portals
- 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
Records that point at documents
Where a record in MySQL references a file in Box, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.
A landing zone for incoming files
Files that arrive in a folder or bucket in Box become rows in MySQL as they land, so a database-driven process can pick them up without polling the storage system's API.
Continuous archival to file storage
Rows from MySQL are written out to Box as files on a schedule or as they change, giving a durable, low-cost copy for backup, compliance, or a data lake, without a custom export job to maintain.
What you can sync between Box and MySQL
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 | MySQL objects | How this pairing syncs | |
|---|---|---|---|
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Stored Procedures Server-side logic that can post-process synced rows. | Users is specific to Box and Stored Procedures to MySQL — 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. | Triggers An alternative change-capture mechanism when binlog access is unavailable. | Groups is specific to Box and Triggers to MySQL — 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. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Tasks is specific to Box and Databases (Schemas) to MySQL — 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. | Tables The primary sync target; rows map to records in connected systems. | Events is specific to Box and Tables to MySQL — 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. | Views Read-side projections used as outbound sync sources. | Files is specific to Box and Views to MySQL — each maps to any object or custom field on the other side. | |
| Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. | Columns Field-level mapping targets with engine-typed values. | Folders is specific to Box and Columns to MySQL — each maps to any object or custom field on the other side. |
How changes propagate between Box and MySQL
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 MySQL 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 MySQL as a row-level write, with types converted between the two schemas.
MySQL Box Sub-second propagation
DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.
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.
- MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Box ⇄ MySQL
Connect Box and MySQL for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–MySQL connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or MySQL 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 MySQL record.
Observability
Monitoring
Track your Box ⇄ MySQL 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 MySQL.
How the Box and MySQL 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.
MySQL
- Integration surface
- SQL wire protocol (MySQL client/server protocol)
- Authentication
- Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
How it works
How to connect Box to MySQL — 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 MySQL 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
MySQL
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and MySQL 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 ⇄ MySQLCustomers 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 MySQLCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and MySQL integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and MySQL: authenticate both systems, choose the objects to sync (such as Box's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 MySQL: Records that point at documents; A landing zone for incoming files; Continuous archival to file storage. Where a record in MySQL references a file in Box, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.
-
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. MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host). Stacksync manages authentication, retries, and rate limits on both sides.
-
MySQL: INSERT ... ON DUPLICATE KEY UPDATE provides native upsert semantics for idempotent inbound writes. 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 MySQL 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 Box and MySQL records are not retained after a sync operation.
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 537 integrations available for Box and MySQL.
Popular · 7 of 537
-
Box ⇄ IBM Db2 -
Box ⇄ Firebase -
Box ⇄ SingleStore -
Box ⇄ Amazon Aurora -
MySQL ⇄ Amazon S3 -
MySQL ⇄ Sharepoint -
MySQL ⇄ Egnyte
No integrations match .
