Migrate from The Applicant Manager to Crelate

TAM Positions map to Crelate Jobs. The Position title, description, department, and status fields map directly to Crelate's Job Name, Description, Department, and Status. Job status (open, closed, on hold) maps to Crelate's Job status picklist. We preserve the TAM Position ID as a reference field so the customer can cross-reference back to the TAM export during reconciliation. Department assignments require lookup resolution if the customer uses a separate Departments configuration in Crelate.

TAM Applicants map to Crelate Contacts. Each applicant record carries the candidate's name, email, phone, address, application date, source, and current workflow stage. We map applicant contact fields directly to Crelate Contact fields. The TAM applicant ID is preserved in a custom reference field on the Crelate Contact for cross-referencing. Application date migrates to a custom field on Contact; Crelate does not have a native application-date concept outside of the Job pipeline.

TAM's custom workflow stage names and sequences vary by customer configuration, so there is no standard mapping. We collect the complete TAM workflow stage inventory during discovery, map each customer-defined stage to an equivalent Crelate pipeline stage name, and preserve the stage order so candidate progression reflects correctly after cutover. Stage probability percentages from TAM migrate to Crelate's stage probability values. If Crelate has fewer stages than TAM, we map the most-critical stages and flag the remainder for the customer's admin to consolidate post-migration.

TAM resumes and cover letters are stored in a password-protected zip archive separate from the Standard Applicant Data CSV. We download and unpack both packages, cross-reference each file by applicant ID or filename to its corresponding Crelate Contact record, and attach files as ContentDocument records linked via ContentDocumentLink. The re-association step is the primary risk point; we use a deterministic filename pattern (applicantID_resume.pdf) or a lookup table built from the CSV to ensure files attach to the correct Contact.

TAM stores application questions as a schema on the Position, with answers stored per Applicant. We extract both the question definitions and the answer values. Question text and answer type migrate to Crelate's Custom Questionnaires attached to the corresponding Job. Applicant answers migrate to custom fields on the Contact or to the Crelate Activity Form associated with the Job submission. Crelate's Business tier supports up to 20 custom fields per entity; we flag any TAM screening schema that exceeds this and negotiate a field consolidation approach with the customer before migration.

Hiring team notes, scorecard ratings, and stage-change timestamps migrate as Crelate Notes attached to the Contact record, or as Activity Form entries tied to the Job. Stage-change timestamps preserve the original TAM timestamp so candidate movement through the pipeline can be reconstructed from the activity timeline. Formatting of notes may vary from TAM's original presentation; we capture plain text and preserve attachment links where TAM supported them.

TAM user accounts (recruiters and hiring managers) are tied to applicant assignments and workflow actions. We map TAM user accounts by email address to Crelate User records. Assignments on applicant records migrate as Crelate Contact owners or as a hiring team entry depending on the customer's Crelate configuration. Any TAM user without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

TAM onboarding document metadata and storage references can be migrated, but the destination system's onboarding module acceptance determines whether forms are fully functional post-migration. We extract document metadata and attach files to the Contact record where Crelate's onboarding module does not have a direct equivalent. Crelate's onboarding suite (Business Plus and Enterprise) uses a separate onboarding workflow; we document the TAM onboarding field inventory for the customer's admin to reconfigure in Crelate's onboarding tool.

TAM tracks the origin of each applicant (job board, referral, direct, agency). The source field migrates to a Crelate Contact custom field or to the built-in source attribution field if available on the customer's tier. Source tracking supports downstream reporting in Crelate's Analytics module. We flag any TAM custom source categories that do not map to Crelate's standard source picklist values for the admin to add post-migration.

If TAM uses internal tags or rating flags on applicants, these migrate to Crelate's Tag feature on the Contact record. Tags are represented in Crelate's API as a Tags object keyed by category name. We flatten any hierarchical TAM tags to Crelate-compatible string tags and preserve the full original tag label in a custom field if the tag structure is important for the customer's segmentation.

TAM supports custom profile fields per applicant beyond the standard contact schema. We extract the full custom field inventory, map field types to Crelate's equivalent types (text, number, date, picklist, checkbox), and provision them on the Contact object or the Job object depending on whether the field is position-level or applicant-level. Crelate's Business tier caps custom fields at 20 per entity; we audit the TAM custom field count during discovery and flag any overflow for consolidation or Business Plus tier consideration.

TAM job posting status and job board distribution references migrate as job distribution records in Crelate. If TAM tracks which boards a position was posted to (Indeed, Monster, LinkedIn, etc.), we map these to Crelate's Sponsored Job Posting integration references or to a custom field on the Job record. Active posting status migrates to the Job's publish status in Crelate's branded job portal.