Migrate from Talent Ninja to Crelate

Talent Ninja candidate records map to Crelate Person objects. The candidate profile—including name, email, phone, resume, LinkedIn URL, and sourced video cover letter attachment—transfers to Crelate's Person fields and Document Attachments. Any Talent Ninja custom candidate fields are flagged for mapping to Crelate custom Person fields or documented for admin configuration. The original Talent Ninja created date and last updated timestamp migrate as read-only audit fields on the Crelate Person record.

Talent Ninja job postings map to Crelate Job Requisition records. The job title, description (with rich text formatting), location, employment type, and salary range fields transfer directly. Job Requisition status (Draft, Open, On Hold, Filled, Closed) maps from Talent Ninja's job status field. We preserve the original job board distribution list (channels where the job was posted) as a Crelate custom multi-select field for reference; Crelate's own job distribution integrations are configured separately post-migration.

Talent Ninja application records map to Crelate Application objects linked to the corresponding Person (candidate) and Job Requisition. The application status pipeline stages from Talent Ninja (e.g., Applied, Screening, Interview, Offer, Hired, Rejected) map to Crelate Application status values, with stage transition timestamps preserved as Activity dates. We resolve the Person and Job Requisition references at migration time before inserting Applications to satisfy Crelate's lookup requirements.

Talent Ninja does not have a standalone client object; company context lives within job postings and candidate records. Where candidate profiles reference an employer or placement company, we extract those references and merge them into Crelate Organization records. Multiple candidate records referencing the same employer company deduplicate into a single Crelate Organization. The Organization record links to Person records via Crelate's candidate-client relationship model.

Talent Ninja interview scores and evaluation ratings migrate to Crelate custom numeric or rating fields on the Application or Person record depending on where the score is stored in the source. We preserve the score value, the evaluator name (mapped to Crelate User if present), and the evaluation date. If Talent Ninja stores multiple interview rounds per application, each round becomes a separate evaluation entry in Crelate.

Talent Ninja offer records (offer amount, start date, offer status, rejection reason if applicable) map to Crelate Offer fields or a custom Offer object if configured in the destination environment. Offer status (Pending, Accepted, Declined, Withdrawn) migrates as-is. The offer is linked to the Application and the corresponding Person and Job Requisition.

Talent Ninja's candidate source attribution (referral, job board, direct, agency) migrates to Crelate's Source field on the Person record. If Talent Ninja tracks source per application rather than per candidate, the source value migrates as an Application-level custom field.

Talent Ninja's pipeline stages (Applied, Shortlisted, Interview, etc.) are mapped to Crelate Application Status values. We configure Crelate's Application status picklist during schema setup to match the exact stage names used in Talent Ninja, avoiding renames post-migration. Stage transition dates migrate as Application Activity records.

Talent Ninja custom fields on candidate profiles (e.g., skill tags, certifications, clearance level, visa status, salary expectation) are flagged during discovery scoping. We create equivalent custom fields in Crelate's Person object schema before migration. Field data type mapping is verified: picklists map to picklists, multi-select maps to multi-select, date fields map to date fields. Any Talent Ninja fields without a direct Crelate equivalent are documented for admin decision during configuration.

Talent Ninja's job board distribution history—indicating which of the 300+ job boards a job was posted to—is preserved as a custom multi-select field on the Crelate Job Requisition record. This is a reference field for audit and reporting; Crelate configures its own job distribution integrations (Indeed, LinkedIn Jobs, Glassdoor, ZipRecruiter) separately post-migration.

Talent Ninja owner or assigned recruiter on a candidate, job, or application record maps to Crelate User by email match. Any Talent Ninja Owner without a matching Crelate User is placed in a reconciliation queue for the customer's admin to provision before the record import phase continues.

Talent Ninja candidate notes and comment history migrate to Crelate Activity records or Notes attached to the Person and Application records. The original author and timestamp are preserved. Activity type (note, email, call, interview) is mapped to the corresponding Crelate Activity type field. If Talent Ninja stores interview scheduling data, it migrates to Crelate Event or Calendar Activity records.