Migrate from Factorial to Crelate

Factorial Employees map to Crelate Candidates. We extract the primary employee record (name, contact, start date, department, employment status) and map it to the Candidate profile. Crelate's Candidate object does not have native fields for salary, manager hierarchy, or employment type beyond what is captured in the work history section. We flag any salary or compensation data stored on the employee profile as requiring a custom field or manual documentation post-migration.

Factorial Departments and Cost Centers map to Crelate Organizations or Teams depending on whether the Crelate instance uses the Organization hierarchy or the Team tagging feature. We preserve parent-child department relationships and validate no orphaned departments remain after import. If the customer uses Factorial's cost center tagging for billing or project allocation, we map cost center codes to a custom field on the Candidate or Job record.

Factorial Documents attached to Employees (contracts, ID files, certifications, offer letters) migrate as Crelate Candidate Attachments. Factorial does not expose a bulk document export endpoint, so we paginate the document list via the API and download each file individually. Large document archives (over 5,000 files) add significant time to the migration window and are flagged during scoping so the customer can decide whether to migrate the full archive or a recent window.

Factorial allows arbitrary custom fields on Employee records but exposes no schema or metadata endpoint. We discover all active custom fields by calling the Employee and Contract API endpoints during scoping, then map each to a Crelate Candidate custom field of equivalent type. Custom fields with no Crelate equivalent are flagged for the customer to create in Crelate Settings before migration begins. This discovery step is required on every Factorial migration because per-customer field sets vary.

Factorial Employment Contracts (contract type, working hours, probation period, legal entity reference) do not have a direct Crelate ATS equivalent. We extract the key fields and populate them as structured entries in the Candidate's Work History section or as custom fields if the customer has configured them. Country-specific legally required fields are noted in the migration deliverable for the customer's HR admin to verify against local compliance requirements.

Factorial Payroll Runs are country-locked to the legal entity and contain salary, deductions, supplements, overtime, and net-pay calculations tied to Factorial's payroll engine. Crelate has no payroll module and no fields for gross salary, tax withholding, social security contributions, or net pay. We do not migrate payroll runs. We export payroll data as a structured CSV for the customer's finance team to use when setting up payroll in their chosen payroll processor.

Factorial Compensation History (effective-dated salary changes, bonuses, equity grants, benefits) has no Crelate equivalent. Crelate's Candidate and Placement records do not include salary history fields. We extract the compensation timeline as a structured export for the customer's HR admin to document in their new HRMS or compensation management tool. If the customer uses Crelate Placements, we map the billing rate or fee to the Placement record as a custom field.

Factorial Absence records (types, balances, accrual rules, and accrual balances at migration time) do not migrate to Crelate. Crelate has no absence management module; it tracks candidate availability for interviews but not time-off balances or accruals. We deliver a written inventory of active absence types and current balances so the customer's HR admin can configure equivalent accrual rules in their new HRMS or payroll system.

Factorial Time Entries (clock-in/out records, timesheets, project tags, cost-center tags) do not migrate to Crelate. Crelate has no time tracking module. For staffing firms using Factorial for contractor time tracking, we recommend migrating the current open timesheet period as a CSV for manual entry into a dedicated time-tracking tool or for import into the customer's new payroll processor.

Factorial approval chains for time-off, expenses, and documents are stored as platform-specific automation objects with no export representation. Crelate's workflow model is different and not compatible. We document the Factorial workflow structure during discovery so the customer's admin can rebuild equivalent approvals in Crelate or in a dedicated workflow tool. This documentation is delivered as part of the standard migration package.

Employee profile photos in Factorial migrate as Candidate photos in Crelate. We extract the photo from the Employee API response and upload it to the corresponding Candidate record. If the photo is stored as a separate document attachment rather than an embedded profile field, we migrate it as a Candidate Attachment.

If the customer uses Factorial's hiring or recruitment module to track open positions, those Job records map to Crelate Job records with position title, department, and status preserved. Factorial's hiring pipeline stages map to Crelate's Job stage values. We flag any custom pipeline stages that require configuration in Crelate before the position data migrates.