Migrate from Talent Connects to Recruit CRM & ATS

Talent Connects Candidates map directly to Recruit CRM Candidates. Standard fields (name, email, phone, resume URL, application timestamp) migrate as typed fields. Application status history (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Recruit CRM's Candidate stage values. Resume files are imported as attachments linked to the Candidate record. We resolve any duplicate candidates by email dedupe before insert. Note: Recruit CRM's Candidate object does not have a native Talent Pool equivalent, so passive-sourced candidates require a custom sourcing attribute.

Talent Connects Jobs map to Recruit CRM Jobs with title, description, status (Open, Closed, On Hold), and pipeline stage configuration. The job's assigned pipeline or stage in Talent Connects maps to Recruit CRM's Pipeline and corresponding Kanban stage. Active versus archived status is preserved. Talent Connects Growth tier's 10-job limit is flagged during scoping — if the source account exceeds 10 active jobs, a plan upgrade or job archival is required before migration.

Talent Connects' application record (Candidate applied to a Job) maps to Recruit CRM's Application or submission record, preserving the link between Candidate and Job. Application date, source channel, and rejection reason (if applicable) transfer. The application status in Talent Connects (Applied, Shortlisted, Interview Scheduled, Offer Extended, etc.) maps to Recruit CRM's submission stage values.

Talent Connects interview records (date, time, attendees, interview type, outcome notes) map to Recruit CRM Task and Event records linked to the Candidate and Job. Calendar sync settings do not transfer — these require reconfiguration in Recruit CRM's calendar integration (Google Calendar or Outlook). Video interview links from Talent Connects' built-in video platform do not migrate; Recruit CRM does not have a native video interview feature, so the admin should re-establish video links post-migration.

Talent Connects' Talent Pool feature (passive candidate sourcing separate from active applications) exists only on the Enterprise tier at $399/month and has no direct Recruit CRM equivalent. We migrate Talent Pool records as Candidate records with a custom sourcing-tag field set to 'Talent Pool (Imported)' to preserve the sourcing context. The passive-sourcing workflow, talent community settings, and engagement history specific to Talent Pool do not transfer and require rebuilding in Recruit CRM's candidate tagging and list-building features.

Talent Connects User records (name, email, role, active/inactive status) map to Recruit CRM Users. Role assignment migrates as a basic role label. Talent Connects Enterprise multi-level permission configurations (department hierarchies, granular access control) do not export as structured data and cannot migrate. Recruit CRM's Teams and Custom Roles feature (Business and Enterprise tiers) must be configured post-migration, with permission granularity reviewed by the customer's admin. Active user count should be confirmed before migration because Recruit CRM is per-user priced.

Talent Connects generates hosted career pages from Job data. The career page template, branding settings, and URL structure do not export as structured data. We flag Career Page configuration as a discrete rebuild item — the candidate list and job data populating the page transfer as normal Job records in Recruit CRM, but the page template and branding require manual reconfiguration in Recruit CRM's career page builder. The admin should export a screenshot of the current career page before migration day.

Talent Connects bulk email campaigns and engagement history are stored as campaign records with send history and open/click tracking. These do not have a direct equivalent in Recruit CRM's data model. We map email campaign activity to Candidate-level Activity or Note records capturing the send date and subject as text, with open/click data flagged as untransferred. Recruit CRM's automated email sequencing features (Business and Enterprise tiers) must be rebuilt post-migration. Email templates from Talent Connects are not exported as structured data and do not migrate.

If Talent Connects contains Company or Client records (particularly from Enterprise tier usage), these map to Recruit CRM's Client/Company object. Company name, contact name, email, phone, website, and address fields migrate directly. Recruit CRM supports custom fields on Client records for additional attributes. This object is optional in Talent Connects but standard in Recruit CRM, so its presence depends on whether the source account used this object.

Talent Connects' optional AI-Assistant add-on ($49/month) generates AI-produced candidate ranking scores and job description suggestions. These scores are computed at query time and do not persist as structured fields in the database. We cannot migrate AI scores. We create a custom field ai_candidate_score_source on the Candidate record labeled 'AI-Assisted Ranking (Source: Talent Connects)' as a placeholder for manual score entry if the customer wishes to preserve comparative rankings. AI-generated job description suggestions are noted as not migratable.