Migrate from CATS to BambooHR

CATS Candidate records split into two BambooHR objects: the applicant record (for candidates still in the hiring pipeline) and the Employee record (for candidates who reached Hired status). We extract hire_date from the CATS candidate status change timestamp and use it as the BambooHR Employee hire_date field. Contact information (name, email, phone, address) migrates directly. Source attribution, tags, and custom fields transfer as applicant metadata. Candidates with Rejected status are preserved as archived Applicants with disposition notes from CATS' last pipeline stage.

CATS Job Orders map directly to BambooHR Jobs. The CATS job title, description, department, and location fields align with BambooHR Job fields. We map CATS pipeline stages to BambooHR job Status values (Open, Closed, On Hold, Draft). If CATS has multiple job pipelines, we use the CATS pipeline name as a BambooHR Job custom field rather than creating multiple job boards, since BambooHR uses a single job listing structure per department.

CATS pipeline stages (New, Screening, Interview, Offer, Hired, Rejected, and any custom stages) map to BambooHR job Status values. Each CATS stage gets a status assignment during migration. If BambooHR's default status set does not include a CATS stage name, we document it as a custom status requirement for the customer's admin to add in BambooHR settings before the job import runs.

CATS Activities linked to Candidates migrate to BambooHR Application Notes. Interview events with timestamps, interviewer names, and ratings migrate as Application Event records if BambooHR's ATS module supports them, or as structured Application Notes with a type flag. Activity timestamps preserve the original CATS creation date. Owner attribution migrates by resolving the CATS user email to the BambooHR Employee record of the recruiter or hiring manager.

CATS custom fields on Candidates and Job Orders migrate to BambooHR custom fields on the corresponding object. Text, number, date, and dropdown field types map directly. Checkbox fields map to BambooHR's Yes/No field type. Multi-select dropdown in CATS maps to a text field in BambooHR with comma-separated values unless a multi-select configuration exists in the destination. We export the full custom field schema from CATS during discovery and create the matching fields in BambooHR before importing any data.

CATS user accounts (name, email, role, department) map to BambooHR Employee records for active recruiters. We use email as the dedupe key. Inactive CATS users who have no applicant or activity attribution migrate as inactive BambooHR Employees or are excluded based on scope during discovery. Owner IDs on Candidate and Job Order records are resolved to Employee IDs in BambooHR during the import phase.

CATS Departments export as a flat list and map directly to BambooHR Departments. Department is a required reference for Job Orders in CATS, so we import Departments before Jobs to satisfy the foreign key. If CATS has nested department structures, we flatten them into BambooHR's single-level department model and add a parent_department custom field if hierarchical context is required.

CATS free-text and pre-defined tags on Candidates migrate as Tags on the corresponding BambooHR Applicant. Tags export as comma-separated values from CATS and split into individual Tag records in BambooHR. If the customer's recruiting team uses tags for source tracking (LinkedIn, Referral, Job Board), we map them to BambooHR's Applicant Source field instead and preserve the original tag string in a custom field for audit.

CATS file attachments on Candidates migrate as Employee Files in BambooHR. We pull the file binary via CATS export or API, preserve the original filename and MIME type, and upload to BambooHR linked to the corresponding Applicant or Employee record. Resume files map to BambooHR's designated resume field where available, or to a custom file field. Multiple attachments per candidate migrate as separate file records.

CATS Candidate Source field (LinkedIn, Referral, Job Board, etc.) maps directly to BambooHR's Applicant Source field on the Job Application. If CATS uses a source taxonomy that does not match BambooHR's built-in options, we document the mismatch and either map to the closest BambooHR default or add the source value as a custom field on the Application object.