Migrate from RECRU to Recruit CRM & ATS

RECRU candidate profiles include parsed CV fields (name, email, phone, skills, work history), AI-generated match scores, application history, and custom tenant properties. We map all standard parsed fields directly to Recruit CRM's candidate record fields. RECRU's proprietary AI match scores are preserved as a custom float field rcru_match_score__c on the candidate record; these scores have no fixed calibration range and are not comparable to any native scoring system in Recruit CRM.

RECRU job requisitions carry title, description, department, location, salary range, and hiring pipeline stages. We migrate Jobs as-is to Recruit CRM's Job object and preserve the pipeline stage order. If Recruit CRM uses a predefined pipeline structure that differs from RECRU's stage names, we map each RECRU stage to the closest Recruit CRM equivalent and flag any stages with no clear match for customer review.

RECRU stores workflow rules as structured JSON in the database with a visual multi-step rule builder interface. Recruit CRM uses a trigger-action automation model. Multi-step conditional branches in RECRU cannot map 1:1 to Recruit CRM's simpler automation structure. We export the full RECRU rule graph as a JSON document and deliver a written mapping table showing each RECRU rule, its conditions and actions, and the recommended Recruit CRM automation equivalent. The customer rebuilds these inside Recruit CRM's workflow builder.

RECRU user accounts carry name, email, role, and team assignment. We migrate active user records and map them to corresponding owner fields on Candidates and Jobs in Recruit CRM. Owner resolution is performed by email match. Any RECRU user without a matching Recruit CRM User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Custom candidate and job properties added by the RECRU tenant are migrated as key-value pairs. We extract each field name, data type, and current values and create equivalent custom fields in Recruit CRM where the target schema supports them. For types not natively supported by Recruit CRM (e.g., non-standard picklist formats), we fall back to text fields and flag them for the customer's admin to finalize after migration.

Email threads and message logs attached to RECRU candidate records are migrated as a flattened activity log in Recruit CRM. RECRU's original thread structure is not preserved in most destination systems. We render each message as a separate activity entry with the sender, recipient, timestamp, and body preserved. Attachments are linked to the activity record where Recruit CRM's schema supports it.

Interview events stored in RECRU carry date, interviewer, and outcome. We map these to Recruit CRM's calendar event or candidate activity records. The mapping preserves the interviewer reference, scheduled date and time, and outcome status. Note that Recruit CRM's Google Calendar sync does not handle deleted meeting deletion propagation — we document this limitation and recommend a manual calendar review post-migration.

Tags applied to candidates in RECRU are migrated as flat label arrays attached to the candidate record in Recruit CRM. The tag naming convention is preserved as-is. If the customer has used tags for segmentation or filtering workflows, we note the full tag inventory in the migration report.

Pipeline stage names and their ordering migrate from RECRU. If Recruit CRM's default pipeline structure differs from the RECRU stage sequence, we map each stage to the closest equivalent and flag any RECRU stages that have no clear destination equivalent. The customer confirms the final pipeline configuration before production migration.

Evaluation scorecards submitted by interviewers in RECRU are exported as structured JSON objects. Recruit CRM does not have a native scorecard object equivalent to RECRU's format. We attach these as formatted notes on the candidate record with the original scorecard JSON preserved as a custom long-text field for reference. The customer reviews these post-migration to determine whether to manually recreate structured scorecards in Recruit CRM's format.