Migrate from TalentRecruit to Crelate

TalentRecruit candidate profiles (contact information, work history, education, skills, resume files, and tags) map directly to Crelate Contact records. The Crelate Contact API uses FirstName and LastName as separate required attributes; we extract both from TalentRecruit's name field and write them as separate API properties. Tags migrate as a tags object keyed by category name (Default for untagged labels). Resume files are uploaded as ContentDocument and linked via ContentDocumentLink to the Contact record.

TalentRecruit jobs (title, description, department, location, hiring manager assignment, opening count, and stage configuration) map to Crelate Job records. The Job Name is the required Crelate field. Department and location migrate as custom fields or standard Crelate Job fields depending on the customer's field taxonomy. Hiring manager assignment resolves as a Contact lookup in Crelate (via the _Id lookup convention for the assigned recruiter).

TalentRecruit application records (linking a Candidate to a specific Job with current stage, stage-transition timestamps, source channel, and tags) map to Crelate as a submission relationship between the migrated Contact and the migrated Job. Stage history is preserved in a custom multi-line text field or as structured Activity notes since Crelate does not expose a native application-stage history object. Source attribution (career page, job board, referral) migrates to a custom Source field.

TalentRecruit interview records (scheduled datetime, interviewer panel, calendar references, and evaluation scorecards with free-text feedback) map to Crelate Activity records or Notes attached to the Contact or Job. Scorecard templates vary per TalentRecruit tenant, so we flatten each scorecard into a structured note body with the evaluation date, interviewer,评分 dimensions, and free-text feedback as key-value pairs. The original scorecard template is preserved as a separate Note for the customer's admin to review.

TalentRecruit job posting records (which job boards and career pages a requisition was published to, posting date, and status per channel) are exported as a structured manifest and mapped to a custom multi-select picklist or structured text field on the Crelate Job record. Channel-specific status (active, paused, expired) is preserved as a custom field. Job board integrations are re-established in Crelate post-migration using Crelate's native job board connectors.

Assessment scores and test results linked to an application in TalentRecruit migrate as structured data in Crelate custom fields on the Contact record or as Notes attached to the application relationship. Assessment type, completion timestamp, and score are preserved. Proprietary third-party assessment vendor formats that TalentRecruit stored as opaque data are flagged for re-entry in Crelate's assessment integration (if applicable) or noted as requiring manual verification.

TalentRecruit offer records (salary, benefits summary, start date, approval status, and signed document attachment) migrate with structured fields mapped to Crelate Contact custom fields or as a Note attached to the Contact. The signed offer document is uploaded as a ContentDocument and linked to the Contact. Approval chain status is preserved as a custom picklist field. Crelate Hire handles new-offer workflows natively, so offer data is imported as historical reference rather than as live workflow state.

TalentRecruit onboarding checklists, task structures, and completion state linked to hired applications migrate as Notes or structured text attached to the Crelate Contact record. Completed state does not carry over as live workflow state; the customer's Crelate admin rebuilds the onboarding checklist in Crelate Hire or as custom Tasks. We preserve the checklist structure and task completion percentages as a reference document for rebuilding.

TalentRecruit user accounts, role assignments, and team memberships are exported as a reference list. Crelate User records must be re-provisioned by the customer's admin during implementation because User IDs are system-assigned and not portable. We export the full role taxonomy (recruiter, hiring manager, admin, viewer, etc.) as a role-mapping spreadsheet that the customer's Crelate admin uses to assign permissions under Settings | Advanced Settings | User Roles. The mapping spreadsheet also identifies which TalentRecruit users are active versus inactive.

TalentRecruit candidate and application tags (stored as flat label arrays) map directly to Crelate Tag records. Crelate's API uses a tags object keyed by category name within each record; we map the default TalentRecruit tag category to the Crelate Default tag category and preserve all tag names verbatim. Tags used for pipeline stage classification are identified separately so the customer's admin can decide whether to use native Crelate stage controls instead of tags for workflow tracking.

TalentRecruit tenant-specific custom fields (beyond the standard candidate, application, and job objects) are captured during discovery and mapped to Crelate custom fields on the equivalent entity. Crelate field types include text, number, currency, date, picklist, multi-select picklist, and boolean. We cross-reference field types during transform to avoid mapping a date field to a monetary field (a constraint documented in Crelate's field-mapping guide). Custom form field mappings are configured in Crelate under Settings | Custom Forms after the base schema is deployed.

TalentRecruit does not have a native Company/Account object in its core ATS data model, but agency workflows often store client company data within candidate company associations or as separate records. We extract any client-company records as identified during discovery and map them to Crelate Company records. Crelate's Company API requires a Name field. Address, industry, and client contact information map to standard Crelate Company fields or custom fields as appropriate.