Skip to content
Human resources ⇄ Database

BambooHR to MySQL integration — real-time, two-way sync

Keep BambooHR and MySQL 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 BambooHR and MySQL

Put your workforce data where your apps can reach it: MySQL and BambooHR share the same people, positions, and org structure in real time.

BambooHR is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. MySQL is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Compensation, Time Off, Employment Status, Departments and Divisions in BambooHR need to exist as queryable Views, Columns, Primary and Unique Keys, JSON Columns in MySQL 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 Views, Columns, Primary and Unique Keys, JSON Columns in MySQL with Compensation, Time Off, Employment Status, Departments and Divisions in BambooHR field by field, in real time. You decide which system owns which fields — BambooHR 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 Expose SaaS objects as MySQL tables so legacy internal tools built on MySQL can read live business data
  • 02 Replicate ERP master data (customers, items, pricing) into the MySQL databases behind storefronts and portals
  • 03 Sync Employees and Employment Status to identity and IT systems so new hires are provisioned and departures deactivated automatically.
  • 04 Read Job Information and Departments into an ERP or planning tool so headcount, cost centers, and org structure stay current.

Common sync patterns

Mirror people records into the database

Records maintained in BambooHR land as queryable Views, Columns, Primary and Unique Keys, JSON Columns in MySQL, 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.

Reporting and analytics on current data

Compensation, Time Off, Employment Status, Departments and Divisions replicate into MySQL where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

What you can sync between BambooHR and MySQL

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.

BambooHR objects MySQL objects How this pairing syncs
Employment Status Effective-dated hire, leave, and termination status; drives automated provisioning and deprovisioning in downstream identity and license systems. Stored Procedures Server-side logic that can post-process synced rows. Employment Status is specific to BambooHR and Stored Procedures to MySQL — each maps to any object or custom field on the other side.
Departments and Divisions Org-structure list values; synced to keep cost centers and team groupings consistent across ERP, identity, and analytics systems. Triggers An alternative change-capture mechanism when binlog access is unavailable. Departments and Divisions is specific to BambooHR and Triggers to MySQL — each maps to any object or custom field on the other side.
Custom Tables Company-specific effective-dated tables (assets, training, certifications); rows read and written so custom HR data isn't trapped in the HRIS. Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. Custom Tables is specific to BambooHR and Databases (Schemas) to MySQL — each maps to any object or custom field on the other side.
Reports Saved company reports retrievable via API; read out on a schedule to feed a warehouse without rebuilding field-by-field queries. Tables The primary sync target; rows map to records in connected systems. Reports is specific to BambooHR and Tables to MySQL — each maps to any object or custom field on the other side.
Employees The core person record with personal and work fields; read out to identity, payroll, and IT systems, and written back from recruiting or onboarding tools. Views Read-side projections used as outbound sync sources. Employees is specific to BambooHR and Views to MySQL — each maps to any object or custom field on the other side.
Job Information Effective-dated job title, department, division, location, and reporting line; synced so org charts and provisioning systems track internal moves. Columns Field-level mapping targets with engine-typed values. Job Information is specific to BambooHR and Columns to MySQL — each maps to any object or custom field on the other side.

How changes propagate between BambooHR and MySQL

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.

BambooHR MySQL Sub-second propagation

DetectionBambooHR notifies Stacksync of record changes through webhook events. The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling.

DeliveryEach detected change is applied to MySQL as a row-level write, with types converted between the two schemas.

MySQL BambooHR Sub-second propagation

DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.

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

Rate-limit considerations

  • BambooHR: Requests are rate-limited per API key with standard REST throttling (429 on excess); bulk reads are best done through saved Reports or the updated-IDs delta endpoint rather than per-employee calls.
  • MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with BambooHR ⇄ MySQL

Connect BambooHR and MySQL for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BambooHR–MySQL connection.

Real-time

Two-way sync

Changes in BambooHR or MySQL instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever BambooHR or MySQL 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 BambooHR or MySQL record.

Observability

Monitoring

Track your BambooHR ⇄ MySQL sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BambooHR and MySQL.

How the BambooHR and MySQL connectors work

BambooHR

Integration surface
BambooHR API (REST, per-company subdomain)
Authentication
API key per user over HTTP Basic auth (key as username), scoped to that user's permission level in BambooHR; OAuth/OpenID available for SSO-enabled apps
Change detection
The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling; webhooks can fire on monitored field changes
Capabilities
read · write · webhooks
Rate limits
Requests are rate-limited per API key with standard REST throttling (429 on excess); bulk reads are best done through saved Reports or the updated-IDs delta endpoint rather than per-employee calls.

MySQL

Integration surface
SQL wire protocol (MySQL client/server protocol)
Authentication
Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
Change detection
Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits and server resources
MySQL setup guide
How it works

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

    Choose tables

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

BambooHR and MySQL 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 454 integrations available for BambooHR and MySQL.

Popular · 8 of 454
All BambooHR integrations All MySQL 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