Two-way sync
Changes in Epicor ERP or Success Factors instantly reflect in both systems. No stale data, no manual imports.
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.
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.
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.
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.
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.
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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Epicor ERP–Success Factors connection.
Changes in Epicor ERP or Success Factors instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Epicor ERP or Success Factors data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Epicor ERP or Success Factors record.
Track your Epicor ERP ⇄ Success Factors sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Epicor ERP and Success Factors.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Epicor ERP and Success Factors: authenticate both systems, choose the objects to sync (such as Epicor ERP's Customers and Suppliers), map fields visually, and changes propagate both ways in milliseconds — no code required.
Epicor ERP: 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. Success Factors: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Epicor ERP: The REST surface wraps Epicor business objects, so API writes pass through the same validation and business logic as the client UI. Success Factors: Two parallel data models exist — the User entity versus the Employee Central model (PerPerson / EmpEmployment / EmpJob) — each with its own lastModifiedDateTime, so a sync must query both to avoid missing changes. Stacksync's field mapping accounts for these differences between Epicor ERP and Success Factors without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Epicor ERP and Success Factors records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Epicor ERP and Success Factors connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Epicor ERP–Success Factors integration in-house.
Yes — Stacksync ships production-grade connectors for both Epicor ERP and Success Factors. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 510 integrations available for Epicor ERP and Success Factors.