Skip to content
ERP ⇄ Human resources

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

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

Sync the workers, org structure, and cost centers that Epicor ERP and Success Factors share in real time, so the people Success Factors manages stay current in the system that runs finance and operations.

Success Factors is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Epicor ERP runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Customers, Suppliers, Parts, Sales orders in Epicor ERP with User, PerPerson, EmpEmployment, EmpJob in Success Factors field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Epicor ERP keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Sync Epicor customers and AR invoices into a CRM so sales sees order history and credit status without ERP logins.
  • 02 Push won opportunities from the CRM into Epicor as sales orders and sync order status back.
  • 03 Two-way sync of User and EmpJob (position, department, manager, cost center) into Postgres so provisioning, internal apps, and analytics read current org data in SQL while HR edits in SuccessFactors.
  • 04 Push new hires (PerPerson, EmpEmployment, EmpJob) into an ERP or payroll system so account, cost-center, and payroll setup fire on hire instead of manual Integration Center exports.

Common sync patterns

Where Success Factors is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Success Factors, the matching employee record in Epicor ERP is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

New hires ready to transact in Epicor ERP

A new person set up in Success Factors becomes an employee record in Epicor ERP in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.

One org structure

Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Epicor ERP roll up to the same structure Success Factors maintains.

What you can sync between Epicor ERP and Success Factors

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 Success Factors objects How this pairing syncs
Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. PerPerson Person-level container in Employee Central holding biographical data; effective-dated child entities (PerPersonal, PerEmail, PerPhone) hang off it. Customers is specific to Epicor ERP and PerPerson to Success Factors — each maps to any object or custom field on the other side.
Suppliers Vendor masters kept aligned with procurement and AP automation tools. EmpEmployment Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling. Suppliers is specific to Epicor ERP and EmpEmployment to Success Factors — each maps to any object or custom field on the other side.
Parts Item masters that anchor inventory, BOM, and order line syncs. EmpJob Effective-dated job info: position, department, manager, FTE, pay grade, cost center; the most-synced record for downstream HR and provisioning. Parts is specific to Epicor ERP and EmpJob to Success Factors — 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. EmpCompensation Effective-dated pay and compensation; usually read into a warehouse for reporting, writable for comp updates as new dated slices. Sales orders is specific to Epicor ERP and EmpCompensation to Success Factors — each maps to any object or custom field on the other side.
Purchase orders Synced with procurement systems and matched against receipts. Foundation Objects (FODepartment, FOLocation, FOCostCenter) Org-structure master data (department, location, cost center, division); mastered elsewhere and written in, or read out to build org charts. Purchase orders is specific to Epicor ERP and Foundation Objects (FODepartment, FOLocation, FOCostCenter) to Success Factors — each maps to any object or custom field on the other side.
Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. Position Position Management records for headcount and requisition planning; synced with an ATS or ERP to keep positions and reqs aligned. Jobs is specific to Epicor ERP and Position to Success Factors — each maps to any object or custom field on the other side.

How changes propagate between Epicor ERP and Success Factors

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

Success Factors Epicor ERP Sub-second propagation

DetectionSuccess Factors notifies Stacksync of record changes through webhook events. Polling on each entity's lastModifiedDateTime / lastModifiedOn (effective-dated entities require date-range handling).

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.
  • Success Factors: OData calls are throttled at the tenant level (Access Limits for OData V2); large reads must be paginated (default page size 1000) via $top/$skip or paging cursors.
What ships with Epicor ERP ⇄ Success Factors

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Epicor ERP ⇄ Success Factors 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 Success Factors.

How the Epicor ERP and Success Factors 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

Success Factors

Integration surface
OData V2 and V4 REST APIs (plus legacy SFAPI / Compound Employee SOAP API)
Authentication
OAuth 2.0 SAML Bearer Assertion — register an OAuth client for an API key (used as client_id), then exchange a signed SAML assertion for a short-lived access token; legacy HTTP Basic auth is being retired
Change detection
Polling on each entity's lastModifiedDateTime / lastModifiedOn (effective-dated entities require date-range handling); Intelligent Services can also push a fixed set of standard business events (e.g. Employee Hire) to a REST endpoint
Capabilities
read · write · webhooks
Rate limits
OData calls are throttled at the tenant level (Access Limits for OData V2); large reads must be paginated (default page size 1000) via $top/$skip or paging cursors.
How it works

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

    Choose tables

    Pick the Epicor ERP and Success Factors 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 ⇄ Success Factors
    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 Success Factors
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Epicor ERP and Success Factors 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:

Coworkers laughing in front of a laptop in a casual office setting

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