Migrate from Arcoro to Crelate

Arcoro ATS applicant records map to Crelate Contacts representing candidates. We extract the full applicant profile including resume attachments, sourcing channel, stage history, scorecards, and notes. Arcoro stage names (e.g., Applied, Phone Screen, Interview, Offer) map to Crelate pipeline stages. Scorecard ratings and interview feedback migrate as custom fields on the Contact record. The candidate's email address is the dedupe key.

Arcoro applicant stage progression history migrates to Crelate's job pipeline stage history. Each stage transition is recorded as a timestamped entry on the Contact record linked to the relevant Job. We preserve the original stage name and transition date so recruiters can review the candidate's full journey.

Arcoro CoreHR Employee records map to Crelate Contacts representing internal employees (if the recruiting team uses Crelate for internal mobility or redeployment). Standard fields (name, department, title, hire date, termination date) migrate as Contact custom fields. Arcoro employment history and termination records migrate as notes or custom fields depending on the field type. We flag any Employee records with no corresponding applicant or candidate profile for the customer's admin to reconcile.

Arcoro onboarding workflow tasks with document checklists migrate to Crelate as a combination of Contact custom fields (for task completion status) and Activity Tasks (for open items). Completed tasks with document attachments migrate as Crelate Activities linked to the Contact record. Active onboarding workflows do not transfer as automation state; we document each workflow's trigger, tasks, and document requirements for the customer's admin to reconfigure in Crelate.

Benefit records (active plans, coverage levels, election dates) migrate as Contact custom fields. Plan names and coverage tiers map to picklist values in Crelate; multi-plan enrollments use multi-select fields. Plans with no direct Crelate equivalent are flagged and mapped to the closest available field type (text or picklist) at the customer's direction. Benefit enrollment history is preserved as read-only field values.

Certification records (issue date, expiration date, renewal alerts) map to Contact custom fields in Crelate. The certification name, issuing body, expiration date, and renewal status are stored as typed fields (date, picklist) on the Contact record. We preserve the full certification history and map it to the closest Crelate custom field equivalent, flagging any OSHA, Davis-Bacon, or apprenticeship certifications that require a dedicated field label in the destination.

Arcoro time entries tied to job cost codes and pay periods have no native equivalent in Crelate, which is an ATS and recruiting CRM without payroll or timekeeping functionality. We flag these records as out-of-scope, extract a summary report (total hours by employee, by pay period, by job cost code) for the customer's payroll team, and document the mapping to the destination payroll system's time entry format. The customer must maintain a separate payroll platform for ongoing time tracking.

Historical payroll records (earnings, deductions, tax withholdings) have no equivalent in Crelate. We extract payroll history as a read-only report and hand it to the customer's payroll team for import into their chosen payroll platform (Rippling, Paylocity, Gusto, or similar). Compensation context from Arcoro (salary, bonus structure) migrates as custom fields on the Contact record if the customer uses Crelate for internal employee records.

Arcoro's job cost code structure (job, phase, cost code, cost class) is construction-specific and has no Crelate equivalent. We capture a crosswalk table during field mapping, but note that these codes are only relevant when paired with a payroll or ERP system. If the customer continues using a construction ERP alongside Crelate, we flag which cost codes cannot map to Crelate fields and document them for the ERP integration team.

Documents (onboarding paperwork, signed agreements, resumes, performance reviews) stored per employee or applicant in Arcoro migrate to Crelate's document management structure. We export available attachments and map them to the appropriate Contact record via ContentDocument and ContentDocumentLink. Resume files attach to the Contact record as the primary candidate document. We flag any file type or size limitations in Crelate's storage during scoping.

Arcoro ATS custom applicant properties and CoreHR custom fields on employee records map to Crelate Contact custom fields. We discover custom field names and types via the Arcoro export configuration interface, then create matching Crelate custom fields (text, number, picklist, multi-select, date, monetary) before migration. Crelate enforces type constraints — a date field cannot map to a monetary field — so we apply a type-coercion rule during the transform phase and flag any incompatible mappings for the customer's admin to resolve.

Arcoro ATS sourcing channel data (e.g., Indeed, LinkedIn, employee referral, direct) migrates as a picklist custom field on the Crelate Contact record. This preserves the recruitment source attribution required for reporting on hiring channel effectiveness.

Arcoro interview scorecards with numerical ratings and evaluator comments map to Contact custom fields for structured ratings and Activity notes for qualitative feedback. If the scorecard uses a consistent format, we recommend creating a Crelate Activity Form with field mappings per evaluator so future interviews use the same structure. We do not migrate scorecard templates as reusable forms; we document the template structure for the customer's admin to recreate.