Migrate from RECRU to Crelate

RECRU Candidate records map to Crelate Contact. All parsed CV fields (name, email, phone, skills, work history) migrate directly. The RECRU AI-generated match score (a float with no fixed range) is preserved as a custom float field on the Contact record. We flag it as non-calibrated and destination-agnostic in the migration report so your team does not confuse it with any native Crelate scoring system. Tags attached to the Candidate migrate as flat label arrays attached to the Contact.

RECRU Job requisitions map to Crelate Job records with title, description, department, location, salary range, and pipeline stages preserved. Pipeline stage names and order from RECRU are mapped to Crelate Job stages; if Crelate uses a predefined stage structure, we map to the closest equivalent and flag any stages with no clear destination. The owner assignment migrates by resolving the RECRU owner email to the corresponding Crelate user.

RECRU Company records map to Crelate Organization. Company name becomes the Organization name, and domain or website data maps to the Organization's web presence fields. If the source RECRU account associates contacts with companies, we resolve the Organization lookup before inserting Contacts so that the relationship is satisfied at migration time.

RECRU Deal records map to Crelate Opportunity when the customer uses Crelate's full ATS + CRM model. Deal stage maps to Crelate Opportunity stage, and fee-based values migrate as monetary fields. If the customer uses only Crelate's ATS without the CRM Opportunity model, Deals map to Job-based opportunity records using a customer-confirmed configuration during scoping.

RECRU User accounts (name, email, role, team assignment) migrate as Crelate User records. We resolve by email match. Any RECRU Owner without a matching Crelate User goes to a reconciliation queue for your admin to provision before record import resumes. Active status is preserved; inactive users in RECRU are held as inactive in Crelate unless your team confirms otherwise.

RECRU custom candidate properties added by the tenant are extracted as key-value pairs with their field types (text, integer, float, date, picklist). We pre-create equivalent custom fields in Crelate under the Contact Core Record during the schema phase, falling back to a text custom field if the Crelate field type does not support the RECRU data type directly. The logical API name in Crelate is set per Crelate's naming convention during field creation.

Email threads and message logs attached to RECRU candidate records are migrated as a flattened activity log in Crelate. The original thread structure is not preserved in Crelate because Crelate's activity model renders each message as a discrete activity entry. We map sender, recipient, timestamp, and body for each message. Attachment references migrate as linked file records pointing to the Contact.

Interview events stored in RECRU (date, interviewer, outcome) map to Crelate Event records when the destination account supports calendar events. We preserve start time, end time, location, and interviewer assignment as attendee records. If the Crelate account does not have calendar event support enabled, interviews migrate as activity records with a custom type field.

Tags applied to candidates in RECRU migrate as flat label arrays attached to the Contact record in Crelate. Crelate's API supports Tags on various record types using a category-key structure; we map RECRU tags to the Crelate default category unless your account uses custom tag categories, in which case we confirm the category mapping during scoping.

Pipeline stage names and order are migrated from RECRU to Crelate. Crelate uses stage definitions on Job records and Opportunity records. We map RECRU pipeline stages to the configured stage structure in Crelate and flag any stages that have no clear equivalent in the destination. Stage probability percentages migrate as custom fields if the customer uses them.

Evaluation scorecards submitted by interviewers in RECRU migrate as JSON objects attached to the candidate Contact record in Crelate. Destination systems that do not natively support scorecard objects receive them as structured JSON notes. We preserve evaluator name, submission date, rating fields, and comments. The customer reviews the scorecard format during staging before final production migration.

RECRU workflow automation rules are JSON-backed in the database with a visual multi-step rule builder. Multi-step conditional branches in RECRU do not collapse cleanly into Crelate's trigger-action automation model. We export the full rule graph (triggers, conditions, branches, and actions) as a written inventory document. The customer's Crelate admin uses this to rebuild equivalent automations in Crelate's workflow builder. This is not a code migration; it is a documentation and reconstruction handoff.