Migrate from eArcu to Recruit CRM & ATS

eArcu Candidate records (name, contact details, work history, custom profile fields, assessment scores) map to Recruit CRM Candidate records. We extract all standard fields and any custom properties, mapping them to Recruit CRM's candidate schema. eArcu's assessment scores (cognitive, personality, situational judgement) export as raw values; we map these to Recruit CRM's candidate profile custom fields using the associated_fields endpoint, which requires field IDs pre-created in Recruit CRM before import.

eArcu Requisition records (title, department, location, employment type, pipeline assignment) map directly to Recruit CRM Job records. Job status, employment type, and location fields map 1:1. Any custom approval workflow configurations on requisitions are documented as a configuration reference for the customer's admin to rebuild in Recruit CRM's job settings.

eArcu Application records link a Candidate to a Requisition with timestamps for each stage transition. These map directly to Recruit CRM Application records. Stage-entry timestamps migrate as Activity records or as custom date fields on the application, preserving the original stage-progression history.

eArcu supports configurable pipeline stages per requisition. We extract the full stage history per application including stage-entry dates and translate these to Recruit CRM's pipeline stage model. Each eArcu stage becomes a Recruit CRM Stage in the configured pipeline, with probabilities mapped proportionally. If the customer has different stage configurations per requisition type, we create multiple pipelines in Recruit CRM and map each requisition type's stage set to the corresponding pipeline.

eArcu User accounts, roles, and permissions map to Recruit CRM Users. We export the user roster with role assignments and map to Recruit CRM's permission model. Owner resolution during import resolves by email match; any eArcu user without a matching Recruit CRM account is held in a reconciliation queue for the customer's admin to provision before record import resumes.

eArcu Offer records include compensation details, start dates, and approval status. Recruit CRM does not have a dedicated Offer object at all tiers, so we map offer data as custom properties on the Application record or as notes attached to the candidate. We preserve compensation amount, start date, and offer status as structured fields for the customer's admin to configure in Recruit CRM.

CVs, cover letters, and supporting files attached to candidates or applications in eArcu are extracted from the document store and re-uploaded as Attachments in Recruit CRM linked to the corresponding Candidate or Application record. We preserve original filenames and file types during re-upload.

Cognitive test scores, personality questionnaire results, and situational judgement data stored as linked records in eArcu are exported as raw score values and assessment type labels. We map these to Recruit CRM associated_fields on the Candidate record. Note that Recruit CRM does not have a native assessment object; assessment data is stored as structured custom properties on the candidate.

Career portal pages, job board widgets, and branding assets in eArcu are HTML and CSS configurations rather than structured database records. We export the content export package where available and flag any assets as requiring manual rebuild in the destination platform. Recruit CRM does not include a native career site builder, so this data is documented as a rebuild scope for the customer's web or marketing team.

Animated onboarding packages and structured onboarding task sequences are platform-native eArcu configurations that cannot be meaningfully transferred to Recruit CRM. We document the existing onboarding structure as a reference guide and deliver a rebuild guide that maps the original package to Recruit CRM's task management and application notes for the customer's admin to reconstruct.