Migrate from The Applicant Manager to Recruit CRM & ATS

TAM Positions (job title, description, department, open/closed status) map to Recruit CRM Job Orders. We extract the position status field to set the Job Order's open/closed flag. Department assignments from TAM become custom picklist values or tags in Recruit CRM's job configuration. Active positions migrate as open jobs; archived positions migrate as closed records with historical data intact. The job order is created first so that applicants can reference it during import.

Each TAM Applicant (contact information, application date, source, current workflow stage, custom profile fields) maps to a Recruit CRM Candidate record. We use the applicant email address as the dedupe key. Application date migrates as the created_at timestamp. Source attribution (Indeed, LinkedIn, referral, direct) becomes a custom field or tag in Recruit CRM. Current workflow stage resolves via the stage name mapping established during discovery so the candidate lands in the correct pipeline stage on day one.

TAM's customer-defined workflow stage names and sequence have no standard vocabulary across TAM instances. We collect the complete workflow configuration during discovery, map each TAM stage to an equivalent Recruit CRM pipeline stage preserving the original order, and configure the pipeline in Recruit CRM before applicant migration begins. Stage probability percentages from TAM migrate as informational fields in Recruit CRM if the customer uses them for reporting.

TAM delivers applicant files (resumes, cover letters, portfolio items) as a separate password-protected zip archive. We unpack the archive, match each file to its applicant record using filename or ID cross-reference from the CSV export, then attach the file to the corresponding Recruit CRM Candidate record via the API. This two-step extraction and re-association adds a processing layer that must be handled carefully to avoid misattachment. File metadata (upload date, file type) migrates where available in the export.

TAM stores custom application questions per position along with each applicant's responses. We migrate the question text, answer type (text, multiple choice, yes/no, rating), and required flag as a Recruit CRM custom form field group attached to the Job Order. Conditional question logic (showing one field based on a prior answer) does not migrate and must be rebuilt in Recruit CRM's form builder. Applicant responses map to the corresponding custom field values on the Candidate record.

Hiring team notes, scorecard ratings, and stage-change timestamps tracked per applicant in TAM migrate as activity history entries in Recruit CRM. We preserve the timestamp, author (linked to the matching Recruit CRM user), and note body. Scorecard ratings map to custom numeric or picklist fields on the Candidate record. Formatting of note bodies may vary between platforms; we do a best-effort rich-text pass on import.

TAM user accounts tied to applicant assignments and workflow actions map to Recruit CRM team member records. We match by email address. Any TAM user without a matching Recruit CRM account is held in a reconciliation queue for the admin to provision before record import resumes. Active versus inactive status and role (recruiter, hiring manager, read-only) maps to Recruit CRM's role and permission configuration.

TAM's onboarding paperwork collection metadata migrates as document reference fields on the Candidate record in Recruit CRM. The actual form files migrate as attachments where the TAM export provides a file path. Form logic and conditional onboarding steps (common in agency temp-to-hire placements) do not migrate as configured rules and must be rebuilt in Recruit CRM's onboarding module.

TAM recruiter and hiring manager accounts migrate to Recruit CRM team member records with the same email as the dedupe key. Role-based access (full recruiter, hiring manager, admin) maps to Recruit CRM's permission groups. We preserve the account creation date as a reference field. Any TAM user accounts without a corresponding team member provisioning in Recruit CRM go to a reconciliation queue for the customer admin to resolve before the applicant import phase.

TAM's department field on positions migrates as a Recruit CRM tag or custom picklist field on the Job Order. If the customer uses departments as a reporting dimension in TAM, we recommend creating a custom field rather than relying on tags so that department filtering works in Recruit CRM's analytics module. The customer confirms the preference during discovery.

The application source field in TAM (Indeed, LinkedIn, Employee Referral, Walk-in, etc.) migrates as a source tag on the Recruit CRM Candidate record. Source attribution is preserved for reporting on candidate acquisition channels. If TAM uses a free-text source field, we categorize recognizable sources and tag the remainder as Direct/Unknown for the admin to correct post-migration.

TAM's application date (the date an applicant entered the system for a specific position) migrates as the Candidate's created_at timestamp in Recruit CRM. Stage-change timestamps migrate as individual activity entries with the original timestamp preserved for accurate pipeline history. This ensures the candidate timeline reflects the full journey from first application through each workflow stage transition.