Migrate from In-recruiting to Recruit CRM & ATS

In-recruiting Candidates map to Recruit CRM Candidate records. We extract all candidate profile fields (name, email, phone, location, skills, experience, education) and map them to Recruit CRM's structured profile sections. In-recruiting custom fields stored as key-value pairs in the export are mapped to typed Recruit CRM custom fields created during schema design. The candidate's original created_date and last_modified_date are preserved in Recruit CRM's timestamp fields for audit.

In-recruiting Job records map to Recruit CRM Job records. The job title, description, location, employment type, salary range, and requirements migrate as structured fields. Active job status is preserved, and we sequence active jobs to be migrated last to minimize disruption to ongoing placements. In-recruiting job boards posting status maps to Recruit CRM's job_publish_status.

In-recruiting Applications map to Recruit CRM Applications attached to the relevant Job and Candidate. The application status (applied, screening, interview, offer, placed, rejected) maps to Recruit CRM's application status values, and any custom status labels in In-recruiting are translated to the closest Recruit CRM equivalent during transformation. We resolve the parent Candidate and Job references at migration time using email and job_id as dedupe keys.

In-recruiting pipeline stages map to Recruit CRM pipeline stages within the Job's pipeline configuration. We read the pipeline structure from In-recruiting (stage name, order, probability if configured) and create matching stages in Recruit CRM before any Application records are imported. Stage history timestamps migrate as stage change events attached to the Application.

In-recruiting interview records map to Recruit CRM Interview records linked to the Application. Interview date, time, interviewer name, interview type, and feedback notes migrate directly. Interview status (scheduled, completed, cancelled) maps to Recruit CRM's interview status. Calendar invitation sync between In-recruiting and Google Calendar or Outlook migrates as Recruit CRM interview records with the calendar sync configured in the destination.

In-recruiting notes attached to Candidates, Jobs, or Applications map to Recruit CRM Note records. Notes are linked to the parent record via ContentDocumentLink. Rich text formatting in In-recruiting notes is preserved as HTML in Recruit CRM's note body. Note timestamps and author information migrate as metadata on the Note record.

In-recruiting Company records map to Recruit CRM Client records if the agency uses the CRM module. Company name, address, industry, size, and contact persons migrate as structured fields. In-recruiting companies that function purely as candidate employers without a sales relationship map to Recruit CRM's Company section within the Candidate profile instead. The customer's use of In-recruiting's company module determines the mapping path during scoping.

In-recruiting Users map to Recruit CRM User records. We match users by email address as the primary key. In-recruiting role assignments (recruiter, hiring manager, admin) map to Recruit CRM roles, and the customer's admin configures permissions in Recruit CRM post-migration. Any In-recruiting user without a matching email in the destination is held in a reconciliation queue.

In-recruiting custom fields (text, number, date, dropdown, checkbox) are read from the export and mapped to Recruit CRM custom fields. Text fields map to Recruit CRM text fields, dropdowns to picklist or multi-select picklist, dates to date fields, and checkboxes to boolean fields. We create the destination custom field schema in Recruit CRM before any record import begins. Dropdown options are preserved verbatim from In-recruiting unless the customer requests consolidation.

In-recruiting candidate attachments (resumes, cover letters, certificates) migrate to Recruit CRM Document records attached to the Candidate. Files are uploaded to Recruit CRM's document storage and linked via ContentDocumentLink. File type and original filename are preserved in the document metadata.

In-recruiting engagement records (calls, emails, meetings, tasks logged within the ATS) map to Recruit CRM Activity records. Call logs with duration and disposition migrate as Call activities. Email activities preserve the email body and timestamp. Meeting activities preserve date, time, and attendee list. All activities are linked to the parent Candidate, Job, or Application record.