Migrate from Darwinbox to Recruit CRM & ATS

Darwinbox employee records created through the recruitment funnel map to Recruit CRM Candidate records. We extract candidate name, email, phone, current stage in the hiring pipeline, source channel, and any custom fields attached to the employee record in Darwinbox's recruitment module. The candidate's application-stage history (applied, screening, interview, offer, hired, rejected) migrates as a custom stage-history field or note in Recruit CRM since Recruit CRM tracks current stage but may not preserve a full multi-stage timestamp log without custom configuration.

Darwinbox job postings map to Recruit CRM Job records. The job title, description, location, employment type, department, and status (open, closed, on hold) migrate directly. Job board distribution settings and posting URLs from Darwinbox are documented as a text field in Recruit CRM since the destination job board integrations are configured separately in Recruit CRM's settings.

Darwinbox organisations created as hiring clients in the recruitment module map to Recruit CRM Client records. Client name, industry, location, primary contact name, and contact email migrate. If the Darwinbox tenant does not use the separate client management module and only stores client information inside job postings, we extract client details from the job records and create standalone Client records in Recruit CRM.

Darwinbox employee records that are not sourced through the recruitment funnel (existing employees being managed in core HR) can be created as Contacts in Recruit CRM if the customer's use case involves managing relationships with placed candidates or internal talent pool contacts. We map employee name, department, title, and email. This is a lookup mapping where the customer's Recruit CRM admin decides whether a Contact record is needed for each employee type.

Darwinbox tenant-specific custom fields in the recruitment module (text, number, date, boolean, or predefined-list types) are not documented in the public API schema and must be introspected from the live Darwinbox tenant before migration. We extract the field registry during discovery and map each custom field to a Recruit CRM custom field of the matching type. Recruit CRM's API supports custom field search with filter types including equals, text, longtext, number, and date. The customer admin configures the Recruit CRM custom field schema before migration day.

Darwinbox interview schedules, interviewer feedback, and rating data stored as part of the recruitment workflow map to Recruit CRM Activity records or Notes attached to the Candidate. We extract interview date, interviewer name, feedback text, and any scoring values. Darwinbox interview stage transitions are preserved as activity timestamps with a custom field for stage status.

Darwinbox user accounts with roles (admin, recruiter, hiring manager, employee) map to Recruit CRM User records. We extract user name, email, and role type and map them to Recruit CRM's user and permission model. Users without a matching Recruit CRM account are placed in a reconciliation queue for the customer's admin to provision before record import.

Darwinbox hierarchical org units and department assignments attached to employees do not have a direct Recruit CRM equivalent. We extract the org structure and map department names to a custom field or tag on the Candidate or Job record in Recruit CRM. The customer admin decides during scoping whether department data attaches to Candidates, Jobs, or both.

Darwinbox attendance punch logs, shift policies, and attendance compliance data are HCM records with no equivalent in Recruit CRM's recruitment and placement data model. We do not migrate attendance data. If the customer requires attendance tracking post-migration, we recommend a dedicated attendance or HRIS integration configured separately in Recruit CRM or a complementary tool.

Darwinbox leave types, accrual rules, and current leave balances are HCM records that do not map to Recruit CRM's ATS and CRM schema. We do not migrate leave balances. If the customer manages contractor or temp placement leave data in Recruit CRM, we can discuss a custom mapping as a separate scope item.

Darwinbox payroll runs, compensation history with effective-dated salary rows, deductions, and tax codes are HCM records that do not have a place in Recruit CRM's candidate and placement data model. Compensation expectations stated by candidates (expected salary in Darwinbox) can be mapped to a custom field on the Candidate record in Recruit CRM as a lookup mapping, but historical payroll data does not migrate.

Darwinbox performance review cycles, ratings, goals, and manager feedback are HCM records that do not have an equivalent in Recruit CRM's ATS and CRM. We do not migrate performance data. If the customer uses Recruit CRM for talent advisory or executive search and wants to track candidate assessments post-placement, we can discuss a custom assessments custom field as a separate configuration item.