Migrate your Talexio data

Employee profiles are the core record in Talexio, displayed in the People section. Each profile can hold contact details, employment history, and permissions. We migrate profile fields 1:1 and preserve the profile's unique ID for cross-referencing with related objects like Employment Positions and leave records.

Talexio links an employee to one profile; role changes and salary adjustments are recorded as new Employment Position entries against that profile. We preserve the position history and effective dates, mapping each position to the destination system's job-title or compensation record.

Clockings sync automatically from physical devices to Talexio's software. We export these as time log records with employee reference, date, and clock-in/out timestamps. The reporting database schema for time data is available on request from Talexio support.

Approved leave booked in Talexio is migratable. We extract leave type, balance used, approval status, and effective dates. Leave entitlements are stored per-employee and must be reconciled separately from usage records.

Talexio operates as an ATS. Candidate profiles, applications, and pipeline stages exist in the system. We map these to the destination ATS objects, but pipeline stage names and custom recruiter fields vary by customer configuration and may require field-level mapping.

The Onboarding Assistant supports bulk employee upload. Onboarding document packages and step completion status are migratable but the document attachments themselves may need to be exported separately via Talexio's file store or USB export.

Offboarding data including exit checklists and document sign-offs are tied to the employee profile. We extract the record and associate it with the employee's final Employment Position. Whether the destination system supports offboarding workflows determines whether this lands as structured data or a note.

Talexio stores documents against employee profiles and recruitment records. Documents can be exported via the reporting database or directly from the UI. We flag which documents are attached to which object to ensure they land in the correct destination record.

Training modules and skill tracking exist as employee profile fields. These are not a separate object in Talexio and are migrated as custom profile fields. Mapping to a dedicated LMS requires field-level alignment.

Custom fields can be created on employee profiles and require specific permissions to view or manage. We enumerate all custom fields during discovery and map each to the corresponding destination field, flagging any with conditional logic that may not transfer cleanly.

Organisational structure including departments and cost centres is supported as standard configuration data in Talexio. We export these as reference data and recreate them in the destination before importing employee records.