Migrate from Employment Hero to Crelate

Employment Hero employee profiles migrate to Crelate Person records. We extract first name, last name, email, phone, employment status, start date, employing entity, cost centre, and location fields. The employing entity and cost-centre assignments are stored as custom fields on the Person record in Crelate because Crelate's standard fields are candidate-recruitment focused. Any employees without email addresses are flagged for manual review before import — candidate records without contact information are not actionable in an ATS.

Employment Hero's SmartMatch candidate profiles (from the recruitment module) map directly to Crelate Person records with the full candidate profile preserved: work experience, education, skills, and screening responses. Application status from SmartMatch migrates as a custom status field on the Person rather than a native Crelate pipeline stage because Crelate tracks stage on Job Orders, not on candidate profiles independently.

Employment Hero job postings from the recruitment module map to Crelate Job Order records. The job title, description, location, employment type, and department fields migrate directly. Compensation details migrate as a custom compensation field on the Job Order if present in Employment Hero. Any job board integrations (LinkedIn, Indeed, Seek) do not migrate; we document the integration configuration for the customer's admin to re-establish in Crelate's job distribution settings.

Applications submitted through Employment Hero's SmartMatch recruitment module migrate as activity entries on the Crelate Job Order tied to the corresponding Person record. Application date, submission source (job board, direct, referral), and current stage migrate as custom fields. Historical stage transitions are preserved as a timestamped activity log entry rather than a native pipeline stage because Crelate manages stage at the Job Order level, not per candidate submission.

Employment contracts, compliance documents, and onboarding files exported from Employment Hero migrate as file attachments linked to the corresponding Person record in Crelate. We preserve the original file name and document type label. Any documents without an associated Person record are held in a document queue for manual candidate-to-file linking before the migration is finalised.

Custom fields created in Employment Hero's organisation schema do not exist in Crelate until explicitly defined. We retrieve the custom field schema via GET /api/v1/organisations/:id/custom_fields before migration, then pre-create equivalent custom fields in Crelate settings (as text, number, date, picklist, or checkbox per the source type) before any data import. Fields without a direct Crelate type equivalent are escalated for the customer's HR team to decide mapping during scoping.

Employment Hero cost-centre hierarchy (departments and cost-attribution units) migrates as a custom picklist field on Crelate Person and Job Order records. We preserve the full cost-centre name and ID for reconciliation. Cost-centre data is used to attribute candidate sourcing and placement activity to business units in downstream reporting.

Employment Hero teams (Groups in the current UI; 'teams' retained in API endpoint names) map to Crelate Teams. Team membership assignments migrate with each Person record. We use the API field team_id or group_id from the source schema to create the equivalent Crelate team and assign members at migration time.

Pay run history, leave balances, superannuation details, and award classification metadata are HR and payroll records that have no equivalent in Crelate's ATS data model. These records are outside the migration scope and are flagged for the customer's HR team to retain in Employment Hero (if the payroll module is kept) or export manually as CSV for compliance archive. We do not migrate payroll data to Crelate.

Employment Hero onboarding workflows include document collection, task checklists, and compliance steps tied to new hires. Crelate does not replicate this workflow model natively. We map active onboarding tasks and flag any custom template steps that require rebuild. We deliver a written inventory of every active onboarding workflow with its trigger, steps, and owner assignment for the customer's admin to configure in Crelate or a separate onboarding tool.

Employment Hero SmartMatch recruitment automation sequences and candidate-matching rules do not migrate as code to Crelate's workflow builder. These are distinct automation models with different trigger conditions, action types, and sequence cadence features. We deliver a written map of every active automation with its trigger, sequence steps, and recommended Crelate workflow or task automation equivalent for the customer's recruiting team to rebuild.

Benefit plans and employee benefit enrollments are plan-gated HR records in Employment Hero. Crelate is an ATS without benefits administration capability. Active benefit enrollments are flagged for the customer's HR team to retain in a separate HR system or export as a CSV for manual reference. We do not migrate benefits data to Crelate.