Skip to content
Marketing ⇄ ERP

Marketo to SAP Business ByDesign integration — real-time, two-way sync

Keep Marketo 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 Marketo and SAP Business ByDesign

Feed the real customer, order, and revenue records from SAP Business ByDesign into Marketo 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: Projects, Employees, Business Partners (Accounts), Contacts 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 Projects, Employees, Business Partners (Accounts), Contacts in SAP Business ByDesign with Leads, Companies, Opportunities and Opportunity Roles, Custom Objects in Marketo 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 Marketo 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 Marketo 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 Create sales orders in ByDesign from e-commerce or CPQ systems and sync order and delivery status back.
  • 02 Replicate customer invoices into a reporting database or collections tool without manual exports.
  • 03 Add or remove Leads on Static Lists or set Program Member status from lifecycle stage computed downstream, then run a trigger Smart Campaign against them.
  • 04 Sync Opportunities and Opportunity Roles into Marketo so revenue and pipeline data can drive account-aware nurture and 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 Marketo, 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, Marketo 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 Marketo 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.

Marketo objects SAP Business ByDesign objects How this pairing syncs
Leads Core person records (called Leads/People), deduped on email address by default or a configured dedupe field; read via GET /rest/v1/leads.json with a filterType, upserted via POST /rest/v1/leads.json (action createOrUpdate/createOnly/updateOnly), bulk-imported via CSV through POST /bulk/v1/leads.json, and bulk-exported via /bulk/v1/leads/export/create.json. Customer Invoices Billing documents synced outward for collections and CRM visibility. Leads is specific to Marketo and Customer Invoices to SAP Business ByDesign — each maps to any object or custom field on the other side.
Companies Company records linked to Leads via a company link field; read and upserted through /rest/v1/companies.json, typically mastered in a CRM or ERP and written into Marketo for account context. Materials / Products Item master data aligned with e-commerce and inventory systems. Companies is specific to Marketo and Materials / Products to SAP Business ByDesign — each maps to any object or custom field on the other side.
Opportunities and Opportunity Roles Revenue objects synced via /rest/v1/opportunities.json and /rest/v1/opportunities/roles.json; roles associate an opportunity with a Lead, so pipeline data can drive nurture and scoring. Purchase Orders Procurement documents exchanged with supplier systems. Opportunities and Opportunity Roles is specific to Marketo and Purchase Orders to SAP Business ByDesign — each maps to any object or custom field on the other side.
Custom Objects Auxiliary data tables described via /rest/v1/customobjects.json and read/written via /rest/v1/customobjects/{apiName}.json, linked to Leads by a dedupe/link field so campaigns branch on records like purchases or subscriptions. Opportunities Built-in CRM records synced with external sales tools when both are in use. Custom Objects is specific to Marketo and Opportunities to SAP Business ByDesign — each maps to any object or custom field on the other side.
Activities and Lead Changes Engagement feed (opens, clicks, form fills, Data Value Changes) read via GET /rest/v1/activities.json using a paging token from /rest/v1/activities/pagingtoken.json (sinceDatetime), plus Get Lead Changes and Get Deleted Leads; read-only, also available via async Bulk Activity Extract. Projects Project structures and tasks read for time and billing integrations. Activities and Lead Changes is specific to Marketo and Projects to SAP Business ByDesign — each maps to any object or custom field on the other side.
Static Lists Named static lists; read via /rest/v1/lists.json, with Leads added or removed via POST and DELETE on /rest/v1/lists/{listId}/leads.json to control campaign membership from lifecycle logic computed downstream. Employees Worker records referenced by time, expense, and project data. Static Lists is specific to Marketo and Employees to SAP Business ByDesign — each maps to any object or custom field on the other side.

How changes propagate between Marketo 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.

Marketo SAP Business ByDesign Interval-based propagation

DetectionStacksync polls Marketo for changes on an incremental schedule, reading only records changed since the previous pass. Polling: Get Lead Changes and Get Lead Activities from a paging token seeded by a sinceDatetime, plus Get Deleted Leads, or Bulk Extract filtered on.

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

SAP Business ByDesign Marketo 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 Marketo through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Marketo: Interactive calls are capped at 100 per 20 seconds (error 606) and a maximum of 10 concurrent calls (error 615) per instance, neither increasable; a default daily quota of 50,000 calls (increasable, resets midnight CST) applies. Bulk Extract shares a 500 MB/day export quota across data types with at most 2 concurrent jobs and 10 queued.
What ships with Marketo ⇄ SAP Business ByDesign

Connect Marketo and SAP Business ByDesign for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Marketo 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 Marketo 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 Marketo or SAP Business ByDesign record.

Observability

Monitoring

Track your Marketo ⇄ 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 Marketo and SAP Business ByDesign.

How the Marketo and SAP Business ByDesign connectors work

Marketo

Integration surface
Marketo REST API (JSON over HTTPS) for Leads, Companies, Opportunities, Custom Objects, Activities, Lists, Programs, and Campaigns, plus an asynchronous Bulk Import (leads) and Bulk Extract (leads/activities/program members/custom objects) API and an Asset REST API for emails, forms, and landing pages
Authentication
OAuth 2.0 client_credentials (2-legged): GET the Identity URL /oauth/token?grant_type=client_credentials with a Custom Service client_id and client_secret to receive an access token valid for 3600 seconds, then send it as Authorization: Bearer on each call. The instance base URL is https://{munchkinId}.mktorest.com; passing the token as an access_token query parameter is deprecated (removal July 31, 2026).
Change detection
Polling: Get Lead Changes and Get Lead Activities from a paging token seeded by a sinceDatetime, plus Get Deleted Leads, or Bulk Extract filtered on createdAt/updatedAt. Marketo's Webhooks are Smart Campaign flow-step outbound HTTP calls to a URL, not a general record-change subscription, so there is no push feed of arbitrary CRUD.
Capabilities
read · write
Rate limits
Interactive calls are capped at 100 per 20 seconds (error 606) and a maximum of 10 concurrent calls (error 615) per instance, neither increasable; a default daily quota of 50,000 calls (increasable, resets midnight CST) applies. Bulk Extract shares a 500 MB/day export quota across data types with at most 2 concurrent jobs and 10 queued.

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 Marketo 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 Marketo 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
    Marketo connected
    SAP Business ByDesign connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Marketo 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 · Marketo ⇄ 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
    Marketo SAP Business ByDesign
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Marketo 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 476 integrations available for Marketo and SAP Business ByDesign.

Popular · 7 of 476
All Marketo integrations All SAP Business ByDesign integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own