Migrate from Factorial to Recruit CRM & ATS

Factorial employee records map to Recruit CRM candidate records. We map name, email, phone, address, and employee status fields to their candidate equivalents. The employment status (active, on leave, terminated) does not map directly — we preserve it in a custom field original_employment_status__c on the candidate record. Department reference resolves to the Recruit CRM candidate's assigned team or department field via the department lookup. Start date and termination date map to candidate registration_date and status_change_date fields where supported, or to custom date fields.

Factorial departments and cost centers export as flat or nested organizational units. We preserve the parent-child hierarchy and map to Recruit CRM department records as lookup values. Any employee department assignment references the department lookup in Recruit CRM. We validate that no orphaned department references exist after import by running a referential integrity check against the employee-to-department mapping table.

Factorial documents attached to employees (contracts, policies, onboarding forms, payslips) migrate as files attached to the corresponding Recruit CRM candidate record. Factorial does not expose a bulk document download API, so we paginate the document list via the API and download each file individually before uploading to Recruit CRM. We flag document-heavy migrations during scoping (over 5,000 files) and set expectations for transfer time accordingly. File type and original filename are preserved in the Recruit CRM document record.

Factorial employment contracts include contract type, working hours, probation period, and legal entity reference. Recruit CRM has no native contract object, so we extract contract metadata (type, start date, end date, hours per week, probation status) and store it as custom fields on the candidate record. Country-specific legally required fields that cannot map directly are flagged for manual review during reconciliation.

Factorial allows arbitrary custom fields on employee profiles with no schema discovery API. We enumerate all active custom fields by querying the employee and contract endpoints during scoping discovery. Each custom field maps to a Recruit CRM candidate custom field of the matching type (text, number, date, picklist, or checkbox). Custom fields that have no Recruit CRM equivalent are flagged as unmapped and included in the handoff document for admin review.

Factorial absence records track balance, accrual rules, and approved leave per employee. Recruit CRM has no absence management module and no equivalent object for leave balances or accrual tracking. We do not migrate absence records. We export the absence data as a structured CSV inventory (employee, absence type, balance at migration date, accrual rule) and deliver it alongside the migration for the customer's HR admin to archive or import into a standalone HRIS if required.

Factorial time entries store clock-in/out timestamps, timesheets, and project or cost-center tags per employee. Recruit CRM has no time-tracking object and does not record employee work hours. We do not migrate time entries. We export a chronological CSV of historical time data (employee, date, hours, project tag, cost center) as a separate data artifact for payroll or billing reference if needed.

Factorial payroll runs are tied to country legal entity configurations and include gross salary, deductions, supplements, and net pay. Recruit CRM has no payroll module. We do not migrate payroll records. We export payroll data as structured CSV files (employee, pay period, gross, deductions, net, currency) for the customer's finance team or external payroll processor to recompute against local tax rules in the destination system.

Factorial compensation history tracks effective-dated salary changes, bonuses, and equity grants per employee. Recruit CRM has no native compensation history object, but we can store current compensation data (most recent salary, currency, bonus target) as custom fields on the candidate record if the agency uses this for internal placements or基准 salary tracking. Full historical compensation timelines export as CSV for reference.

Factorial approval chains for time-off, expenses, and document workflows are stored as platform-specific automation objects. These have no export representation and no Recruit CRM equivalent because Recruit CRM's automation model (AI agents, workflow triggers, Kanban actions) is architecturally different. We document the existing workflow structure during discovery and deliver it as a written inventory so the customer's admin can rebuild equivalent automations in Recruit CRM's no-code workflow builder post-migration.