Skip to content
ERP / Human resources · Two-way sync platform

SuiteAnalytics and UKG Pro integration

Plan how SuiteAnalytics and UKG Pro should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

  • Scope your workflow with an integration engineer
  • Review the systems, records, and updates you need
Integration planning
stacksync.com
SuiteAnalytics
UKG Pro
Review the integration scope

Built for teams where self-serve, reliability and scale matter

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

Proposed workflow

Worker or employee sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving SuiteAnalytics Employee or UKG Pro Employee (Person Details) needs a defined result in the other system.

  1. Start with SuiteAnalytics Employee and UKG Pro Employee (Person Details). Use the record-matching and field-ownership rules from your mapping worksheet.

  2. Resolve organization, position, manager, and effective-date context before dependent changes.

  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest a future-dated transfer, a rehire, concurrent assignments, and an employee with a missing manager.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between SuiteAnalytics and UKG Pro
SuiteAnalytics recordUKG Pro recordRecord matchingField ownership
EmployeeDocumented record: Read: Supported. Write: see guide.Record matchingEmployee (Person Details)Proposed record; confirm Stacksync object support.Use the worker/employment ID and distinguish a person from their employment records, assignments, or rehires.HR owns employment decisions and effective dates. Downstream changes must follow the authorized joiner/mover/leaver process.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

SuiteAnalytics

Read-only connector

Record types covered in the setup guide

Record typesCoverage and requirements
  • Customer
  • Contact
  • All custom objects
  • Nexus
  • Tax Type
  • Sales Tax Item
  • Billing Schedule Customer Subsidiary Relationship
  • Account
  • Accounting Period
  • Bin Transfer
  • Currency Rate
  • Price Level
  • Term
  • Subsidiary
  • Vendor
  • Vendor Category
  • Employee
  • Other Name Category
  • Vendor Subsidiary Relationship
  • Project
  • Project Status
  • Project Task
  • Job Type
  • Task
  • Partner
  • Customer Status
  • Phone Call
  • Support Case
  • Calendar Event
  • Note Type
  • Message
  • Contact Category
  • Contact Role
  • Customer Category
  • Customer Message
  • Department
  • Expense Category
  • Job Status
  • Classification
  • Location
  • Saved Searches
  • Deleted Records
Reading: ✅ Supported. Updating this object: confirm availability.
  • Invoice
  • Sales Order
  • Check
  • Credit Card Charge
  • Credit Card Refund
  • Credit Memo
  • Currency Revaluation
  • Customer Deposit
  • Customer Payment
  • Customer Refund
  • Deposit
  • Deposit Application
  • Estimate
  • Expense Report
  • Intercompany Journal Entry
  • Advanced Intercompany Journal Entry
  • Item Fulfillment
  • Item Receipt
  • Journal Entry
  • Opportunity
  • Purchase Order
  • Transfer
  • Vendor Bill
  • Vendor Credit
  • Vendor Payment
✅ Supported. Confirm field permissions and sync direction.
  • Lead
  • Case
  • Published Reports
Reading: 🔓 Request Access. Updating this object: confirm availability.

Read the SuiteAnalytics connector guide

UKG Pro

Connection and object support require review

Record types to review with Stacksync

Record typesCoverage and requirements
  • Employee (Person Details)
  • Employment Details
  • Job / Position History
  • Compensation Details
  • Payroll (Pay Statements, Direct Deposit, Earnings)
  • Terminations
Confirm support for this record type and the direction you need.

Discuss UKG Pro requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits
Connection requirementSuiteAnalyticsUKG Pro
Integration interfaceSQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect)REST API (UKG Pro HCM REST services) with separate Onboarding and Recruiting REST APIs, plus legacy SOAP-based UKG Pro Web Services
AuthenticationNetSuite token-based authentication with integration credentials, access token, account ID, and a role with SuiteAnalytics permissions.Confirm the credentials, API plan, and permissions required for UKG Pro.
Change detectionThe saved Stacksync guide does not specify the change-detection mechanism.Confirm how Stacksync detects changes for this connector and the objects you need.
Read accessAvailable for supported recordsConfirm with Stacksync
Write accessNot supported by this connectorConfirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

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

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:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

SuiteAnalytics
Integration interface
SQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect)
Authentication
NetSuite token-based authentication with integration credentials, access token, account ID, and a role with SuiteAnalytics permissions.
Change detection
The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Read access
Available for supported records
Write access
Not supported by this connector
Setup requirements
  • Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication.
  • Create an integration, access token, and role with the SuiteAnalytics Connect permissions listed in the authorization guide.
Limitations to check
  • SuiteAnalytics is a read-only route. Use a separately supported NetSuite connector for write-back requirements.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

