Migrate from The Applicant Manager to Bullhorn ATS & CRM

TAM Positions (job title, description, department, status) map directly to Bullhorn JobOrder. TAM's position-level custom application questions migrate as Bullhorn JobOrder custom fields or as Custom Objects if the Bullhorn edition supports them. We preserve position status (active, closed, on hold) so that the Bullhorn JobOrder reflects the original TAM state. JobOrder must exist in Bullhorn before any Candidate import referencing it begins, so Positions migrate first in the dependency order.

TAM Applicants map to Bullhorn Candidate records. TAM stores contact information, application date, source, and current workflow stage per applicant. We map TAM's applicant fields to Bullhorn Candidate standard fields (firstName, lastName, email, phone, address), set the dateApplied to the TAM application date, and carry the source attribution. The TAM applicant ID is preserved in a Bullhorn custom field for cross-reference. TAM Applicant custom profile fields migrate as Candidate custom fields.

TAM organizes applicant progress through customer-defined workflow stages with no standardized vocabulary. Bullhorn JobOrder uses pipeline stages configured per record type. We collect the full TAM workflow stage configuration during discovery, map each TAM stage name to an equivalent Bullhorn pipeline stage, and preserve the original stage order so candidate progress reflects correctly in Bullhorn's Opportunity and Candidate pipeline views. Stage probabilities are set to match TAM's implied stage weights if available.

TAM delivers applicant files (resumes, cover letters, portfolio items) as a separate password-protected zip archive. We download and unpack both the TAM CSV and the zip, cross-reference files by applicant ID in the filename, and attach each file to the corresponding Bullhorn Candidate record via ContentDocumentLink. This two-step extraction is the highest-risk step in the migration; we validate file-to-applicant pairing against the CSV before bulk attach to avoid misattachment.

TAM stores custom application questions in the position configuration and responses per applicant. Bullhorn supports custom fields on Candidate (up to 55 per Custom Object depending on edition). We extract the question schema from TAM during discovery, pre-create the corresponding custom fields in Bullhorn (or a Custom Object if question count exceeds field limits), and map responses per applicant. Bullhorn ATS Growth limits 2 Custom Objects; ATS Enterprise allows 10.

TAM hiring team notes, scorecard ratings, and stage-change timestamps migrate to Bullhorn Note records (attached to the Candidate via ContentDocumentLink) and Task records (with ActivityDate set to the original TAM timestamp for timeline ordering). Scorecard ratings migrate as custom fields on the Note or as a separate scorecard object depending on the Bullhorn edition configuration. Formatting may vary between TAM's plain text notes and Bullhorn's rich text Note bodies.

TAM user accounts (recruiters, hiring managers) are tied to applicant assignments and workflow actions. We map TAM users to Bullhorn User records by email match. Any TAM user without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision. We do not migrate TAM user permissions as Bullhorn profiles and permission sets; these are set up natively in Bullhorn post-migration. OwnerId on Candidate records is resolved via the User mapping after provisioning.

TAM positions carry department assignments that may not map cleanly to Bullhorn's schema. If the customer uses Bullhorn's ClientCorporation model (typical for staffing firms), we map TAM departments to Bullhorn BusinessSector or a custom field on ClientCorporation. If Bullhorn is used purely as an ATS without CRM client records, department maps to a custom field on JobOrder.

TAM tracks applicant source (job board, referral, direct) per applicant. Source values map to Bullhorn Candidate source field. TAM's custom source categories (if any) require configuration as Bullhorn picklist values before migration so that source attribution is preserved as a structured value rather than free text.

TAM collects onboarding paperwork metadata. Bullhorn does not have a native onboarding module; onboarding document references and metadata migrate as Bullhorn Case records (if Service Cloud is active in the destination) or as a Bullhorn Custom Object. Actual form templates do not migrate; they must be rebuilt in Bullhorn or a separate onboarding tool. Document storage references from TAM may not resolve in Bullhorn without re-upload.

TAM links each Applicant to a Position. Bullhorn links Candidate to JobOrder via an Application record (or JobSubmission depending on Bullhorn edition). We resolve the JobOrder ID from the TAM position mapping and create Bullhorn Application records linking each Candidate to the corresponding JobOrder. This relationship must be established before the Candidate record is fully usable in Bullhorn's pipeline views.

The TAM file vault zip contains files named with applicant ID patterns. We parse filenames, strip TAM path prefixes, and attach files to Bullhorn Candidate records by matching applicant ID segments in the filename. Any TAM files that cannot be cross-referenced to an applicant ID (orphaned files) are collected in a separate folder with a manifest and flagged in the migration report for manual disposition.