Migrate from ADP Workforce Now to Recruit CRM & ATS

ADP Workers map to Recruit CRM Candidates. The Worker's legal name (givenName, familyName, preferredName), date of birth, gender, and ethnicity migrate to Candidate profile fields. SSN migrates to Candidate as a tax identification number for background check and onboarding workflows, stored with encrypted access controls in Recruit CRM. Work authorization status from ADP Job Data migrates to the Candidate's work authorization field. We use the ADP Worker Management API v2 /workers endpoint to extract, deduplicating by workerID.

ADP Job Data entries (position title, jobCode, businessUnit, departmentIdentifier, locationCode) map to Recruit CRM Job Orders. The ADP job title maps to Job Order title; department and location map to Job Order department and office fields. ADP does not expose a native requisition or job posting object via API — if the customer used ADP Workforce Now Recruitment for job requisitions, we extract the requisition data via the Recruitment module API and map it to active Job Orders in Recruit CRM. Closed or filled requisitions in ADP become archived Job Orders.

ADP supports 8 types of Worker Custom Fields (amount, code, date, indicator, number, percentage, string, telephone) at the Worker and Worker Person levels. However, the ADP API does not expose a read endpoint for these fields — they are write-only via API. We document which custom fields are in use during scoping, request a reference file of current values from the customer, and map those values to Candidate custom fields in Recruit CRM. Without a reference file, custom field values are flagged as data loss and excluded from migration with a reconciliation note.

ADP Locations (legal entity and work site) and Departments (reporting hierarchy) map to Recruit CRM Clients or to the internal Client record if the organization uses Recruit CRM to manage its own placements. If the customer is a staffing agency, ADP Departments that represent their own internal HR structure map to Recruit CRM's internal company record. ADP job locations map to Job Order office/location fields in Recruit CRM. We validate the location hierarchy via ADP's Validation Tables API before import.

ADP Worker contact methods (personalEmail, personalMobile, homeAddress) map to Candidate email, phone, and address fields in Recruit CRM. We extract work email and work phone from ADP's workCommunication if the Worker record has them. Multiple phone numbers are supported as separate phone type entries. The ADP mailingAddress and workAddress objects map to Candidate primary and secondary address fields.

ADP employmentStatus (active, inactive, terminated, leave) and terminationDate map to Candidate status in Recruit CRM. Active Workers in ADP migrate as active Candidates with status 'Available' or 'Placed'. Inactive Workers (on leave) migrate with status 'On Hold'. Terminated Workers migrate as archived Candidates with a termination flag and last placement date. We set the Candidate's current employment status from the most recent ADP Job Data entry.

ADP voluntary deduction instructions (health, retirement, benefits) map to Candidate records as a compliance note in Recruit CRM, not as a native deduction object (Recruit CRM does not have a payroll deduction object). Garnishments and Involuntary Withholding Orders cannot be migrated via ADP API — the Deduction Instruction API explicitly lists these as unsupported. We flag all active garnishment orders during scoping and provide a manual reconciliation checklist for the customer's HR admin to recreate in the destination HR system.

ADP benefit enrollment data (health plan, dental, vision, retirement contribution rate) maps to Candidate onboarding intake fields in Recruit CRM if the customer uses Recruit CRM's onboarding intake feature. Plan configurations (employer-specific benefit tiers) are ADP-instance-specific and do not migrate; we document the benefit plan names and enrollment elections as candidate notes for the HR admin to re-enter during new-hire onboarding. External Benefit Plans exposed via ADP's Benefits API migrate as enrollment records attached to the Candidate.

ADP time off balance records (accrued hours, leave type, leave event dates) map to Candidate records as a note entry for compliance and background purposes. Leave plan configurations and accrual rules are not exposed via API and do not migrate. We extract leave event history via the Time Off Requests API and record it as a candidate note in Recruit CRM noting the leave period, type, and duration.

If the customer used ADP Workforce Now Recruitment for active requisitions and applicant tracking, we extract candidate application data via the Recruitment module API. Each ADP applicant record maps to a Recruit CRM Candidate with an associated Job Application linked to the corresponding Job Order. ADP applicant stages map to Recruit CRM pipeline stages. We preserve the ADP application date, source (referral, job board, direct), and any score or rating submitted by ADP recruiters as candidate notes or custom fields.

ADP Validation Tables store reference values for Job Titles, Cost Numbers, Locations, and other domain lists. We map these to Recruit CRM Job Order custom fields (dropdown or tag) to maintain data consistency after migration. The ADP validation table structure is employer-specific — we extract the active values via the Validation Tables API and pre-populate the corresponding picklist or tag options in Recruit CRM before candidate import begins.