Migrate your Recruit CRM & ATS data

Candidates are the primary object in Recruit CRM, storing profile data, resume files, skills, status, and source. The API exposes candidates at /v1/candidates with standard CRUD endpoints. We migrate all candidate fields including custom properties and associated job histories.

Jobs represent open requisitions with associated pipeline stages and assigned recruiters. The Jobs endpoint supports associated custom fields per job-candidate pair. We preserve job structure, stage configurations, and assignment records during migration.

Contacts are distinct from candidates in Recruit CRM, representing hiring managers, referrers, or other business contacts separate from job-seeking candidates. Contacts support custom fields and can be linked to companies.

Companies store client organizations, with associated contacts, jobs, and deals. The Companies endpoint supports custom fields. We map company-contact associations and preserve deal linkage during migration.

Deals track placement or business transactions tied to companies and candidates. Deal stages and values map to destination CRM opportunity objects but require value translation since field names and stage labels differ across platforms.

Tasks linked to candidates, contacts, or jobs are exposed via the API. We preserve task assignments, due dates, and status but note that completed versus open task counts affect the migration scope.

Meeting records with date, time, attendees, and outcome are migrated as activity records. The API exposes meeting endpoints that we map to the destination's calendar or activity object.

Notes attached to candidates, companies, or jobs are stored as free-text records. We preserve the full note content and its association to the parent object during migration.

Call log records include duration, outcome, and linked contact or candidate. We migrate call log entries as activity records in the destination system, preserving timestamps and outcomes.

Hotlists are curated candidate lists with custom names and saved search criteria. We migrate the candidate IDs in each hotlist as a tagged group or list in the destination platform since hotlist structure is platform-specific.

Recruit CRM supports nested custom fields on Candidates, Jobs, Contacts, Companies, and Deals. Custom field schemas vary by organization and must be mapped field-by-field to the destination's equivalent custom properties.

Email sequences are automation objects defining outreach cadences. We do not migrate sequence logic directly; instead we identify which candidates are enrolled in active sequences and preserve enrollment status as tags or notes in the destination.

Files attached to candidates (resumes, cover letters) and companies (contracts, briefs) are accessible via the Files API. Large volume file migrations require chunked extraction and re-upload to the destination's file storage.

Recruit CRM user accounts map to recruiters, consultants, and admins. We map active user assignments on Jobs, Candidates, and Deals to the corresponding user records in the destination platform. Inactive or archived users require separate handling.

Pipeline stages are fully customizable per pipeline. We extract the complete stage configuration including stage names, order, and any automation triggers, then rebuild the equivalent pipeline structure in the destination ATS.