Migrate from Talexio to Recruit CRM & ATS

Talexio People profiles migrate to Recruit CRM Contacts. We extract name, email, phone, address, department, job title, and employment status. Talexio's single employee profile may contain both HR and recruiting context; we separate these into Contact fields and, where employment data exceeds Recruit CRM's standard Contact fields, into custom fields on the Contact record. Active status, start date, and manager references migrate as custom fields since Recruit CRM Contacts do not have a native employment date schema.

Talexio's candidate records in the ATS module map directly to Recruit CRM Candidate records. We extract name, email, phone, current title, current company, LinkedIn URL, source channel, pipeline stage, and any recruiter assignment. Custom Talexio candidate fields require enumeration during discovery and are mapped to Recruit CRM custom candidate fields created before import. Pipeline stage names from Talexio do not auto-map to Recruit CRM stages; we document the stage mapping as a configuration step.

Talexio job postings migrate to Recruit CRM Job records. We extract job title, description, location, employment type, department, salary range, and status (open/closed/hired). Talexio job IDs are preserved in a custom field on the Recruit CRM Job record for reconciliation. Published date and closing date migrate to Recruit CRM's job date fields.

Talexio Employment Position records (each representing a role or salary change against a People profile) have no direct Recruit CRM object. We decompose each position into its component fields—title, salary, effective date, employment type, cost centre—and store them as structured entries in a custom Talexio_positions__c custom field on the Candidate or Contact record as a multi-line text or JSON blob. We flag during scoping whether the customer requires this level of employment history preservation or a simpler current-position snapshot.

Talexio leave records (leave type, balance used, approval status, effective dates) are extracted but have no native Recruit CRM equivalent since Recruit CRM is an ATS, not an HRMS. We store leave balance data as custom fields on the Contact record (leave_type__c, balance_used__c, effective_date__c) or as a note attached to the Contact, depending on volume. We do not migrate leave entitlements as a managed object.

Talexio clocking records (employee reference, date, clock-in/out timestamps) are extracted from the reporting database. Because Recruit CRM has no time tracking module, we attach a structured time log summary as a Note or as date-stamped custom fields on the Contact record. Historical clocking data exceeding 12 months is flagged during scoping for exclusion or archival since it has limited recruiting value in Recruit CRM.

Talexio companies linked to candidate records in the ATS module migrate to Recruit CRM Company records. We extract company name, website, industry, size, and address. Company name is used as the dedupe key. Company records are created before Candidate import so that the Company lookup is satisfied at the point of Candidate insert.

Talexio organisational units (departments, cost centres) are exported as reference data. We create corresponding values in Recruit CRM as custom picklist fields on Candidate, Contact, or Job depending on where the department context is most relevant. If the customer uses departments as placement categories, we map them to Recruit CRM Job departments or hotlist tags.

Talexio Onboarding Assistant document packages and step completion status are not native Recruit CRM objects. We migrate onboarding step names and completion status as custom fields on the Candidate record (onboarding_step_1__c, completion_status__c) and attach any onboarding documents as Notes or Files linked to the Contact. We flag that document attachments require separate export from Talexio's document store if they are stored as binary files rather than text records.

Talexio custom profile fields are enumerated during discovery (requiring Talexio view permissions on the account). Each custom field is mapped to a Recruit CRM custom field of the matching type (text, number, date, picklist, checkbox). Recruit CRM's custom field creation via Admin Settings must precede the bulk import. We document the full custom field inventory in the migration scope for the customer's admin to review before we create destination fields.

Talexio documents attached to People profiles or candidate records are exported from the reporting database or directly from the UI. We link documents to the corresponding Recruit CRM Candidate or Contact record as Files. Document naming conventions from Talexio are preserved in the file name so that the admin can audit attachment history post-migration. Binary file attachments require a separate export step from Talexio's document store.

Talexio skill and training tracking exists as profile fields rather than a separate object. Skills migrate as multi-select or comma-separated custom fields on the Recruit CRM Candidate record. If the customer uses skills as searchable criteria in Recruit CRM, we recommend configuring them as picklist-based custom fields with a controlled vocabulary to maintain search consistency.