Migrate from Arcoro to BambooHR

Arcoro employee records map directly to BambooHR's employee table with standard fields (name, contact info, employment dates, department, job title) mapping 1:1. Arcoro's CoreHR exports include custom fields that map to BambooHR custom fields; we discover field names and types via Arcoro's export configuration before migration. Construction-specific certifications from Arcoro map to BambooHR's credential tracking with expiration dates and alerts preserved. Employment status normalization is required because Arcoro uses construction-specific classifications (prevailing wage, apprenticeship program) that are not BambooHR standard values; we map each status to a BambooHR picklist value during scoping and flag any that require custom status creation.

Arcoro ATS applicant records map to BambooHR's applicant records in the hiring module. Arcoro stage names (Applied, Phone Screen, Interview, Offer, Hired, Rejected) map to BambooHR stage names where a direct equivalent exists. Scorecards, interview notes, and sourcing channel metadata migrate as informational fields. Resume file attachments migrate by uploading to BambooHR's onboarding packet for candidates who advance to hire. Arcoro's sourcing channel tracking has no direct BambooHR equivalent; we preserve the channel as a custom field for reporting and flag it as requiring manual entry for new applicants post-migration.

Arcoro onboarding workflows are task-based with document checklists tied to construction onboarding requirements. We migrate completed onboarding tasks and checklist status as informational records in BambooHR. Arcoro's active workflow states (which tasks are pending, which are skipped) do not map to BambooHR's task model; we deliver a written handoff document describing each active Arcoro onboarding workflow with its trigger, assigned tasks, document checklist, and recommended BambooHR equivalent. The customer's HR team recreates workflow states and active task assignments in BambooHR post-migration.

Arcoro time entries contain hours worked, date, and optionally job cost code and overtime calculations. We extract hours by employee and pay period as historical data loaded into BambooHR as informational records linked to the employee. Arcoro's GPS-enabled clock-in/out data has no BambooHR equivalent; we preserve the raw timestamps as a custom field note for the employee's record. Job cost codes from Arcoro cannot migrate as functional cost allocations in BambooHR since BambooHR has no job costing structure; we flatten them to an informational custom field. The Arcoro next-day sync delay means we schedule extraction for the calendar day following the end of the pay period.

Arcoro payroll history includes earnings, deductions, and tax withholdings per pay period. We export historical payroll as read-only records and load them into BambooHR's employee compensation history, preserving pay period dates, gross pay, net pay, and major deduction categories. Arcoro pay frequencies (weekly, biweekly, semimonthly, monthly) map to BambooHR pay types. If Arcoro stores pay rates in a different currency from BambooHR's configured currency, we flag the discrepancy during scoping. Payroll data loads last in the migration sequence to preserve audit trails and avoid retroactive changes after cutover.

Arcoro benefit records contain active plans, coverage levels (employee, employee plus spouse, family), and election dates. We import benefit enrollments as informational records linked to the employee in BambooHR. Plan names and coverage tier labels migrate as text fields; we flag any Arcoro plans with no clear BambooHR benefit module equivalent so the HR team can create new benefit offerings post-migration. Active benefit elections are preserved with their effective dates for audit continuity, but BambooHR's benefit administration features are not automatically populated from Arcoro data.

Arcoro certifications include issue dates, expiration dates, and renewal alert settings for OSHA cards, trade licenses, and apprenticeship completions. We extract the full certification history and map it to BambooHR's employee certification tracking with expiration dates preserved. Arcoro's construction-specific certification types (OSHA 10-hour, OSHA 30-hour, trade-specific credentials) may require type classification during scoping; we create a crosswalk mapping each Arcoro type to a BambooHR credential type and flag any that cannot be cleanly categorized for manual review.

Arcoro CoreHR supports custom fields on employee records. We discover custom field names and types via Arcoro's CoreHR export configuration interface before migration. Custom fields map to BambooHR custom fields of the equivalent type (text, number, date, dropdown) with any Arcoro validation rules applied as value transformations in our migration layer. Arcoro CoreHR custom exports must be pre-configured before they can be automated; we include a pre-flight check in the migration plan at least one week before the extraction window to confirm export configurations are in place.

Arcoro stores documents per employee including onboarding paperwork, signed agreements, performance reviews, and OSHA forms. We export available attachments and map them to BambooHR's employee file management, linking each document to the corresponding employee record. Arcoro document metadata (document type, upload date, uploaded by) migrates as file notes. BambooHR's file upload API accepts documents under 10 MB per file; we chunk larger files and flag any that exceed this limit for manual upload post-migration.

Arcoro job cost codes reference the construction ERP and encode job, phase, cost code, and cost class dimensions simultaneously. BambooHR has no job costing structure; we extract job cost codes from Arcoro time entries and flatten them into an informational custom field on the employee record. The crosswalk table built during field mapping captures each Arcoro job cost code and its meaning so the HR team and accounting department have a reference for post-migration reconciliation. Any job cost codes without a clear mapping go to a flag list for the customer's finance team to resolve.