Migrate from Talos ATS to Crelate

Talos ATS Candidates map directly to Crelate Person records. We preserve all contact details (name, email, phone, address), CV attachment, application history, and stage progression timeline. The Talos candidate_id becomes a custom field crelate_import_id__c for reconciliation. Any Talos candidate records with missing email addresses are flagged in the audit phase and held in a review queue because Crelate relies on email as the primary deduplication key.

Talos Job records map to Crelate Job with title, description, location, department, and status preserved. Active and closed jobs migrate. The Talos job posting URL is stored as a custom field for reference. Talos custom fields on Jobs (e.g. hiring manager, approval status, internal/external flag) map to Crelate Job custom fields, with field type validation applied because Crelate enforces picklist and date formats that Talos does not.

Talos Applications link a Candidate to a Job and track stage progression. We migrate the application record with its current stage, stage history as a chronological note block, and submission timestamp. The link between Application and Candidate is resolved at migration time by matching the Talos candidate_id stored on the Application record against the imported Person records.

Talos allows fully custom stage names and counts per job or pipeline, which can range from 3 to 15+ stages. Crelate uses a pipeline-stage model with configurable stages per pipeline. We extract the customer's actual stage labels, map them to Crelate pipeline stages (creating new Crelate stages if the count exceeds the default), and flag any stage with automation triggers for manual rebuild. Stage count mismatches above 10 stages require customer input on consolidation strategy.

Talos Interview records (date, interviewer, type, outcome notes, video transcription where available) migrate to Crelate Interview records linked to the Person and Job Application. Talos video transcription is stored as a note attachment because Crelate does not currently support video transcription import. Interviewer assignment resolves by matching the Talos interviewer email against the imported User list.

Free-text Notes attached to Candidates, Applications, and Jobs migrate as Crelate Notes linked to the corresponding Person, Job Application, or Job record. Notes inherit the Talos owner attribution and timestamp. Rich text formatting in Talos Notes is preserved as HTML-formatted text in Crelate Notes.

Talos Offer records (compensation, start date, status, terms) map to Crelate Offer records linked to the Job Application. We flag any Offer records that have an associated Docusign e-Sign status in Talos, because the e-Sign integration status does not export as structured data and the signed document must be retrieved separately from Docusign's own export tools.

Talos supports custom fields on Job records. We discover all custom field definitions during the data audit, validate field types (text, number, date, picklist, checkbox), and create equivalent custom fields in Crelate Job before migration. Picklist custom fields require value mapping if Talos picklist values differ from Crelate's existing picklist options.

Talos custom fields on Candidate records map to Crelate Person custom fields. Talos supports flexible field types that may include multi-select picklists, large text areas, and linked record references. Crelate enforces stricter field type validation. We flag any Talos field type that cannot be mapped directly (e.g. linked record references become text fields with a warning note). Talos Assess fields (structured scoring rubrics) require field-level mapping to Crelate's assessment format.

Talos Users assigned as record owners (recruiters, hiring managers) map to Crelate Users resolved by email match. Inactive or departed Talos users are flagged and held for reassignment. Crelate requires all Owner references to resolve to an active User at the time of record import, so any missing Crelate Users must be provisioned before the migration phases that include OwnerId references.

The Talos Tali AI agent applies tags to candidates and jobs based on its hiring analysis. These tags are stored as a tagging taxonomy in Talos but do not export as structured key-value pairs. We extract the tag data as text strings and store them in a Crelate custom text field (tag_list__c) on the Person record. The customer's admin reviews and re-establishes tagging taxonomy post-migration because Crelate's AI tools use a different tagging model.

Talos multi-brand and franchise configurations aggregate hiring metrics across locations under a single instance. Crelate does not have an equivalent franchise multi-brand model. We extract each franchise or location's candidate, job, and stage data and tag each record with a franchise_location__c tag. Pipeline consolidation decisions are made during scoping: customers can maintain separate Crelate pipelines per location or consolidate into one pipeline with the location tag for filtering.

Talos DBS Check records (via Credence integration) contain status, type (basic to enhanced), and result data. These records are stored in Talos but export depends on whether the add-on module was active and whether Credence DBS data is included in the Talos export package. We scope DBS usage during the audit phase and flag whether a separate pull from Credence DBS is required. DBS results migrate as a linked record on the Person with status and type fields preserved.

Talos e-Sign records (Docusign integration) track offer letters and contracts with signing status. The Docusign envelope status does not export from Talos as a structured record. We migrate the associated Offer record with a note indicating e-Sign status must be verified in Docusign's own envelope export. The signed PDF may be retrievable from Docusify directly as a separate data pull.

Talos Reference Checking records (candidate and client portal) contain reference contact details, status, and responses. If the Reference Checking add-on was active, these records export as structured data from Talos. We migrate them as Reference records linked to the Person, preserving the reference contact and status. Full response content migrates as a note attachment.

Talos ATS reporting configurations and saved dashboard views are platform-specific and do not export in a usable format. We do not migrate them. We deliver a written map of the top 10 Talos reports with their filters, groupings, and data sources so the customer's admin can rebuild equivalents in Crelate's native reporting module. Crelate reporting is included at all tiers.