Workday Data Migration Pipeline — Release Highlights v1.0.50

Release: v1.0.50
Audience: Platform administrators and IT teams performing tenant onboarding

Overview

v1.0.50 ships a first-class migration pipeline for organisations moving from Workday. Rather than requiring manual data exports or custom scripting, the pipeline provides a guided, auditable path from raw Workday tenant data to fully loaded platform records — covering employees, org hierarchies, compensation, benefits, and financial data in a single operation.

What You Can Migrate

The pipeline supports the following data domains in a single run:

Domain	Examples
Employees	Worker profiles, contact info, employment type, job titles
Org Structure	Departments, supervisory orgs, reporting lines, cost centres
Compensation	Salary plans, pay grades, allowances, bonus structures
Benefits	Benefit plans, enrolment records, coverage levels
Financial Data	Budget lines, spend categories, ledger account mappings

How It Works

The migration runs as four sequential, clearly demarcated phases.

Phase 1 — Extract

The pipeline authenticates with your Workday tenant using the credentials configured in Settings → Integrations → Workday and pulls raw data across all selected domains. No data is written to the platform during this phase.

Phase 2 — Validate

All extracted records are checked against platform schemas and referential-integrity rules. Validation errors are surfaced before any data is written, giving you the opportunity to correct issues in Workday or adjust field mappings without risking partial imports.

Phase 3 — Transform

Validated records are mapped from Workday's data model to the platform's native structures. Field-level transformation rules (e.g. currency normalisation, date format conversion, org ID remapping) are applied automatically based on the configured mapping templates.

Phase 4 — Load

Transformed records are written to the platform database. The load phase supports rollback — if a domain load fails mid-run, previously loaded domains within the same run can be unwound to maintain consistency.

Progress Tracking

The migration dashboard (accessible at Admin → Data Migration → Workday) provides:

A phase indicator showing which of the four phases is currently active
Per-domain progress bars with live counts of processed, skipped, and failed records
An estimated completion time that updates as the run proceeds
Downloadable JSON and CSV run logs for audit trails and support escalations

Conflict Resolution

When incoming Workday records overlap with data already present in the platform (e.g. during a re-migration or a partial prior import), the conflict resolution UI is triggered automatically.

Resolution Strategies

Strategy	Behaviour
Keep existing	The current platform record is preserved; the incoming Workday record is discarded
Overwrite with source	The Workday record replaces the existing platform record entirely
Merge manually	A field-level editor opens, allowing you to pick individual values from either record

Batch Resolution

For high-volume conflicts of the same type (e.g. hundreds of compensation records with a mismatched currency field), you can apply a single resolution strategy to an entire conflict group rather than resolving each record individually.

Getting Started

Configure the Workday integration — Navigate to Settings → Integrations → Workday and enter your Workday tenant URL, client ID, and client secret.
Select domains — Choose which data domains to include in the migration run.
Run validation — Execute a dry-run (Extract + Validate only) to review any schema errors before committing.
Start the full migration — Proceed through all four phases. Monitor progress from the migration dashboard.
Resolve conflicts — Address any flagged conflicts using the resolution UI before finalising the load.
Verify records — Spot-check imported employees, org nodes, and financial entries in their respective modules.

Notes & Limitations

Migrations run asynchronously; you can navigate away from the dashboard and return — progress is persisted.
A single migration run processes one Workday tenant at a time.
Re-running a migration against a previously loaded tenant will trigger conflict detection for all overlapping records.
Financial data migration requires the Finance module to be enabled on your plan.