Migrate from Recruiterflow to Crelate

Recruiterflow Candidates map to Crelate People records. Standard fields (name, email, phone, status, source) migrate 1:1. The Candidate status values (Active, Passive, Placed, etc.) map to Crelate's Person status field. We preserve the source attribution, tags, and custom field values. For large databases (10,000+ candidates), we use Advanced Search XLS exports in parallel with targeted API reads because Recruiterflow lacks a documented bulk read endpoint. Custom field values migrate to Crelate custom fields on the Person object, but require the custom field schema from Recruiterflow support or UI export before migration.

Recruiterflow Contacts represent client relationships separate from candidates. They map to Crelate Client Contacts with the company association preserved as a Client lookup. Lifecycle stage values from Recruiterflow (prospect, active, inactive) migrate as Crelate Contact tags. Custom contact fields migrate to Crelate custom fields on the Client Contact object.

Recruiterflow Jobs represent open reqs with title, description, location, employment type, and owner. They map directly to Crelate Jobs. Job pipeline stages are configurable in Recruiterflow and map to Crelate Job status values (Open, On Hold, Filled, Cancelled). The job owner maps to the Crelate recruiter assignment. We migrate job custom fields, required skills, and benefits fields.

Recruiterflow Placements track hired candidates tied to a Job and a Client/Company. They carry compensation data (fee, rate, start date) and placement status. We map these to Crelate Placements with the Job and Client associations resolved at migration time. If the candidate was migrated before the placement, we re-link the Person record by email lookup.

Recruiterflow Companies store client organization data including address, industry, size, and associated contacts. They map to Crelate Clients. The company domain becomes the Client Website field and is used as the deduplication key during import. Custom company fields migrate to Crelate Client custom fields.

Recruiterflow Deals track revenue opportunities tied to Companies. They map to Crelate Opportunities with deal value, stage, and owner preserved. Recruiterflow's dealstage property maps to Crelate Opportunity stage values. Deal-specific fields like probability, expected close date, and custom deal properties migrate as Crelate Opportunity custom fields. We flag that Crelate's Opportunity object is primarily for business development tracking; placement revenue is handled through Placements.

Recruiterflow call logs map to Crelate Call records linked to the Person record by email resolution. Call disposition, duration, and recording URL (if stored in Recruiterflow) migrate to Crelate Call custom fields. Activity timestamp preserves the original call date for timeline ordering.

Recruiterflow notes and custom activity types migrate to Crelate Notes attached to the corresponding Person, Job, Client, or Placement record. Custom activity types are stored as separate API endpoints in Recruiterflow; we query each activity type endpoint and map them to Crelate Notes with a custom type tag indicating the original activity category.

Recruiterflow email engagement history migrates to Crelate Email records linked to the Person record. Email subject, body, timestamp, and direction (sent/received) preserve. We flag active campaign enrollment status on each email so the destination platform's outreach system can manage re-engagement without cold-email reputation risk.

Documents attached to candidates or jobs are downloaded via GET /api/external/document/get and re-uploaded as Crelate Attachments on the corresponding Person or Job record. We preserve the original filename and content type.

Recruiterflow's Off-Limits feature enforces compliance boundaries per client but has no dedicated API export endpoint. We identify Off-Limits candidates by scanning candidate tags and custom fields where the compliance boundary is stored. We recreate these as a Crelate custom property on the Person object (typically a checkbox or restricted picklist) and flag the Client association so the compliance boundary is preserved in the destination system.

Recruiterflow multi-channel sequences (email, SMS, WhatsApp, social) store enrollment status and step data per candidate. Crelate's engagement model differs from Recruiterflow's cadence architecture. We migrate sequence membership and step status as Crelate Tags on the Person record and add a Note recording the original sequence name, step, and enrollment date. We do not recreate active sequences as Crelate sequences; the customer's team configures outreach sequences post-migration.

Recruiterflow Users map to Crelate Team Members. Owner assignments on Jobs, Candidates, Deals, and Activities resolve by matching the user email address. Any Recruiterflow Owner without a matching Crelate Team Member goes to a reconciliation queue for the customer's admin to provision before record import resumes.