Skip to content
Human resources ⇄ Database

Hibob to SAP ASE (Sybase) integration — real-time, two-way sync

Keep Hibob and SAP ASE (Sybase) 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 Hibob and SAP ASE (Sybase)

Put your workforce data where your apps can reach it: SAP ASE (Sybase) and Hibob share the same people, positions, and org structure in real time.

Hibob is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. SAP ASE (Sybase) is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Documents, Named lists, People (Employees), Employment in Hibob need to exist as queryable Tables, Views, Stored Procedures, Databases and Schemas in SAP ASE (Sybase) before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Tables, Views, Stored Procedures, Databases and Schemas in SAP ASE (Sybase) with Documents, Named lists, People (Employees), Employment in Hibob field by field, in real time. You decide which system owns which fields — Hibob typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Migrate off ASE incrementally by keeping old and new databases in sync during cutover.
  • 02 Expose customer and transaction data locked in ASE to CRM and reporting systems.
  • 03 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.
  • 04 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.

Common sync patterns

Computed and operational fields flow back

Values assembled or corrected in SAP ASE (Sybase) write onto the matching record in Hibob where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Hibob land as queryable Tables, Views, Stored Procedures, Databases and Schemas in SAP ASE (Sybase), so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

What you can sync between Hibob and SAP ASE (Sybase)

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.

Hibob objects SAP ASE (Sybase) objects How this pairing syncs
Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Indexes Access paths that keep keyed polling queries efficient on large OLTP tables. Salaries is specific to Hibob and Indexes to SAP ASE (Sybase) — each maps to any object or custom field on the other side.
Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Tables The core sync unit; rows are read and written with standard SQL. Time off is specific to Hibob and Tables to SAP ASE (Sybase) — each maps to any object or custom field on the other side.
Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Views Read-only projections used to shape data for extraction without touching base tables. Lifecycle is specific to Hibob and Views to SAP ASE (Sybase) — each maps to any object or custom field on the other side.
Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Stored Procedures T-SQL routines that encapsulate business logic; often invoked instead of direct table writes. Documents is specific to Hibob and Stored Procedures to SAP ASE (Sybase) — each maps to any object or custom field on the other side.
Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Databases and Schemas Namespaces that scope sync configuration and permissions. Named lists is specific to Hibob and Databases and Schemas to SAP ASE (Sybase) — each maps to any object or custom field on the other side.
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. Triggers Server-side hooks sometimes used to populate change-capture tables for syncs. People (Employees) is specific to Hibob and Triggers to SAP ASE (Sybase) — each maps to any object or custom field on the other side.

How changes propagate between Hibob and SAP ASE (Sybase)

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.

Hibob SAP ASE (Sybase) 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 applied to SAP ASE (Sybase) as a row-level write, with types converted between the two schemas.

SAP ASE (Sybase) Hibob Interval-based propagation

DetectionStacksync polls SAP ASE (Sybase) for changes on an incremental schedule, reading only records changed since the previous pass. Timestamp or key-based polling and trigger-based capture.

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

Rate-limit considerations

  • 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 Hibob ⇄ SAP ASE (Sybase)

Connect Hibob and SAP ASE (Sybase) for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–SAP ASE (Sybase) connection.

Real-time

Two-way sync

Changes in Hibob or SAP ASE (Sybase) instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Hibob or SAP ASE (Sybase) 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 Hibob or SAP ASE (Sybase) record.

Observability

Monitoring

Track your Hibob ⇄ SAP ASE (Sybase) sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Hibob and SAP ASE (Sybase).

How the Hibob and SAP ASE (Sybase) connectors work

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

SAP ASE (Sybase)

Integration surface
SQL over the TDS wire protocol; JDBC (jConnect) and ODBC drivers
Authentication
Database credentials (username/password), optionally backed by LDAP or Kerberos
Change detection
Timestamp or key-based polling and trigger-based capture; log-based replication requires SAP Replication Server components
Capabilities
read · write
How it works

How to connect Hibob to SAP ASE (Sybase) — 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 Hibob and SAP ASE (Sybase) 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
    Hibob connected
    SAP ASE (Sybase) connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Hibob and SAP ASE (Sybase) 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 · Hibob ⇄ SAP ASE (Sybase)
    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
    Hibob SAP ASE (Sybase)
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Hibob and SAP ASE (Sybase) 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 466 integrations available for Hibob and SAP ASE (Sybase).

Popular · 7 of 466
All Hibob integrations All SAP ASE (Sybase) 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