Real-time
Two-way sync
Changes in Box or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Salesforce integration — real-time, two-way sync
Keep Box and Salesforce 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 Salesforce
Keep the paperwork with the relationship: Salesforce and Box share every customer's records and files in real time, in both directions.
Salesforce holds the customer relationship as structured records; Box holds the files that belong to those relationships, from contracts and proposals to signed agreements and statements of work. The two are linked in practice and disconnected in software: someone downloads a document, renames it, and uploads it to the right folder, or exports records out to storage for retention. Done by hand, files drift away from the records they belong to and copies fall out of date.
Stacksync keeps Campaigns, Tasks and Events, Products and Price Books, Custom Objects in Salesforce aligned with Users, Groups, Tasks, Events in Box, in real time. A new account or deal can open its own folder in Box; a document filed in Box can surface as a link and metadata on the matching record in Salesforce; and records from Salesforce can be written into Box as files or objects for backup, archival, and compliance. You choose which side owns what, and Stacksync keeps the two consistent as either one changes.
Common use cases
- 01 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
- 02 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
- 03 Mirror Metadata template instances on Files into database columns so contracts and assets are searchable and reportable alongside other business data.
- 04 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
Common sync patterns
One place for a customer's files
Attachments that accumulate against a record in Salesforce collect in that customer's folder in Box, so the full document history lives in one place and is reachable by anyone who needs it.
A folder per account or deal
When an account or deal is created in Salesforce, a matching folder or container opens in Box, named and organized the same way, so files have a home the moment they are needed.
Documents linked back to the record
A contract, proposal, or signed agreement filed in Box surfaces as a link on the matching record in Salesforce, so the customer's paperwork sits with the relationship instead of a shared drive.
What you can sync between Box and Salesforce
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | Groups is specific to Box and Products and Price Books to Salesforce — 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. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | Tasks is specific to Box and Custom Objects to Salesforce — 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. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Events is specific to Box and Accounts to Salesforce — 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. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Files is specific to Box and Contacts to Salesforce — 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. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Folders is specific to Box and Leads to Salesforce — each maps to any object or custom field on the other side. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Metadata is specific to Box and Opportunities to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between Box and Salesforce
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 Salesforce 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 written to Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce Box Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with Box ⇄ Salesforce
Connect Box and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Salesforce 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 Salesforce record.
Observability
Monitoring
Track your Box ⇄ Salesforce 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 Salesforce.
How the Box and Salesforce 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.
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Box to Salesforce — 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 Salesforce 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
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Salesforce 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 ⇄ SalesforceCustomers 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 SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Salesforce: authenticate both systems, choose the objects to sync (such as Box's Groups and Tasks), 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 Salesforce records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Salesforce integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and Salesforce. 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 Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Salesforce side: Campaigns, Tasks and Events, Products and Price Books, Custom Objects, plus custom fields where Salesforce exposes them. On the Box side: Users, Groups, Tasks, Events. 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 528 integrations available for Box and Salesforce.
Popular · 7 of 528
-
Box ⇄ Vtiger CRM -
Box ⇄ Zoho SalesIQ -
Box ⇄ ZoomInfo -
Box ⇄ Vitally -
Salesforce ⇄ Amazon S3 -
Salesforce ⇄ Sharepoint -
Salesforce ⇄ Egnyte
No integrations match .
