Migrate from Arcoro to Zoho Recruit

Arcoro ATS applicant records map directly to Zoho Recruit Candidate records. We extract the full applicant profile including name, email, phone, resume attachment, sourcing channel, stage history, scorecards, and notes. Arcoro stage names are mapped to Zoho Recruit Candidate Status picklist values; any stages without a Zoho Recruit equivalent require pre-migration custom picklist value creation. The Candidate's First Name, Last Name, Email, and Mobile Phone fields are mapped 1:1; additional Arcoro fields become Zoho Recruit custom fields.

Arcoro job postings map to Zoho Recruit Job Opening records. Each Job Opening carries the position title, department, location, employment type, and job description from Arcoro. Arcoro's job posting channels (where the position was advertised) migrate as a custom text field or note in Zoho Recruit. Job Opening ownership (recruiter assignment) migrates by email match to Zoho Recruit User records.

Arcoro applications (applicant tied to a job posting) map to Zoho Recruit as a Candidate record associated with a Job Opening via the Candidates subform on the Job Opening. The application date, current stage, and stage transition history are preserved as custom fields and notes on the Candidate. We do not migrate the full application form structure because Arcoro and Zoho Recruit use different form field models.

Arcoro scorecards with rating criteria and scores map to Zoho Recruit Candidate Ratings or custom multi-select picklist fields. If Arcoro uses custom scorecard templates, we flatten them to named rating fields in Zoho Recruit. Scorecard summary scores migrate as numeric custom fields for reporting. Detailed per-question responses migrate as notes for audit purposes.

Arcoro resume attachments on applicant records migrate to Zoho Recruit Candidate attachments. We export the binary attachment file from Arcoro and upload it to the corresponding Zoho Recruit Candidate record via the API or file upload endpoint. Resume parsing in Zoho Recruit must be re-run post-migration to populate structured fields from the uploaded resume.

Arcoro onboarding document attachments (I-9, W-4, signed agreements) attached to applicant or employee records are extracted and linked to the migrated Zoho Recruit Candidate as attachments. These documents are preserved as-is; Zoho Recruit does not have a structured onboarding document checklist. We flag this limitation and recommend the customer sets up a Zoho WorkDrive folder or a separate onboarding checklist tool post-migration.

Arcoro employees stored in the ATS module are split by employment status. Active employees with open internal applications migrate to Zoho Recruit Candidate records with a custom employment_status__c field. Former employees who were previously applicants migrate as Zoho Recruit Contacts with historical application notes. This split is computed at migration time using Arcoro's employee status field. Employees with no applicant record in Arcoro do not migrate to Zoho Recruit because Zoho Recruit is ATS-focused and does not hold general employee records.

Arcoro onboarding task checklists (documents signed, training completed, HR forms submitted) have no direct Zoho Recruit equivalent. We migrate task completion status as custom fields on the Candidate record (checkbox fields for each onboarding item). We do not migrate the task workflow itself. We recommend using Zoho Creator or a separate onboarding tool to rebuild the checklist workflow post-migration.

Arcoro CoreHR employee records including employment history, compensation, benefits, and performance reviews are outside Zoho Recruit's ATS scope. We do not migrate CoreHR employee data to Zoho Recruit Candidate records because Zoho Recruit is not an HRIS and does not hold compensation, benefits, or performance data on candidates. We flag this scope boundary explicitly and deliver a written inventory of CoreHR objects that require manual re-entry or a separate HRIS migration.

Arcoro time entries tied to job cost codes and pay periods have no Zoho Recruit equivalent. Zoho Recruit is an ATS and does not track time entries. We do not migrate time entry data. We flag this as a gap and recommend the customer maintains time tracking in Arcoro, the existing construction ERP, or a dedicated time-tracking tool if the migration proceeds.

Arcoro payroll history including earnings, deductions, and tax withholdings per pay period is out of scope for Zoho Recruit. Zoho Recruit has no payroll object. We do not migrate payroll records. We deliver a written inventory of payroll fields for the customer's HR admin to re-enter manually or migrate separately to a payroll platform.

Arcoro benefit enrollments (active plans, coverage levels, election dates) are outside Zoho Recruit's scope. We do not migrate benefit data. We flag plan names and coverage tiers in a written handoff document so the customer can re-enroll employees in their new HRIS or payroll platform post-migration.

Arcoro certification records with issue dates, expiration dates, and renewal alerts are mapped to Zoho Recruit Candidate custom fields. Each certification (OSHA 10, NCCER, apprenticeship completion) becomes a custom field on the Candidate with expiration date tracked via a Zoho Recruit workflow reminder or custom function. We preserve the original issue date and expiration date for audit. Construction-specific certifications that are relevant to the candidate's role are flagged as high-priority custom fields during scoping.

Arcoro CoreHR custom fields on employee records that also appear in the ATS module migrate to Zoho Recruit Candidate custom fields. We discover custom field names and data types via the Arcoro CoreHR export configuration and map them as equivalent custom fields in Zoho Recruit. Custom field types are preserved (text, number, date, picklist) with picklist values translated where Arcoro and Zoho Recruit use different value sets.

Arcoro job cost codes used for construction ERP integration do not map to Zoho Recruit. Zoho Recruit has no job cost structure. We do not migrate job cost codes. We flag unmapped codes in a written crosswalk document for the customer's ERP admin to re-enter manually in the destination accounting platform.