Skip to content
Database ⇄ Human resources

IBM AS/400 to Ukg Ready integration — real-time, two-way sync

Keep IBM AS/400 and Ukg Ready 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 IBM AS/400 and Ukg Ready

Put your workforce data where your apps can reach it: IBM AS/400 and Ukg Ready share the same people, positions, and org structure in real time.

Ukg Ready is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. IBM AS/400 is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Payroll (Earnings / Deductions / Employee Payroll Runs), Benefits, Cost Centers / Groups, Reports (Report-as-a-Service) in Ukg Ready need to exist as queryable Data queues, Libraries, Physical files (tables), Logical files (views) in IBM AS/400 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 Data queues, Libraries, Physical files (tables), Logical files (views) in IBM AS/400 with Payroll (Earnings / Deductions / Employee Payroll Runs), Benefits, Cost Centers / Groups, Reports (Report-as-a-Service) in Ukg Ready field by field, in real time. You decide which system owns which fields — Ukg Ready 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 AS/400 order, inventory, and item master data to modern SaaS tools without rewriting green-screen applications.
  • 02 Use journal-based change capture to replicate IBM i data into a cloud warehouse for reporting.
  • 03 Import computed Earnings and deductions into UKG Ready payroll runs from a warehouse or external time-tracking system ahead of each pay period.
  • 04 Create new-hire Employee records in UKG Ready from an ATS or onboarding workflow, including position, cost center, and compensation fields.

Common sync patterns

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

Payroll (Earnings / Deductions / Employee Payroll Runs), Benefits, Cost Centers / Groups, Reports (Report-as-a-Service) replicate into IBM AS/400 where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Ukg Ready stay consistent in IBM AS/400, so hierarchy-driven logic and permissions don't drift.

What you can sync between IBM AS/400 and Ukg Ready

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.

IBM AS/400 objects Ukg Ready objects How this pairing syncs
Members Sub-partitions of files in legacy applications, flattened or selected during syncs. Employees Core person records (demographics, contact info, status, work location); synced two-way and mapped to HRIS or person tables in a database. Members is specific to IBM AS/400 and Employees to Ukg Ready — each maps to any object or custom field on the other side.
Rows / records The unit of read and write, accessed via SQL or record-level access. Employment / Positions Job title, department, employment type, hire and termination dates; read for org modeling and written when roles change. Rows / records is specific to IBM AS/400 and Employment / Positions to Ukg Ready — each maps to any object or custom field on the other side.
Journals and journal receivers The change log that enables log-based CDC on journaled files. Compensation Salary or hourly rate, pay frequency, and FLSA status; often mastered elsewhere and written onto the employee record, or read into finance. Journals and journal receivers is specific to IBM AS/400 and Compensation to Ukg Ready — each maps to any object or custom field on the other side.
Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. Timesheet Entries Time-and-attendance punches, hours worked, and breaks; written from external time systems and read into warehouses for labor-cost reporting. Data queues is specific to IBM AS/400 and Timesheet Entries to Ukg Ready — each maps to any object or custom field on the other side.
Libraries The schema-equivalent containers that scope which files a sync reads. Accruals / Time Off PTO balances, requests, and approver status; read for liability reporting and requests can be created against employee records. Libraries is specific to IBM AS/400 and Accruals / Time Off to Ukg Ready — each maps to any object or custom field on the other side.
Physical files (tables) The Db2 for i tables mapped directly to sync targets. Payroll (Earnings / Deductions / Employee Payroll Runs) Earnings and deductions can be imported into pay runs; Employee Payroll Runs (gross, net, taxes) read back for GL posting and analytics. Physical files (tables) is specific to IBM AS/400 and Payroll (Earnings / Deductions / Employee Payroll Runs) to Ukg Ready — each maps to any object or custom field on the other side.

How changes propagate between IBM AS/400 and Ukg Ready

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.

IBM AS/400 Ukg Ready Sub-second propagation

DetectionChanges in IBM AS/400 are captured at the source via change data capture — no polling loop against its API. Journal-based CDC by reading journal receivers on journaled files.

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

Ukg Ready IBM AS/400 Sub-second propagation

DetectionUkg Ready notifies Stacksync of record changes through webhook events. UKG Webhooks for select events (employee.created, employee.updated, account/org changes) with HMAC signing.

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

Rate-limit considerations

  • IBM AS/400: Bounded by system resources and subsystem configuration rather than an API quota.
  • Ukg Ready: Rate limits apply over roughly a 1-minute window and return HTTP 429 when exceeded (back off / exponential retry); UKG Webhooks run on a tiered quota with a free tier around 10,000 event notifications per month and 14-day event retention.
What ships with IBM AS/400 ⇄ Ukg Ready

Connect IBM AS/400 and Ukg Ready for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every IBM AS/400–Ukg Ready connection.

Real-time

Two-way sync

Changes in IBM AS/400 or Ukg Ready instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever IBM AS/400 or Ukg Ready 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 IBM AS/400 or Ukg Ready record.

Observability

Monitoring

Track your IBM AS/400 ⇄ Ukg Ready sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between IBM AS/400 and Ukg Ready.

How the IBM AS/400 and Ukg Ready connectors work

IBM AS/400

Integration surface
SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access
Authentication
IBM i user profile credentials (database credentials)
Change detection
Journal-based CDC by reading journal receivers on journaled files; polling as a fallback
Capabilities
read · write · CDC
Rate limits
Bounded by system resources and subsystem configuration rather than an API quota.

Ukg Ready

Integration surface
UKG Ready REST API (v1/v2) plus the Import Tool (XML transactions) and Report-as-a-Service (IBM Cognos); a legacy SOAP API also exists
Authentication
A 7-digit company short name, a Web API key (Company Setup > Login Config), and a dedicated API service-account user (username/password) are exchanged for a session Bearer token sent on every request; Onboarding/Recruiting endpoints use a separate authorization token
Change detection
UKG Webhooks for select events (employee.created, employee.updated, account/org changes) with HMAC signing; broad change capture via polling REST endpoints with date filters or scheduled Report-as-a-Service extracts
Capabilities
read · write · webhooks
Rate limits
Rate limits apply over roughly a 1-minute window and return HTTP 429 when exceeded (back off / exponential retry); UKG Webhooks run on a tiered quota with a free tier around 10,000 event notifications per month and 14-day event retention
How it works

How to connect IBM AS/400 to Ukg Ready — 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 IBM AS/400 and Ukg Ready 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
    IBM AS/400 connected
    Ukg Ready connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the IBM AS/400 and Ukg Ready 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 · IBM AS/400 ⇄ Ukg Ready
    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
    IBM AS/400 Ukg Ready
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

IBM AS/400 and Ukg Ready 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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 433 integrations available for IBM AS/400 and Ukg Ready.

Popular · 7 of 433
Coworkers laughing in front of a laptop in a casual office setting

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