SuiteAnalytics setup guide
UKG Pro
Integration interface
REST API (UKG Pro HCM REST services) with separate Onboarding and Recruiting REST APIs, plus legacy SOAP-based UKG Pro Web Services
Authentication
Confirm the credentials, API plan, and permissions required for UKG Pro.
Change detection
Confirm how Stacksync detects changes for this connector and the objects you need.
Read access
Confirm with Stacksync
Write access
Confirm with Stacksync
Setup requirements
  • Identify the UKG Pro account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for UKG Pro, including read/write support, authentication, and initial-load limits.
Limitations to check
  • Confirm Stacksync support for UKG Pro and the record types your workflow needs.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.
Technical documentation

Prepare SuiteAnalytics and UKG Pro access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

SuiteAnalytics setup checklist
  • Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication.
  • Create an integration, access token, and role with the SuiteAnalytics Connect permissions listed in the authorization guide.

Setup guides: Authorize SuiteAnalyticsNetSuite SuiteAnalytics Connect

UKG Pro setup checklist
  • Identify the UKG Pro account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for UKG Pro, including read/write support, authentication, and initial-load limits.
Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the SuiteAnalytics and UKG Pro planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Record matching

Employee / Employee (Person Details)

Compare whether SuiteAnalytics Employee and UKG Pro Employee (Person Details) describe the same worker or employee in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

SuiteAnalytics
Documented record · Read: ✅ Supported. Write: see guide.
UKG Pro
Object support to establish
Record identity
Use the worker/employment ID and distinguish a person from their employment records, assignments, or rehires.
Field ownership
HR owns employment decisions and effective dates. Downstream changes must follow the authorized joiner/mover/leaver process.

Fields to include

  • Source worker ID
  • Employment status
  • Effective date
  • Manager reference
  • Department
Record dependencies
Resolve organization, position, manager, and effective-date context before dependent changes.
Validation
Test a future-dated transfer, a rehire, concurrent assignments, and an employee with a missing manager.
Recovery
Reconcile effective dates before applying a delayed change; route ambiguous termination or access changes for review.

References: SuiteAnalytics: Employee documentationUKG Pro: Employee (Person Details) documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Employee / Employee (Person Details) to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit
Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Check record matching: Use the worker/employment ID and distinguish a person from their employment records, assignments, or rehires. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit
A vendor-built integration may fit if it supports your SuiteAnalytics and UKG Pro record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify Employee / Employee (Person Details), update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when SuiteAnalytics and UKG Pro need a transformation, approval, or action outside a direct record sync.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit
Consider for a one-time SuiteAnalytics / UKG Pro migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Worker or employee sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Employee or Employee (Person Details) record needs a defined result in the other system.

  1. Start with SuiteAnalytics Employee and UKG Pro Employee (Person Details). Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve organization, position, manager, and effective-date context before dependent changes.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a future-dated transfer, a rehire, concurrent assignments, and an employee with a missing manager.

If it fails: Reconcile effective dates before applying a delayed change; route ambiguous termination or access changes for review.

Worker lifecycle planning for UKG Pro and SuiteAnalytics

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A worker joins, moves, or leaves in UKG Pro; a downstream process in SuiteAnalytics needs the approved context.

  1. Identify the worker and employment record represented by Employee (Person Details) or Job / Position History. Retain effective dates and organizational scope.
  2. Determine what Customer or Vendor represents: an operational task, a user identity, or a reporting row. Define a relationship; do not map these records as if they were the employee itself.
  3. Require the process owner to approve any access, payroll, or account action and assign an exception owner.

Expected result: Rehires and concurrent assignments keep distinct employment context; delayed updates do not reverse a newer effective state.

If it fails: Inspect employment identity and effective dates before retrying the downstream action.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Employee / Employee (Person Details)

Test case

Test a future-dated transfer, a rehire, concurrent assignments, and an employee with a missing manager.

Expected result

The expected worker or employee relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated worker or employee change

Investigate

Inspect SuiteAnalytics Employee and UKG Pro Employee (Person Details), their IDs, and the destination error.

Next action

Reconcile effective dates before applying a delayed change; route ambiguous termination or access changes for review.

A record type or update is unavailable

Investigate

Check the SuiteAnalytics and UKG Pro connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between SuiteAnalytics and UKG Pro

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

SuiteAnalytics UKG Pro Direction requires confirmation

Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.

Apply updatesConfirm that Stacksync can create or update the records you need in UKG Pro.

UKG Pro SuiteAnalytics Direction not supported

Detect changesThis route requires read access from UKG Pro and write access to SuiteAnalytics; the documented connector restrictions do not permit it.

Apply updatesUse a supported direction or review a separate integration method for this requirement.

Update timing and record limits
  • Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ

SuiteAnalytics and UKG Pro integration FAQ

Further reading

Resources for your technical review

Next step

Plan your integration with an engineer

Walk through your SuiteAnalytics and UKG Pro records, field mappings, and requirements with an integration engineer.

Talk to an engineer Explore plans and pricing