Migrate from PeopleStrong to Recruit CRM & ATS

PeopleStrong employee records that were created through the recruitment module map to Recruit CRM Candidate records. The candidate's full name splits into First Name and Last Name fields. Email, phone, and location data transfer directly. We flag that PeopleStrong employee records created outside the recruitment module (for example, direct hires bypassing the ATS) require deduplication against existing candidate records in Recruit CRM to avoid creating duplicate entries for the same individual.

PeopleStrong candidate records within the Talent Acquisition module carry stage history (applied, screened, interviewed, offered, hired, rejected) that maps directly to Recruit CRM's candidate stage pipeline. The original application date, source channel, and recruiter owner transfer as standard fields. Any PeopleStrong custom fields on candidate records are discovered during schema scoping and mapped to Recruit CRM custom fields on the Candidate object.

PeopleStrong job postings and requisitions map to Recruit CRM Job records. The job title, department assignment, location, employment type (full-time, contract, part-time), and job description text transfer directly. Salary range and compensation details from PeopleStrong map to custom fields in Recruit CRM if configured, or are noted in the job description field as a fallback. Active versus closed status on the PeopleStrong requisition maps to the Job status field in Recruit CRM.

Each PeopleStrong application record (a candidate linked to a job) maps to a Candidate-Job association in Recruit CRM. A single candidate in PeopleStrong who applied to multiple jobs generates multiple candidate-job associations in Recruit CRM. The application date, current stage within the hiring pipeline, and rejection reason (if applicable) transfer as association metadata. We preserve the stage progression history as custom fields or notes since Recruit CRM's standard interface shows the current stage.

PeopleStrong interview evaluations containing structured scores, interviewer feedback, and ratings map to Recruit CRM Notes attached to the relevant Candidate record. Structured rating values (for example, numeric scores or category-based rankings) map to custom fields on the Candidate object if Recruit CRM's schema supports them. Free-text feedback transfers as Note body text. Interviewer name and interview date transfer as Note metadata fields.

PeopleStrong offer letters stored as document attachments to candidate records migrate as file attachments in Recruit CRM linked to the corresponding Candidate record. We extract binary files via the PeopleStrong document API and upload them to Recruit CRM using the Files API, linking each file to the candidate record via ContentDocumentLink. E-signature status on the offer letter is noted in a custom field.

PeopleStrong stores candidate resumes as file attachments. We extract resume files from PeopleStrong's document API and attach them to the corresponding Recruit CRM Candidate record. Recruit CRM also supports parsing resume data into structured fields (name, email, phone, work history) if the customer opts in; we configure this parsing step during migration setup and validate the parsed output against the source resume.

PeopleStrong recruiter and hiring manager assignments on candidate and job records map to Recruit CRM User lookups. We perform an email-based lookup against Recruit CRM's User table. Any PeopleStrong user without a matching Recruit CRM account is placed in a reconciliation queue for the customer's admin to provision before record import continues. We do not create user accounts; we only resolve references to existing accounts.

PeopleStrong departments and office locations referenced by candidate and job records migrate as value lookups in Recruit CRM. Departments map to Recruit CRM's Company records if the organization uses Recruit CRM's company management for internal organizational units, or to custom picklist fields on the Job object if departments represent internal divisions rather than external client companies. We clarify the customer's data model intent during scoping.

PeopleStrong organizations with custom fields on candidate or job records require a schema discovery step before migration. We enumerate all active custom fields in the source PeopleStrong instance, identify their data types, and configure equivalent custom fields in Recruit CRM. Text fields map to text, numeric fields to number, dates to date, and picklist values to picklist or multi-select picklist depending on the field configuration. Custom field schema varies by tenant in PeopleStrong, which is why we probe during scoping rather than applying a fixed mapping template.

PeopleStrong payroll records (payrun cycles, salary components, deductions, payslips) have no equivalent object in Recruit CRM. Recruit CRM is a recruiting ATS and CRM and does not include payroll functionality. We flag payroll data as out of scope during scoping, recommend the customer retain payroll records in PeopleStrong or export them to a dedicated payroll archive, and document this decision in the migration scope sign-off.

PeopleStrong attendance logs, leave balances, and leave request records do not migrate to Recruit CRM. Recruit CRM has no attendance or time-off management module. We exclude these objects from migration scope, recommend the customer maintain them in PeopleStrong or move them to a dedicated HR system if payroll and attendance remain needed post-migration, and document the exclusion in the migration scope.