Migrate from HROffice to Recruit CRM & ATS

HROffice Candidate records map directly to Recruit CRM Candidate. We export standard fields including name, email, phone, address, skills, experience, and application history. The mapping is straightforward for fields that exist in both systems; custom fields on Candidate may require prioritization if the customer's Recruit CRM plan is Team tier (15-field limit per entity) versus Business tier (50 fields). We flag any HROffice custom candidate fields exceeding the destination tier limit during scoping and work with the customer to prioritize or restructure.

HROffice Applications tied to open Job Postings map to Recruit CRM Applications. Each Application carries the candidate reference, job reference, application date, status pipeline, and recruiter notes. Status values from HROffice's application pipeline map to Recruit CRM's candidate pipeline stages, with the mapping defined during scoping based on the customer's specific stage names.

HROffice Job Postings map to Recruit CRM Jobs. Job content including title, description, requirements, location, department, and employment type migrate directly. Employer branding, custom career site fields, and embedded media tied to HROffice's career site builder do not carry over; these are platform-specific assets that require recreation in Recruit CRM's job posting interface.

HROffice Assignment records represent temporary or temp-to-perm placements with start dates, end dates, assignment type, and placement status. This is a staffing-agency-specific concept without a direct Recruit CRM equivalent. We export Assignments as supplemental metadata and attach them to the migrated Candidate record as custom fields (assignment_type, assignment_start_date, assignment_end_date, placement_status) or as structured notes. This preserves the staffing history without forcing placement records into a standard employment model that Recruit CRM does not support.

HROffice timecard records capture hours worked and submission dates for temporary workers on assignment. Recruit CRM has no native timecard object. We export timecard history as a structured note on the related Candidate record or as custom fields (weekly_hours, timecard_submission_date, pay_period) if the customer's data volume and Recruit CRM tier support it. Recruit CRM's invoice management feature can handle billing for placed candidates but does not replace payroll cycle tracking.

HROffice internal Users (recruiters, administrators) are separate from the candidates placed through the platform. User records carry role-based permissions and name/email. We export active User accounts for reconciliation against Recruit CRM User provisioning. Inactive HROffice users are exported as a reference list for the customer's admin to provision or archive in Recruit CRM after migration.

HROffice benefit enrollment records include plan assignments, coverage type, and effective dates for placed workers. These map to custom fields on the Candidate record in Recruit CRM if the destination tier supports the field count. We export benefit data as structured key-value fields or as a supplemental notes section on the candidate, depending on the volume and Recruit CRM plan constraints.

HROffice compensation records include pay type (hourly, salary), rate, currency, and effective dates for temporary placements. These map to custom fields on the Candidate record in Recruit CRM (pay_type, hourly_rate, salary, currency, compensation_effective_date). We standardize currency values to the primary currency used in the Recruit CRM instance during the transform step.

HROffice Company records (client organizations that post jobs or receive placements) map to Recruit CRM Client records. Company name, address, industry, contact information, and notes migrate directly. The mapping uses company name as the dedupe key during import to prevent duplicate client records.

HROffice Contact records (hiring manager or client-side contact individuals) map to Recruit CRM Contact records attached to Client organizations. Name, title, email, phone, and relationship to the client organization migrate directly. We resolve the parent Client reference during migration so that contacts are properly linked at import time.

Archived or closed HROffice Job Postings migrate to Recruit CRM Jobs with a closed status flag. The customer's Recruit CRM plan determines whether archived jobs count against the active job posting limit. We flag any archive strategy during scoping and advise whether to migrate all historical postings or only recent ones.

HROffice candidate documents (resumes, CVs, attachments) migrate as linked documents to the corresponding Candidate record in Recruit CRM. We handle document extraction from HROffice's storage, validate file format compatibility, and attach each document to the correct Candidate using the candidate ID mapping established during the primary record migration.