Migrate from Talos ATS to BambooHR

Talos ATS Candidates map directly to BambooHR Applicants. The Talos candidate record holds contact details, CV, application history, and stage progression. We preserve all standard fields (name, email, phone, address) and map the source candidate_id as a custom field talos_candidate_id__c for audit traceability. Custom fields discovered during the data audit phase map to BambooHR custom applicant fields by type (text, date, dropdown). Inactive or departed candidates are flagged for customer review before import.

Talos ATS Jobs map to BambooHR Jobs with title, description, location, department, and status preserved. Active and closed jobs migrate with their original posting URL stored in a custom field. BambooHR's job status values (Open, Draft, Closed, Filled) map from Talos status values during the transform phase. If the customer used Talos multi-brand job templates, we preserve the brand identifier as a custom field for reassignment in BambooHR.

Talos ATS Applications link a Candidate to a Job and track stage progression as a linear timeline. Each Application migrates as an Applicant record linked to the corresponding Job in BambooHR. The Talos application_date and most_recent_status_change_date migrate as BambooHR custom fields to preserve the original timeline. Stage history beyond the current stage is stored as notes entries in BambooHR since the native model tracks current stage only.

Talos ATS allows fully customisable stage names and counts per job or pipeline. BambooHR's ATS uses a standardised stage model with configurable labels and a capped number of stages per pipeline (varies by package). We extract the customer's stage labels and map them to BambooHR stage values, flagging where the Talos stage count exceeds BambooHR's limits. The customer chooses which stages to consolidate during scoping. Stage rules and automation triggers tied to stage transitions do not transfer and are documented separately for BambooHR workflow rebuild.

Talos ATS Interview records (date, interviewer, type, outcome notes) migrate to BambooHR Interview records linked to the Applicant. Interviewer name maps to the BambooHR Interviewer field. Talos video interview transcription and Tali AI interview insights do not migrate since BambooHR does not have a native AI interview analysis feature; these are flagged for the customer to review post-migration.

Free-text notes attached to Talos ATS Candidates and Applications migrate as Notes linked to the corresponding Applicant in BambooHR. The note author and timestamp preserve. Notes are imported after Applicants to satisfy the parent-record lookup. Structured scoring rubrics and assessment data from Talos custom fields map to BambooHR custom fields of equivalent type.

Talos ATS Offer records (compensation, start date, status) migrate as BambooHR Offer Letters. The e-Sign status from Talos (Docusign integration) does not carry to BambooHR because e-Sign records live in Docusign, not in Talos. We preserve the offer compensation and start date, and flag that the customer's admin should reissue e-Signed offer letters in BambooHR or re-sync with Docusign if maintaining the same signing service.

Talos ATS Users (recruiters and hiring managers assigned as owners on records) map to BambooHR Users. We match by email address during migration. Any Talos User without a matching BambooHR User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive or departed Talos users are flagged for reassignment of their owned records.

Talos ATS supports custom fields on Jobs and Candidates. We discover these during the data audit phase and map them to BambooHR custom fields of equivalent type (text, number, date, dropdown, checkbox). Unsupported field types (e.g., Talos-specific structured objects) are flagged and the customer chooses whether to drop or store them as text notes in BambooHR.

Talos ATS reporting configurations and saved dashboard views are platform-specific and do not export cleanly. BambooHR provides native Candidate Sources and Candidate Funnel reports. We do not migrate saved reports; instead, we deliver a written mapping of the key Talos metrics and filters that the customer's admin can recreate in BambooHR's reporting module using the migrated data.

Talos ATS e-Sign records (offer letters, contracts signed via Docusign) do not exist as extractable records in Talos. Docusign is an integrated add-on, not a native Talos object. We flag e-Sign usage during the audit phase and recommend the customer's admin re-initiates e-signature workflows from BambooHR for active or pending offers. Historical signed documents remain in Docusign and should be accessible there independently.

DBS Check records from Talos (via Credence integration) do not export as structured data through the Talos data package. We flag DBS check usage during the audit phase. If the customer requires DBS history to carry forward, they should request a data export directly from Credence DBS separately. BambooHR's background check integration (available on Pro and Elite) can be configured post-migration to run new checks through BambooHR's partner providers.