Skip to content
CRM ⇄ E-commerce

DealCloud to Shopware integration — real-time, two-way sync

Keep DealCloud and Shopware 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 DealCloud and Shopware

Keep the customers and orders that DealCloud and Shopware share aligned in real time, so sales works from live purchase history and the store works from current account details.

DealCloud holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Shopware runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.

Stacksync links Company, Contact, Fund, Investment in DealCloud to Media, Products, Categories, Customers in Shopware with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.

The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.

Common use cases

  • 01 Mirror DealCloud activities and tasks into an operational database to power internal dashboards without hitting the API on every read.
  • 02 Push portfolio and fund performance data from a warehouse into DealCloud so dealmakers see up-to-date metrics on each investment.
  • 03 Consolidate orders and customers from multiple `sales_channel` storefronts into one Postgres database for cross-channel analysis.
  • 04 Two-way sync of the `product` catalog — titles, nested price arrays, and stock — between Shopware and an ERP or PIM so pricing and inventory stay aligned.

Common sync patterns

New buyers become CRM records

A customer created in Shopware creates or updates the matching contact or account in DealCloud, so first-time and repeat buyers land in the relationship system without a manual import.

Contact and address details stay consistent

An email, phone, or shipping and billing address corrected in either system updates the other, so the next order and the next outreach both use current information.

Where DealCloud segments customers: status travels to the store record

Lifecycle stage, tier, or account owner set in DealCloud syncs onto the customer record in Shopware, so the buying side can act on how the relationship is classified.

What you can sync between DealCloud and Shopware

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.

DealCloud objects Shopware objects How this pairing syncs
Investment Synced with incremental and full sync. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Investment is specific to DealCloud and Customers to Shopware — each maps to any object or custom field on the other side.
Relationship Synced with incremental and full sync. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. Relationship is specific to DealCloud and Orders to Shopware — each maps to any object or custom field on the other side.
Activity Synced with incremental and full sync. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Activity is specific to DealCloud and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Task Synced with incremental and full sync. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Task is specific to DealCloud and Order Deliveries to Shopware — each maps to any object or custom field on the other side.
User Synced with incremental and full sync. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. User is specific to DealCloud and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Deal Synced with incremental and full sync. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Deal is specific to DealCloud and Sales Channels to Shopware — each maps to any object or custom field on the other side.

How changes propagate between DealCloud and Shopware

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.

DealCloud Shopware Interval-based propagation

DetectionStacksync polls DealCloud for changes on an incremental schedule, reading only records changed since the previous pass. Incremental via each entry's last-modified timestamp.

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

Shopware DealCloud Sub-second propagation

DetectionShopware notifies Stacksync of record changes through webhook events. App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field.

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

Rate-limit considerations

  • DealCloud: API request limits apply per firm tenant; Stacksync manages throttling and retries automatically.
  • Shopware: No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores.
What ships with DealCloud ⇄ Shopware

Connect DealCloud and Shopware for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DealCloud–Shopware connection.

Real-time

Two-way sync

Changes in DealCloud or Shopware instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever DealCloud or Shopware 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 DealCloud or Shopware record.

Observability

Monitoring

Track your DealCloud ⇄ Shopware sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between DealCloud and Shopware.

How the DealCloud and Shopware connectors work

DealCloud

Integration surface
REST API (DealCloud Data API v2)
Authentication
OAuth 2.0 client-credentials; a DealCloud administrator generates a client ID and secret in the DealCloud admin API settings and grants Stacksync the required scopes
Change detection
Incremental via each entry's last-modified timestamp; DealCloud has no universal native change-data-capture, so Stacksync polls modified rows on an interval
Capabilities
read · write
Rate limits
API request limits apply per firm tenant; Stacksync manages throttling and retries automatically.

Shopware

Integration surface
Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
Authentication
OAuth 2.0 — client-credentials grant using an Integration's Access Key ID + Secret Access Key, or resource-owner password grant for a user; access tokens expire after 10 minutes
Change detection
App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields
Capabilities
read · write · webhooks
Rate limits
No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores
How it works

How to connect DealCloud to Shopware — 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 DealCloud and Shopware 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
    DealCloud connected
    Shopware connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DealCloud and Shopware 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 · DealCloud ⇄ Shopware
    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
    DealCloud Shopware
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

DealCloud and Shopware 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 380 integrations available for DealCloud and Shopware.

Popular · 6 of 380
All DealCloud integrations All Shopware 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