Skip to content
ERP ⇄ Human resources

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

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

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

Hibob 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 Parts, Sales orders, Purchase orders, Jobs in Epicor ERP with Employment, Work, Salaries, Time off in Hibob 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 Push won opportunities from the CRM into Epicor as sales orders and sync order status back.
  • 02 Mirror parts, on-hand inventory, and job status into a reporting database for shop-floor dashboards.
  • 03 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.
  • 04 Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.

Common sync patterns

Where Hibob is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Hibob, 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 Hibob 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 Hibob maintains.

What you can sync between Epicor ERP and Hibob

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 Hibob objects How this pairing syncs
Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Customers is specific to Epicor ERP and Named lists to Hibob — each maps to any object or custom field on the other side.
Suppliers Vendor masters kept aligned with procurement and AP automation tools. People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. Suppliers is specific to Epicor ERP and People (Employees) to Hibob — each maps to any object or custom field on the other side.
Parts Item masters that anchor inventory, BOM, and order line syncs. Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Parts is specific to Epicor ERP and Employment to Hibob — 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. Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Sales orders is specific to Epicor ERP and Work to Hibob — each maps to any object or custom field on the other side.
Purchase orders Synced with procurement systems and matched against receipts. Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Purchase orders is specific to Epicor ERP and Salaries to Hibob — 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. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Jobs is specific to Epicor ERP and Time off to Hibob — each maps to any object or custom field on the other side.

How changes propagate between Epicor ERP and Hibob

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

Hibob Epicor ERP Sub-second propagation

DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.

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.
  • Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
What ships with Epicor ERP ⇄ Hibob

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Hibob

Integration surface
REST API (the Bob API)
Authentication
Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
Change detection
Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
Hibob setup guide
How it works

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

    Choose tables

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

Epicor ERP and Hibob 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 510 integrations available for Epicor ERP and Hibob.

Popular · 7 of 510
All Epicor ERP integrations All Hibob 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