Migrate from UKG Ready to Recruit CRM & ATS

UKG Ready Recruiting Candidate records map to Recruit CRM Candidate. We extract candidate name, contact information, application date, source, status, and resume attachment. The UKG Ready candidate status workflow maps to Recruit CRM's pipeline stage values. Resume files migrate as attachments linked to the candidate record. Note: UKG Ready stores some candidate data in nested HR tabs; we confirm during scoping which tabs are accessible via API for the recruiting module versus the broader HR module.

UKG Ready job requisitions map to Recruit CRM Job records. We preserve job title, job description, location, employment type (full-time, part-time, contract), department, and salary range fields. UKG Ready job status (Draft, Open, On Hold, Closed) maps directly to Recruit CRM job status. Active jobs are prioritized in migration sequencing so the recruiting pipeline is live at cutover.

UKG Ready applications (candidate-to-job associations) map to Recruit CRM's candidate-to-job link. We preserve the application date, current stage in the hiring pipeline, and any rejection reason. If UKG Ready tracks multiple applications per candidate, we map these to Recruit CRM's multiple job associations on a single candidate record.

UKG Ready interview schedules and feedback forms map to Recruit CRM Interview records with attached notes. Interview date, interviewer name, interview type, and feedback score (if structured) migrate. Free-text interview notes map to Recruit CRM's notes attached to the interview record. Interview status (scheduled, completed, cancelled) is preserved.

UKG Ready Recruiting may track client companies as part of the staffing or placement workflow. These map to Recruit CRM Client records with company name, contact person, contact details, and any client-specific notes. For organizations using UKG Ready primarily for internal recruiting (not staffing clients), this object may be empty or not used, and we skip the mapping.

UKG Ready Employee records do not map directly to Recruit CRM Candidates because the data model is employee-centric versus candidate-centric. However, for organizations tracking internal mobility, former employees as candidates, or employee referrals, we extract Employee records matching specific criteria (status = terminated, flagged for internal mobility, or referral source) and map them to Recruit CRM Candidates with a source field indicating internal origin. Standard active employees are not migrated to Recruit CRM's candidate pool.

UKG Ready Cost Center assignments on employee records may indicate the hiring department for requisitions or the candidate's target team. We confirm during scoping which Cost Center field (UKG Ready supports multiple) holds the primary organizational unit and map it to Recruit CRM's department or team assignment on the Job or Candidate record. UKG Ready documentation confirms integrations map to specific numbered Cost Center fields regardless of label.

Recruit CRM logs email communications on the candidate record. UKG Ready Recruiting email engagements migrate as communication log entries with timestamp, direction (sent/received), subject, and body. We preserve email threading context where UKG Ready exposes it. Email attachments migrate as candidate attachments.

UKG Ready offer letter records (if part of the recruiting module) map to Recruit CRM candidate custom fields for offer status, offer amount, start date, and offer response. We confirm during scoping which offer fields are exposed via API. Offer letter documents migrate as attachments on the candidate record.

UKG Ready HR Custom Fields on the Employee object (up to 10 via the Put HR Custom Fields API) do not map directly to Recruit CRM's candidate schema. However, if custom fields on candidates were configured in UKG Ready Recruiting, we map these to Recruit CRM custom candidate fields. Field type mapping (text, date, picklist) must be validated during scoping. Any HR-only custom fields (pay rate, benefits tier) are excluded from ATS migration scope.