Migrate from Talent Ninja to Recruit CRM & ATS

Talent Ninja Candidate records map to Recruit CRM Candidate records. The primary fields (full name, email, phone, LinkedIn URL, location, current title, current company) migrate directly. The resume file migrates as a ContentDocument attachment linked to the Candidate record via ContentDocumentLink. We resolve the duplicate detection key (email) before insert to prevent duplicate Candidate records in Recruit CRM.

Talent Ninja Job postings map to Recruit CRM Job records. Fields including job title, job description, location, employment type (full-time, part-time, contract), salary range, and required skills migrate to the corresponding Recruit CRM job fields. Job status (active, on hold, filled, closed) maps to Recruit CRM's job status values. We preserve the original job created date and last modified date as custom fields if they do not map natively.

Talent Ninja Application records (candidate-job associations with stage history) map to Recruit CRM's pipeline stage entries on the Job record. Each application maps as a Candidate assigned to a specific stage in the Job's Kanban pipeline. Stage names from Talent Ninja are mapped to Recruit CRM's configurable stage labels during the pipeline configuration phase. The application submission date, last activity date, and rejection reason (if applicable) migrate as stage metadata.

Talent Ninja Company records map to Recruit CRM Client records. Fields including company name, industry, size (employee count), website, billing address, and primary contact information migrate directly to Recruit CRM's Client module. Recruit CRM's Client module is integrated with Jobs, meaning the Client lookup on the Job record is populated during migration when the Company-to-Client mapping is resolved.

Talent Ninja custom fields on Candidate records are identified during the scoping phase. We map each custom field to an equivalent custom field in Recruit CRM's Candidate module, using Recruit CRM's field type matching (text, number, date, picklist, checkbox, currency). Any Talent Ninja custom field without a direct Recruit CRM equivalent is flagged in the scoping report with a recommended configuration. Data migrates into the configured custom field after the destination field is provisioned.

Talent Ninja interview score data (numerical ratings, evaluator comments, interview stage labels) migrates to Recruit CRM's Candidate Notes attached to the relevant Candidate record, or to custom numeric fields if the customer elects structured scoring migration. The interview date and interviewer name migrate as date and user fields on the note or custom field.

Talent Ninja offer details (offered salary, offer date, offer status, expiry date) map to Recruit CRM custom fields on the Candidate record or as structured notes. We preserve the offer status chain (extended, accepted, declined, expired) as a picklist-style custom field to maintain the offer lifecycle history for reporting purposes.

Talent Ninja Owner records (recruiters and administrators) map to Recruit CRM User records. We resolve by email match against Recruit CRM's User table. Any Talent Ninja Owner without a matching Recruit CRM User is held in a reconciliation queue for the customer's admin to provision before production migration begins.

Talent Ninja candidate tags (skills tags, source tags, status tags) migrate to Recruit CRM candidate tags. Recruit CRM supports tagging on candidate records natively. Tags used for skills classification migrate as Recruit CRM skills tags; tags used for sourcing attribution migrate as separate source tags. The customer selects the tagging strategy during scoping.

Talent Ninja job posting distribution settings (which boards a job was posted to, posting date, posting status per board) do not migrate as configuration data. We document every active distribution configuration as a written record so the customer's admin can reconfigure job board integrations in Recruit CRM. This is documented as a separate rebuild task outside migration scope.