Migrate from Workforce Analytics to Recruit CRM & ATS

Workforce Analytics Employee records map to Recruit CRM Candidates. The employee's full name, email, phone, location, and employment status become candidate profile fields. The most recent job title and department from the Employee record populate the candidate's Current Title and Current Company fields. We flag records where the Employee has no email address on file; these require manual enrichment or a notes-only import to avoid Recruit CRM validation failures on the required email field.

Workforce Analytics Department records (or the department affiliation on an Employee record) have no direct Recruit CRM equivalent. We map department names to Recruit CRM Tags applied to the candidate profile, or we create a custom picklist field (e.g., Previous_Department__c) depending on the customer's reporting needs. The choice is made during scoping based on how the customer intends to filter candidates by source department.

Workforce Analytics preserves the hierarchy between employees, their roles, and their reporting relationships for org chart reconstruction. Recruit CRM has no native org chart object. We export the reporting relationship data as a structured CSV and as candidate notes documenting manager name and reporting chain. For organizations that require this data in a queryable form, we create custom lookup fields (Reports_To__c pointing to another Candidate record) and populate them during migration where the manager also exists as a candidate.

Workforce Analytics handles effective-dated employment changes as time-slice records rather than point-in-time snapshots. Each unique job assignment (title, department, manager, effective date range) becomes a separate Work History entry on the Recruit CRM candidate profile. We flatten the time-slice records into a linear employment timeline ordered by start date, preserving job title, company name, and date range. Compensation fields from Workforce Analytics do not map to standard Recruit CRM fields; these transfer to custom fields if the customer specifies a business need.

Workforce Analytics performance ratings, scorecards, or review data map to custom numeric or text fields on the Recruit CRM candidate profile (e.g., Last_Performance_Rating__c). If the customer does not have a custom field configured, we attach the most recent performance rating as a note on the candidate record. Performance trend data (multi-period ratings) is exported as a written CSV for manual review since Recruit CRM does not support time-series custom fields on candidate profiles natively.

Workforce Analytics flight-risk scores and tenure distribution benchmarks have no direct Recruit CRM equivalent. These aggregate analytics outputs do not map to individual candidate records. We export the flight-risk data as a separate written inventory (CSV or PDF) for the customer's recruiting team to review independently. In Recruit CRM, the candidate record retains the original hire date and employment status, from which the recruiting team can infer tenure independently.

Workforce Analytics hiring velocity metrics (open reqs, time-to-fill, departmental headcount plans) translate to Recruit CRM Job Orders. Each active headcount request in Workforce Analytics becomes a Job Order in Recruit CRM with the department as a tag, the job title from the req, and the hiring manager name in the recruiter assignment field. Historical time-to-fill data does not migrate; it lives in Workforce Analytics reporting and is not part of the candidate record.

Workforce Analytics compensation distribution data (salary bands, actual compensation, equity, bonus) maps to custom fields on the Recruit CRM candidate profile if the customer has a business need to carry this data into the recruitment process. Compensation data is sensitive; we apply field-level encryption in transit and at rest, and we flag any records containing compensation data for explicit customer sign-off before migration begins.

Workforce Analytics users who will use Recruit CRM post-migration need to be provisioned as Recruit CRM users. We extract the user list from Workforce Analytics by email, match against Recruit CRM's user table, and identify any gaps. The customer provisions missing Recruit CRM users before migration, as OwnerId references on candidate records require a valid Recruit CRM User.

Any custom objects configured in Workforce Analytics (e.g., Certifications, Background Checks, I-9 Records, Skills Matrices) map to Recruit CRM Custom Objects of matching API name. We pre-create the destination schema in Recruit CRM before any data import, including custom fields, picklist values, and any lookup relationships to standard objects. Compliance-related custom objects (I-9, background check status) are migrated as notes-only unless the customer specifies a business need for structured fields, due to the sensitivity of this data.