Migrate from Recruiterflow to Recruit CRM & ATS

Recruiterflow Candidates map 1:1 to Recruit CRM Candidates. Standard fields (name, email, phone, status, source) carry over directly. We identify Off-Limits candidates by scanning candidate tags and custom fields during scoping since Recruiterflow exposes no dedicated Off-Limits endpoint; these records receive a compliance tag in Recruit CRM to preserve client exclusivity boundaries. Custom candidate fields require schema extraction from Recruiterflow support or UI export before migration; the API does not return field definitions alongside record data.

Recruiterflow Contacts (client-side relationships) map to Recruit CRM Client Contacts. The company association migrates as a lookup to the Organization record, which is created before Contact import to satisfy the foreign key. Lifecycle stage and contact role fields carry over as custom or standard fields depending on the Recruit CRM account configuration.

Recruiterflow Jobs map 1:1 to Recruit CRM Jobs. Title, description, location, employment type, and owner fields transfer directly. Job pipeline stages are configurable per job type in Recruiterflow; we document the stage mapping and create equivalent stage values in Recruit CRM before job import. Job-status custom fields migrate to Recruit CRM custom fields of the same type.

Recruiterflow Placements track hired candidates tied to a Job and Company, carrying compensation data, start dates, and placement status. These map to Recruit CRM Placements with the candidate, job, and organization lookups resolved at migration time. Placement-specific fields like fee percentage and billing terms migrate as custom fields.

Recruiterflow Companies (client organizations) map to Recruit CRM Organizations. Address, industry, size, and associated contact data transfer directly. The Organization is created before any Client Contact or Deal import so that lookup relationships are satisfied at the moment of insert. Custom company fields migrate as typed fields in Recruit CRM after schema extraction from the source.

Recruiterflow Deals track revenue opportunities tied to Companies, analogous to Deals in Recruit CRM. Deal value, stage, probability, and owner migrate directly. Deal-specific fields like close date probability weighting map to Recruit CRM deal fields of equivalent type. We configure deal pipeline stages in Recruit CRM before migration to match the source stage set.

Recruiterflow Users map to Recruit CRM Users by email match. All owned records (Candidates, Contacts, Jobs, Placements, Deals) are re-linked to the corresponding User identity in Recruit CRM after the User records are confirmed in the destination. Owners without a matching Recruit CRM User go to a reconciliation queue for the customer to provision before record import resumes.

Recruiterflow call logs migrate to Recruit CRM Call Log entries linked to the parent Candidate or Contact. Call duration, disposition, and timestamp transfer to equivalent fields. We resolve the parent record reference (Candidate or Contact) by the original Recruiterflow record ID carried through the migration transform.

Recruiterflow notes migrate to Recruit CRM Notes linked to the parent record. Note body, author, and timestamp carry over. For notes attached to candidates or contacts, we resolve the parent record lookup by ID; for notes attached to jobs or companies, the parent reference migrates to the equivalent Recruit CRM record.

Recruiterflow exposes separate API endpoints for custom activity types. These map to Recruit CRM custom activity records configured before migration. We request the custom activity type definitions from Recruiterflow during scoping and create matching custom activity types in Recruit CRM, then migrate the activity records with their type associations preserved.

Documents attached to Candidates or Jobs in Recruiterflow are accessible via GET /api/external/document/get. We download each document and re-upload it to the corresponding record in Recruit CRM as an attachment. Document filenames and associated metadata (upload date, author) transfer alongside the binary file.

Recruiterflow tags stored on Candidates, Contacts, Jobs, and Companies migrate to Recruit CRM Tags. Tags used for compliance marking (Off-Limits, for example) are flagged during scoping and receive a corresponding Tag or custom property in Recruit CRM to maintain the compliance boundary. Tag counts and tag-to-record associations migrate as tag assignment records in Recruit CRM.