Migrate from The Applicant Manager to BambooHR

TAM Positions (job title, description, department, status) map directly to BambooHR Job Openings. The TAM position status (active, closed, on hold) maps to BambooHR's Job Opening status field. We extract all active and closed positions from the TAM CSV during the initial export, preserving the original posting date and any department classification. BambooHR requires Job Openings to be created before Applicants can be attached, so positions load first in the dependency sequence.

TAM Applicant records (contact information, application date, source attribution, current workflow stage) map to BambooHR Candidate records attached to the corresponding Job Opening. We map the TAM applicant ID as a reference field and preserve the application date as the candidate's submission timestamp. Custom profile fields from TAM map to BambooHR's custom candidate fields. If the candidate email matches an existing BambooHR Employee record, we link the Candidate to the Employee for onboarding continuity.

TAM's customizable workflow stages have no standard naming vocabulary—every TAM tenant defines its own stage names and sequence. We collect the complete TAM workflow configuration during discovery, then configure the BambooHR Hiring pipeline with matching stage names in the same order. The stage order is preserved so candidate progress reflects correctly after cutover. If TAM had five stages (Applied, Phone Screen, Interview, Offer, Hired), BambooHR gets five matching pipeline stages.

TAM stores applicant files in a separate password-protected zip archive, not embedded in the CSV export. We download and unpack both the CSV and the file archive, then cross-reference each file by applicant ID or filename pattern to re-associate it with the correct BambooHR Candidate record. Resume and cover letter files upload as attachments to the candidate profile in BambooHR Hiring. This two-step extraction is the most manual part of the migration and adds processing time for large file volumes.

TAM supports custom application questions stored in the position configuration, with responses per applicant. We extract both the question schema (question text, answer type, required flag) and the applicant responses. Questions migrate as Custom Application Questions in BambooHR; responses attach to the corresponding Candidate record. Formatting of free-text responses is preserved; multi-select or dropdown responses map to BambooHR's equivalent answer type.

Hiring team notes, scorecard ratings, and stage-change timestamps tracked per TAM applicant migrate as Activity History entries in BambooHR. We preserve the author (hiring manager or recruiter), timestamp, and content. Scorecard ratings with structured attributes migrate as formatted text notes. Formatting varies depending on how the destination BambooHR account renders activity history, and the customer's ATS package tier affects how rich the activity display is.

TAM includes onboarding paperwork collection with document metadata and storage references. Document metadata migrates to BambooHR Onboarding, but the destination system's onboarding module acceptance determines whether forms are fully functional post-migration. BambooHR's onboarding is tied to the BambooHR Employee record, so the candidate must have been converted to an Employee (or have a matching Employee record) for onboarding tasks to attach. We flag any forms that require manual reconfiguration in BambooHR Onboarding.

TAM user accounts tied to applicant assignments and workflow actions map to BambooHR Employee records. We match by email address and preserve assignment ownership so that the hiring manager responsible for each TAM applicant is linked to the corresponding BambooHR Candidate. TAM users without matching BambooHR Employee records go to a reconciliation queue for the customer's admin to provision before the migration batch completes.

TAM positions carry a department classification. We extract department names from the TAM CSV and map them to existing BambooHR Department records, or flag missing departments for the customer to create before position migration. Department assignment on Job Openings in BambooHR references the HRIS department list, so this lookup must be satisfied at migration time.

TAM tracks applicant source (Indeed, LinkedIn, Referral, etc.) in the applicant record. Source attribution migrates as the Candidate Source field in BambooHR Hiring. We map the TAM source label directly, with a reconciliation pass if the customer's BambooHR account uses a different source vocabulary. Source data is preserved for reporting on hiring channel effectiveness.