Skip to content
Marketing ⇄ ERP

Salesforce Marketing Cloud to SAP Business ByDesign integration — real-time, two-way sync

Keep Salesforce Marketing Cloud 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.

  • 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 Salesforce Marketing Cloud and SAP Business ByDesign

Feed the real customer, order, and revenue records from SAP Business ByDesign into Salesforce Marketing Cloud so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.

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. SAP Business ByDesign holds exactly that: Sales Orders, Customer Invoices, Materials / Products, Purchase Orders 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 Sales Orders, Customer Invoices, Materials / Products, Purchase Orders in SAP Business ByDesign with Tracking Events, Transactional Sends, Data Extensions, Contacts / Subscribers in Salesforce Marketing Cloud 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 Salesforce Marketing Cloud 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 Salesforce Marketing Cloud flow back onto the record in SAP Business ByDesign.

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.

Common use cases

  • 01 Replicate customer invoices into a reporting database or collections tool without manual exports.
  • 02 Align the ByDesign material master with external product catalogs and inventory systems.
  • 03 Fire Journey Builder entry events (/interaction/v1/events) from an app or database when a contact acts, so behavioral journeys trigger on live events instead of scheduled batch loads.
  • 04 Land tracking events - Sent, Open, Click, Bounce, Unsubscribe - from the SOAP tracking objects or Automation Studio Data Views into a warehouse table for per-send deliverability reporting.

Common sync patterns

Purchase history drives segmentation

Orders, invoices, and revenue totals from SAP Business ByDesign land on the matching contact or account in Salesforce Marketing Cloud, so audiences are built from what customers actually bought and spent rather than from guesses.

Suppress or target existing customers

Because SAP Business ByDesign knows who is already a paying customer, Salesforce Marketing Cloud can exclude them from acquisition campaigns or single them out for renewal and cross-sell.

One customer identity across both systems

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.

What you can sync between Salesforce Marketing Cloud and SAP Business ByDesign

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.

Salesforce Marketing Cloud objects SAP Business ByDesign objects How this pairing syncs
Contacts / Subscribers The contact model keyed by Subscriber Key, holding channel addresses and subscription status; managed through the Contacts API (/contacts/v1/contacts) and the SOAP Subscriber object, and referenced by every send and journey. Materials / Products Item master data aligned with e-commerce and inventory systems. Contacts / Subscribers is specific to Salesforce Marketing Cloud and Materials / Products to SAP Business ByDesign — each maps to any object or custom field on the other side.
Journeys (Journey Builder) Multi-step automated flows read and managed via /interaction/v1/interactions; contacts are injected by firing an entry event to /interaction/v1/events with an EventDefinitionKey and contact data. Purchase Orders Procurement documents exchanged with supplier systems. Journeys (Journey Builder) is specific to Salesforce Marketing Cloud and Purchase Orders to SAP Business ByDesign — each maps to any object or custom field on the other side.
Content Assets (Content Builder) Emails, templates, images, and reusable content blocks stored in Content Builder and read or written via /asset/v1/content/assets, used to compose the messages a journey or send delivers. Opportunities Built-in CRM records synced with external sales tools when both are in use. Content Assets (Content Builder) is specific to Salesforce Marketing Cloud and Opportunities to SAP Business ByDesign — each maps to any object or custom field on the other side.
Automations (Automation Studio) Scheduled or triggered workflows of import, query, extract, and send activities managed via /automation/v1/automations; SQL Query Activities read Data Views and write results into Data Extensions. Projects Project structures and tasks read for time and billing integrations. Automations (Automation Studio) is specific to Salesforce Marketing Cloud and Projects to SAP Business ByDesign — each maps to any object or custom field on the other side.
Tracking Events Sent, Open, Click, Bounce, Unsubscribe, and NotSent events retrieved through the SOAP tracking objects (SentEvent, OpenEvent, ClickEvent, BounceEvent) or the Automation Studio Data Views (_Sent, _Open, _Click, _Bounce) - the queryable record of engagement per send. Employees Worker records referenced by time, expense, and project data. Tracking Events is specific to Salesforce Marketing Cloud and Employees to SAP Business ByDesign — each maps to any object or custom field on the other side.
Transactional Sends Triggered and transactional Email/SMS delivered through the Messaging API (/messaging/v1/email/messages/{key}); the Event Notification Service reports each message's disposition (delivered, bounced, opened, clicked). Business Partners (Accounts) Customer and supplier master data synced with CRMs and procurement tools. Transactional Sends is specific to Salesforce Marketing Cloud and Business Partners (Accounts) to SAP Business ByDesign — each maps to any object or custom field on the other side.

How changes propagate between Salesforce Marketing Cloud and SAP Business ByDesign

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.

Salesforce Marketing Cloud SAP Business ByDesign Sub-second propagation

DetectionSalesforce Marketing Cloud notifies Stacksync of record changes through webhook events. The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback.

DeliveryEach detected change is written to SAP Business ByDesign through its API, with automatic retries and rate-limit backoff.

SAP Business ByDesign Salesforce Marketing Cloud Interval-based propagation

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 Salesforce Marketing Cloud through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Salesforce Marketing Cloud: Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
What ships with Salesforce Marketing Cloud ⇄ SAP Business ByDesign

Connect Salesforce Marketing Cloud and SAP Business ByDesign for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce Marketing Cloud–SAP Business ByDesign connection.

Real-time

Two-way sync

Changes in Salesforce Marketing Cloud or SAP Business ByDesign instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Salesforce Marketing Cloud or SAP Business ByDesign 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 Salesforce Marketing Cloud or SAP Business ByDesign record.

Observability

Monitoring

Track your Salesforce Marketing Cloud ⇄ SAP Business ByDesign sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Salesforce Marketing Cloud and SAP Business ByDesign.

How the Salesforce Marketing Cloud and SAP Business ByDesign connectors work

Salesforce Marketing Cloud

Integration surface
Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
Authentication
OAuth 2.0 via an Installed Package (Client ID + Client Secret). Server-to-server uses the client_credentials grant and web apps use authorization_code, both against {subdomain}.auth.marketingcloudapis.com/v2/token. The 20-minute access token response also returns the account's rest_instance_url and soap_instance_url.
Change detection
The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback URL and subscription are registered and verified. There is no general data-change feed, so Data Extension and Data View syncs poll by date fields.
Capabilities
read · write · webhooks
Rate limits
Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.

SAP Business ByDesign

Integration surface
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
Change detection
Polling on last-changed timestamps; the platform does not offer a general webhook surface
Capabilities
read · write
How it works

How to connect Salesforce Marketing Cloud to SAP Business ByDesign — 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.

  1. 01

    Connect your apps

    Authenticate Salesforce Marketing Cloud 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Salesforce Marketing Cloud connected
    SAP Business ByDesign connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Salesforce Marketing Cloud 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Salesforce Marketing Cloud ⇄ SAP Business ByDesign
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Salesforce Marketing Cloud SAP Business ByDesign
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Salesforce Marketing Cloud and SAP Business ByDesign integration FAQ

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 476 integrations available for Salesforce Marketing Cloud and SAP Business ByDesign.

Popular · 7 of 476
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.