Migrate from Talexio to Crelate

Talexio People profiles map directly to Crelate Contacts. Each Talexio profile holds name, contact details, national ID, and employment metadata. We map Talexio firstname, lastname, email, phone, and address fields to Crelate's standard Contact fields. National ID and emergency contact details migrate as custom fields on the Contact record. Active employee status maps from Talexio's Employment Position effective dates; terminated employees map with a custom status field and the offboarding date preserved.

Talexio Employment Positions are time-varying: each role change, salary adjustment, or title change creates a new Position entry against a People profile. Crelate Contact has no native position-history object. We decompose the position history into a flat set of Crelate custom fields: current_job_title__c, current_department__c, current_salary__c, current_start_date__c, and employment_type__c. For customers who need full history, we create additional Crelate custom objects (Position_History__c) with lookup to Contact, ordered by effective_date__c. This approach handles multiple concurrent positions (common in Malta part-time contracts) by treating each as a separate history entry.

Talexio clockings migrate to Crelate Activity records of type Time Log. Each activity captures the Talexio employee reference, date, clock-in timestamp, clock-out timestamp, and work code. We export from Talexio via the reporting database schema (requested via support ticket per Talexio's process) and load into Crelate via the Activity API with the contact_id__c lookup resolved before insert. Physical device exports (USB) that have not been synced to Talexio are reconciled during the data audit phase to avoid missing historical records.

Approved leave booked in Talexio migrates as Crelate Activity records with a custom leave_type__c field and leave_balance__c capturing the used entitlement. Approval status, request date, and effective dates transfer as activity date and custom field values. Leave entitlements per employee are stored as Talexio annual entitlement values and migrate as a custom field leave_entitlement_total__c on the Contact. Leave type picklist values (annual, sick, parental) map to Crelate custom picklist options configured during schema setup.

Talexio candidates (from the ATS module) map to Crelate Contacts using the candidate's contact fields. Talexio vacancy applications map to Crelate Opportunity records linked to the Contact via the candidate_id__c custom field. Talexio pipeline stage names (Applied, Screening, Interview, Offer, Hired) map to Crelate Opportunity stage values configured during Crelate setup. Custom recruiter fields on Talexio candidates migrate as Crelate Contact custom fields. Talexio's linked HR account candidate-to-employee promotion is a separate workflow that the customer's admin handles post-migration.

Talexio vacancy records map to Crelate Opportunity records representing open job orders. Vacancy title, department, location, and salary range become Opportunity name, custom department and location fields, and a compensation custom field. Vacancy status (Open, On Hold, Closed) maps to Crelate Opportunity status. Active vacancies migrate as open Opportunities; closed vacancies migrate as Closed Won or Closed Lost based on Talexio's fill outcome.

Talexio organisational structure (departments and cost centres) exports as reference data and is recreated in Crelate as Organisations (Companies) representing departments, with a custom org_type__c = 'Department' to distinguish from client Organisations. Cost Centre codes migrate as a custom field on the Contact record (cost_centre__c). Department hierarchy (reporting lines) is preserved in a custom parent_department__c lookup if the customer maintains a hierarchical org chart in Talexio.

Talexio custom fields on People profiles migrate as Crelate Contact custom fields. Talexio's Contains Sensitive Data flag is preserved as a Crelate custom field sensitivity_flag__c (checkbox). We enumerate all custom fields during discovery, verify permissions on each via the Graph API, and map type (text, number, date, picklist) to the equivalent Crelate custom field type. Custom fields scoped to a specific country (a Talexio position-level feature) map to a Crelate custom field with country-specific visibility handled post-migration by the admin.

Talexio stores documents against employee profiles and recruitment records. We export document metadata (filename, document type, upload date, attached entity) from Talexio's reporting database. The documents themselves are downloaded and attached to the corresponding Crelate Contact or Opportunity record as Files. Document types (contract, ID copy, certificate, CV) map to Crelate file category tags. Any document exceeding the Crelate Business plan storage limit is flagged during scoping.

Talexio Onboarding Assistant step completion status migrates as Crelate Activity records representing onboarding tasks, with a custom onboarding_package__c field linking to the package name and a status__c field showing step completion. Onboarding documents (contracts, tax forms, policy acknowledgements) migrate as Crelate Files attached to the Contact. The onboarding package itself (the template and step sequence) is not migratable as a Crelate onboarding workflow; we document the package structure and required steps for the customer's admin to rebuild in Crelate.

Talexio offboarding data (exit date, exit interview notes, document sign-offs) migrates as a final Crelate Activity record on the Contact timeline with type = 'Offboarding' and a custom exit_date__c field. Offboarding checklist completion status migrates as custom fields on the Contact record. The Contact remains in Crelate with a custom employment_status__c = 'Terminated' and the termination_date__c field populated.

Talexio training modules and skill tracking exist as profile fields rather than a dedicated object. We extract skill names, certification names, and training completion dates and map them as Crelate Contact custom fields (skill_list__c as a multi-select picklist, certification_name__c and certification_expiry__c as date fields). Customers with dedicated LMS integrations in Talexio are flagged during scoping; the LMS connection is not migratable and requires reconfiguration post-migration.