Migrate from eArcu to BambooHR

eArcu Candidate records (name, contact details, work history, custom profile fields) map to BambooHR Employee records. The candidate's final application status determines whether the Employee status is Active (hired) or a historical record (former employee with termination date). Any eArcu custom fields on the candidate profile map to BambooHR custom employee fields. Assessment scores stored against the candidate attach as text or number custom fields with the assessment type and score value preserved; we flag these as reference data since BambooHR has no native assessment object.

eArcu Job Requisitions (title, department, location, employment type) map to BambooHR Job Openings. BambooHR's Job Opening supports title, employment status, location, and department. If the eArcu requisition includes a compensation range, salary banding, or recruiter assignment, these map to BambooHR Job Opening custom fields or become notes on the record. BambooHR's job opening caps per tier (5 on Core, 25 on Pro, 50 on Elite) must be confirmed against the customer's plan during scoping to avoid a plan-upgrade requirement mid-migration.

eArcu Application records link a Candidate to a Requisition with timestamps for each hiring stage transition. In BambooHR, there is no Application object; the candidate's journey from application to hire maps to the Employee record's hire date, job title, and department. We preserve the full stage progression history as an Employee File note listing each stage, the date entered, and the outcome. This gives the HR team a readable audit trail without requiring them to cross-reference a separate ATS system.

eArcu's configurable pipeline stages per requisition (screening, interview, assessment, offer, hire) have no direct equivalent in BambooHR. We extract the full stage history per application including entry dates and convert each stage to a timestamped entry in the Employee File note. The customer documents their BambooHR hiring stage configuration (if using BambooHR's ATS module) against these migrated stage entries post-migration.

eArcu cognitive test results, personality questionnaire scores, and situational judgement data are stored as linked records attached to the candidate. BambooHR has no assessment object or test-results field type. We export raw scores, assessment type names, and completion dates as text or number custom fields on the Employee record (e.g., assessment_cognitive_score__c, assessment_sjt_date__c). These are reference fields only — BambooHR does not surface them in standard reports or workflows, so the customer should treat them as archival data. If assessment results need to be actionable, a third-party assessment platform integration (e.g., Pymetrics, Criteria, Harver) is the appropriate path post-migration.

eArcu Offer records include compensation details, start dates, and approval status. These map to BambooHR Employee custom fields (e.g., offered_salary__c, offered_start_date__c, offer_approval_status__c) and/or an Employee File note with the offer details. BambooHR's Compensation Management module (Elite tier) offers structured compensation entry that can absorb offer data if the customer is on that plan tier.

eArcu user accounts, roles, and permissions (recruiters, hiring managers, admins) map to BambooHR User accounts. We export the user roster with role assignments and map to BambooHR's permission model (Full Admin, Admin, Manager, Employee). The customer provisions the BambooHR users during the discovery phase. Any eArcu role without a direct BambooHR equivalent (e.g., dedicated sourcing specialist permissions) is documented in the role-mapping sheet for manual configuration.

eArcu career portal pages, job board widgets, and branding assets are HTML and CSS platform-native configurations, not structured database records. BambooHR's hiring pages are structured templates (job title, description, location) without custom HTML. We export the career site content package where available as a reference document and deliver a rebuild guide mapped to BambooHR's Job Opening template fields. The customer's marketing or recruiting team rebuilds the branded career page experience using BambooHR's pages or an external careers-site builder.

Animated onboarding content and structured onboarding task sequences are platform-native eArcu configurations that cannot be meaningfully transferred to BambooHR's onboarding module. We export the package structure (task list, sequence order, content links) as a written rebuild guide that maps each eArcu task to a BambooHR onboarding task step. The customer's HR admin configures the BambooHR onboarding checklist using this guide. BambooHR's onboarding module supports task assignment, new hire document collection, and e-signature routing as standard features on Pro and Elite plans.

CVs, cover letters, and supporting files attached to eArcu candidates or applications are binary files extracted from the document store. We re-upload these to the corresponding BambooHR Employee File under the Documents tab, preserving the original filename and attachment date. BambooHR supports PDF, DOC, DOCX, XLS, XLSX, PNG, and JPEG uploads up to the file size limits documented in the BambooHR API. Any files exceeding size limits are flagged for the customer's admin to handle manually.