Skip to content
ERP ⇄ Marketing

Epicor ERP to Rollworks integration — real-time, two-way sync

Keep Epicor ERP and Rollworks 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 Epicor ERP and Rollworks

Feed the real customer, order, and revenue records from Epicor ERP into Rollworks 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. Epicor ERP holds exactly that: Bills of materials, Customers, Suppliers, Parts 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 Bills of materials, Customers, Suppliers, Parts in Epicor ERP with Reporting and Attribution, Target Account Lists, Account Tiers, Accounts (TAL Items) in Rollworks 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 Rollworks 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 Rollworks flow back onto the record in Epicor ERP.

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 Sync shipment confirmations out to commerce platforms and customer portals as jobs complete.
  • 02 Sync Epicor customers and AR invoices into a CRM so sales sees order history and credit status without ERP logins.
  • 03 Consolidate account-level ad engagement by domain into a reporting database to join RollWorks spend against CRM Opportunities.
  • 04 Push a Target Account List from a CRM or warehouse into RollWorks, keeping Accounts (domains) and their Account Tiers aligned as the source data changes.

Common sync patterns

Suppress or target existing customers

Because Epicor ERP knows who is already a paying customer, Rollworks 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.

Lifecycle triggers from back-office events

A first order, a renewal, or a lapsed account recorded in Epicor ERP appears in Rollworks within seconds, ready to start or stop a lifecycle campaign.

What you can sync between Epicor ERP and Rollworks

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.

Epicor ERP objects Rollworks objects How this pairing syncs
Shipments Fulfillment confirmations synced to customer portals and commerce systems. Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. Shipments is specific to Epicor ERP and Campaigns to Rollworks — each maps to any object or custom field on the other side.
Bills of materials Methods of manufacturing read for costing and planning integrations. Ad Groups and Ads Campaign subdivisions carrying attribute, contextual, geo, and device targeting plus creative; read and written to keep targeting aligned with an internal planning system. Bills of materials is specific to Epicor ERP and Ad Groups and Ads to Rollworks — each maps to any object or custom field on the other side.
Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. Reporting and Attribution Delivery and attribution metrics (impressions, clicks, cost, conversions, view-throughs) from the GraphQL Reporting API; read-only, aggregated by campaign, ad, and account domain. Customers is specific to Epicor ERP and Reporting and Attribution to Rollworks — each maps to any object or custom field on the other side.
Suppliers Vendor masters kept aligned with procurement and AP automation tools. Target Account Lists Named lists of B2B accounts for ABM; managed through /audience/v1/target_accounts so a CRM or warehouse can push and reconcile the accounts RollWorks advertises against. Suppliers is specific to Epicor ERP and Target Account Lists to Rollworks — each maps to any object or custom field on the other side.
Parts Item masters that anchor inventory, BOM, and order line syncs. Account Tiers Groups within a Target Account List; an account belongs to only one tier per list, so tier assignments are written from source-of-truth data to drive tiered targeting. Parts is specific to Epicor ERP and Account Tiers to Rollworks — each maps to any object or custom field on the other side.
Sales orders Created from won CRM opportunities; status and line changes sync back out. Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. Sales orders is specific to Epicor ERP and Accounts (TAL Items) to Rollworks — each maps to any object or custom field on the other side.

How changes propagate between Epicor ERP and Rollworks

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.

Epicor ERP Rollworks Interval-based propagation

DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.

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

Rollworks Epicor ERP Interval-based propagation

DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.

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

Rate-limit considerations

  • Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
  • Rollworks: NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
What ships with Epicor ERP ⇄ Rollworks

Connect Epicor ERP and Rollworks for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Epicor ERP–Rollworks connection.

Real-time

Two-way sync

Changes in Epicor ERP or Rollworks instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Epicor ERP or Rollworks 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 Epicor ERP or Rollworks record.

Observability

Monitoring

Track your Epicor ERP ⇄ Rollworks sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Epicor ERP and Rollworks.

How the Epicor ERP and Rollworks connectors work

Epicor ERP

Integration surface
REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
Authentication
API key combined with basic or token authentication, depending on version and deployment
Change detection
Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments

Rollworks

Integration surface
REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
Authentication
OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts
Change detection
Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published
Capabilities
read · write
Rate limits
NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
How it works

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

    Choose tables

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

Epicor ERP and Rollworks 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 374 integrations available for Epicor ERP and Rollworks.

Popular · 8 of 374
All Epicor ERP integrations All Rollworks 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