Migrate from HROffice to Crelate

HROffice Candidate records map directly to Crelate Contact. Name, email, phone, address, source channel, and current application status migrate as standard Contact fields. The HROffice candidate_id is preserved as an external reference field for audit and reconciliation. We resolve the HROffice application history to build a Crelate activity timeline showing the candidate's placement pipeline progression.

HROffice Applications tied to Job Postings map to Crelate Job Orders (representing the role) and as Activity records on the Contact timeline (representing the candidate's application event). Application status from HROffice maps to a Crelate custom picklist preserving the original stage name so recruiters can still read the pipeline progression. Application notes and recruiter comments migrate as Activity notes on the Contact.

HROffice Job Postings migrate to Crelate Job Orders with title, department, location, employment type, and description preserved. Posting date and expiration date migrate as Job Order metadata. HROffice's department and location metadata map to Crelate's category and region custom fields. Employer branding, custom career site styling, and job posting HTML templates do not migrate; we deliver a written job posting template specification for your admin to rebuild in Crelate.

HROffice Assignments represent temporary or temp-to-perm placements with start dates, end dates, assignment type, and weekly pay rate. This is a staffing-agency-specific concept with no direct Crelate equivalent. We export Assignments as supplemental records and attach them as a structured set of custom fields on the Contact record—assignment_type__c, assignment_start__c, assignment_end__c, assignment_rate__c, and assignment_status__c—so the placement history is preserved without creating duplicate or conflicting employment records. This is the critical design decision for this pair and we document it explicitly in the scoping deliverable.

HROffice weekly timecards include hours worked and submission dates per assignment. Crelate does not include a native timecard or payroll cycle module. We export timecard history as Crelate Activity records (with a custom timecard subtype) linked to the Contact, and hours data as a custom numeric field on each activity. This preserves the payroll context in a searchable, auditable form. We flag this as a configuration item during scoping because some customers prefer timecard history stored as a custom JSON or structured text field rather than individual activity records.

HROffice internal users (recruiters, administrators) map to Crelate User records by email match. Role-based permissions (recruiter, hiring manager, admin) map to Crelate's permission roles. We extract every distinct HROffice user referenced on Candidate, Application, or Assignment records. Any HROffice user without a matching Crelate User goes to a reconciliation queue for your admin to provision before the record import phase.

HROffice benefit enrollment records and plan assignments may exist for placed temporary workers. We export benefit plan name, enrollment date, and coverage type as custom fields on the Contact record. We do not attempt to create a separate Benefits object because Crelate does not include a native benefits management module; the benefit history travels as supplemental metadata on the candidate or placement record.

HROffice compensation records include pay type (hourly, salary), rate, and effective dates for temporary placements. Pay rate, pay frequency, and pay type migrate as custom fields on the Contact (for direct hires) or on the Assignment custom fields (for temporary placements). The mapping destination depends on whether the worker is still on assignment or has converted to direct hire at migration time.

HROffice custom candidate, application, and job posting fields require a discovery audit before migration. HROffice's limited public API documentation means we cannot programmatically enumerate custom fields in advance; we request read access to the HROffice data dictionary during scoping or extract a representative record set that includes all non-empty custom field values. We then reproduce the field structure in Crelate (text, number, picklist, date, or Boolean type matching Crelate's supported types), create the fields before migration, and apply the transform during the migration run.

HROffice's built-in career website builder, branded job posting templates, and employer branding assets (logos, color schemes, copy) do not have a Crelate equivalent that accepts automated content import. We do not migrate branded career site pages or employer content. We deliver a written content inventory listing every active HROffice job posting URL, branded page title, and key copy so your admin can reproduce them in Crelate's job distribution tools or a standalone career site CMS.

HROffice's built-in referral recruitment tool generates candidate records with a referral source indicator. Referral source metadata migrates to the Candidate Source field in Crelate. Active referral workflows and referral-specific routing rules do not migrate; we document the referral source values and recommend rebuilding any referral-specific routing in Crelate's workflow builder post-migration.

All HROffice records carry created_at and updated_at timestamps. We preserve these on every migrated Crelate record using the API's created_date and last_modified_date parameters. This is critical for audit trails, compliance reporting, and recruiter workflows that rely on time-of-action context. We do not overwrite timestamps with the migration run date.