HRMS migration
Field-level mapping, validation, and rollback between UKG Ready and Crelate. We move data and schema; workflows are rebuilt natively in Crelate.
UKG Ready
Source
Crelate
Destination
Compatibility
6 of 13
objects map 1:1 between UKG Ready and Crelate.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Migrating from UKG Ready to Crelate is a transition from a full HCM suite to a dedicated applicant tracking system. UKG Ready functions as the system of record for employees, their compensation and benefits enrollment, time and attendance, and recruiting pipeline data. Crelate is purpose-built for talent acquisition workflows and manages Candidates, Job Orders, Placements, and hiring team Activities. We migrate the recruiting-adjacent data (employee records as contacts, candidates, job postings, and interview history) and flag that payroll, benefits, accrual balances, time entries, and pay statement data have no native equivalent in Crelate and require manual handoff to HR or payroll systems. Workflow configurations, HR Action Request templates, and Benefits workflows do not migrate; we deliver a written inventory for the customer's admin to rebuild in Crelate's workflow builder.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a UKG Ready object lands in Crelate, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
UKG Ready
Employee
Crelate
Contact
1:1UKG Ready employee records map to Crelate Contact. We preserve first name, last name, email, phone, address, hire date, employment status, and manager relationship. The manager relationship in UKG maps to the manager field on Crelate Contact. HR Custom Fields on the Employee object migrate as Crelate Custom Properties with field type validated against Crelate's supported property types (text, number, date, dropdown) during scoping. Employment status values (active, inactive, terminated) map directly to Crelate Contact status.
UKG Ready
Employee (recruiter or hiring manager reference)
Crelate
User
1:1UKG Ready employees who participate in recruiting (hiring managers, interview panelists, HR recruiters) map to Crelate User records. We match by email address. Any UKG Ready employee referenced as a hiring manager without a corresponding Crelate User goes to a reconciliation queue for the customer's admin to provision the account before activity import begins.
UKG Ready
Base Compensation
Crelate
Contact Custom Property
lossyUKG Ready Base Compensation records (salary amount, pay type, effective date) have no native equivalent in Crelate's ATS schema. We store the most recent compensation data as text-based Custom Properties on the Crelate Contact (e.g., Annual Salary, Pay Type, Compensation Effective Date) and flag during scoping that this is reference data only, not a native compensation tracking capability. Full compensation history does not migrate.
UKG Ready
Accrual Balances
Crelate
Not migrated
lossyUKG Ready accrual balances (PTO, sick leave, and other leave types) have no equivalent in Crelate's ATS schema. Accrual tracking is an HR system function, not an ATS function. We document accrual balance snapshot values for each employee in a written reference sheet for the customer's HR admin to maintain in their payroll system. No accrual data moves into Crelate.
UKG Ready
Cost Center
Crelate
Department or Contact Custom Property
lossyUKG Ready Cost Center data maps to Crelate Department if the organizational structure is relevant to talent acquisition (hiring team ownership, requisition routing). We confirm during scoping which Cost Center field holds the primary organizational unit, since third-party integrations specifically reference the third Cost Center field regardless of its label. Crelate Departments are flat groupings; Cost Center hierarchies in UKG flatten to a single Crelate Department assignment per Contact.
UKG Ready
Position (Enterprise tier)
Crelate
Department or Team
lossyUKG Ready Position data (available in Enterprise tier only) defines job title, department, and reporting structure. We map Position titles to Crelate Department or Team for requisition ownership and candidate routing. Position-based reporting hierarchies do not have a Crelate equivalent and are documented in the written organizational handoff rather than migrated.
UKG Ready
Benefits Plans
Crelate
Not migrated
lossyUKG Ready benefits enrollment data, carrier connections, and plan types do not migrate to Crelate. Benefits administration is an HR system function outside ATS scope. We document the existence of benefits enrollment records per employee as a written reference sheet for the customer's HR admin to maintain in their payroll system. No benefits data moves into Crelate.
UKG Ready
Pay Period Profile
Crelate
Not migrated
lossyUKG Ready Pay Period Profile definitions (weekly, bi-weekly, semi-monthly payroll cycles) have no equivalent in Crelate. We document the pay period configuration in the written handoff as relevant for HR administrators who may need this context when managing offer letters or start dates within Crelate. No pay period data migrates.
UKG Ready
Candidates (UKG Ready Recruitment module)
Crelate
Candidate
1:1If UKG Ready contains candidate records from its recruitment module, these migrate to Crelate Candidate. We preserve all application stage history, source information (referral, job board, direct), and any existing candidate score or rating. Pipeline stage names from UKG map to Crelate pipeline stages during the stage alignment step of configuration. Candidate attachments migrate as file links in Crelate.
UKG Ready
Job Posting / Job Requisition
Crelate
Job Order
1:1UKG Ready job postings and requisitions map to Crelate Job Orders. We preserve job title, job description, department, location, employment type (full-time, part-time, contract), and the open or closed status. The recruiting pipeline stage from UKG (e.g., Open, On Hold, Filled) maps to Crelate Job Order status. Candidate count per job and source breakdown migrate as reference data on the Job Order.
UKG Ready
Interview and Hiring Activity
Crelate
Activity
1:1UKG Ready interview activities, evaluation scores, and hiring workflow actions migrate to Crelate Activity records. We preserve activity type (interview, assessment, screening call), date, duration, participant list (linked to Crelate User or Contact by email), and any scoring or rating data. Activity ordering is preserved by timestamp. Bulk API chunking handles large activity volumes to avoid timeout during import.
UKG Ready
Workflow Configurations
Crelate
Not migrated
lossyUKG Ready workflow configurations (HR Action Requests, Benefits workflows, Time Approval workflows, Performance Review workflows) are destination-dependent and do not transfer 1:1 to Crelate. We do not migrate workflows as code. We deliver a written inventory of every active UKG Ready workflow with its trigger, conditions, and actions for the customer's admin to rebuild in Crelate's workflow builder. HR Action Request workflows require particular review because Crelate's workflow model differs significantly from UKG's.
UKG Ready
Company
Crelate
Company
1:1UKG Ready companies mapped as clients or customer organizations (distinct from the employing organization) migrate to Crelate Company records. We preserve company name, address, industry, and any associated contacts or candidate relationships. If UKG Ready Company records serve exclusively as the employer organization, they are handled within the Employee-to-Contact mapping instead.
| UKG Ready | Crelate | Compatibility | |
|---|---|---|---|
| Employee | Contact1:1 | Fully supported | |
| Employee (recruiter or hiring manager reference) | User1:1 | Fully supported | |
| Base Compensation | Contact Custom Propertylossy | Fully supported | |
| Accrual Balances | Not migratedlossy | Mapping required | |
| Cost Center | Department or Contact Custom Propertylossy | Fully supported | |
| Position (Enterprise tier) | Department or Teamlossy | Fully supported | |
| Benefits Plans | Not migratedlossy | Mapping required | |
| Pay Period Profile | Not migratedlossy | Fully supported | |
| Candidates (UKG Ready Recruitment module) | Candidate1:1 | Fully supported | |
| Job Posting / Job Requisition | Job Order1:1 | Fully supported | |
| Interview and Hiring Activity | Activity1:1 | Fully supported | |
| Workflow Configurations | Not migratedlossy | Mapping required | |
| Company | Company1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
UKG Ready gotchas
Recurring pay calculation errors trace to pay rule and timesheet profile configuration
Security profile API permissions require granular configuration across five tabs
Initial employee roster import may take up to 24 hours to complete in batches
UKG API follows a lifecycle and deprecation policy with 6-12 month advance notice
Cost Center field mapping requires explicit confirmation of which field holds department data
Crelate gotchas
120 req/min API rate limit throttles bulk migrations
20 custom field per-entity cap forces data model decisions
15,000-record export ceiling on single operations
Sequences and automation workflows do not migrate
API key is a querystring parameter, not a header
Pair-specific challenges
Migration approach
Discovery and tier audit
We audit the source UKG Ready account across tier (Start, Core, Plus, or Advanced), employee volume, candidate record count, job order history, HR custom field count, Cost Center configuration, and any active recruiting workflows. We confirm whether the UKG Ready recruitment module is in use and whether candidate records exist. The discovery output is a written migration scope document specifying what migrates to Crelate, what migrates as a reference note, and what is excluded with justification.
Scope definition and field mapping specification
We define the mapping specification: employees to Crelate Contacts, candidates to Crelate Candidates, job postings to Crelate Job Orders, and activities to Crelate Activities. We confirm which Cost Center field is the primary organizational unit. We validate HR custom field types against Crelate's supported property types. We perform stage alignment between UKG recruiting stages and Crelate pipeline stages. We document all UKG data that does not migrate (compensation history, accrual balances, benefits, pay period profiles, workflow configurations) with written reference handoff instructions.
Sandbox migration and reconciliation
We run a full migration into a Crelate sandbox using production-like data volume. The customer's talent acquisition lead reconciles record counts (Contacts in, Candidates in, Job Orders in, Activities in), spot-checks 20-30 random records against the UKG source, and validates that Cost Center-to-Department mapping is correct. Stage alignment is confirmed by checking that candidate records appear in the correct pipeline stage. The customer signs off the sandbox results before production migration begins.
Destination configuration
We configure Crelate destination objects: creating Departments from UKG Cost Centers (with the confirmed field selection), adding HR custom fields as Crelate Custom Properties, creating or aligning recruiting pipeline stages to match UKG stage names and probabilities, and setting up Crelate User accounts for any UKG employees who participate in recruiting. Custom property field types are validated against Crelate's type model before any data loads.
Production migration in dependency order
We run production migration in dependency order: Crelate Users first (for any active hiring managers not yet provisioned), then Contacts (from UKG Employees), then Candidates, Job Orders, Activities, and Companies. Each phase emits a row-count reconciliation report before the next phase begins. Compensation data (stored as Contact custom properties) loads after the base Contact record is confirmed. Activities load via chunked batch processing to handle volume without timeout.
Cutover, validation, and workflow rebuild handoff
We freeze UKG Ready recruiting writes during cutover, run a final delta migration of any records modified during the migration window, then enable Crelate as the recruiting system of record. We deliver the UKG workflow inventory document to the customer's admin team with Crelate equivalent recommendations. We support a one-week hypercare window where we resolve any reconciliation issues raised by the recruiting team. We do not rebuild UKG workflows in Crelate; that is a separate engagement or an internal admin task.
Platform deep dives
UKG Ready
Source
Strengths
Weaknesses
Crelate
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across UKG Ready and Crelate.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
UKG Ready: Not publicly documented; depends on customer tier and agreement.
Data volume sensitivity
UKG Ready doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during UKG Ready to Crelate migration scoping. Not seeing yours? Book a call.
Walk through your UKG Ready to Crelate migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave UKG Ready
Other ways to arrive at Crelate
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.