Migrate from Talent Pool Builder to Recruit CRM & ATS

Talent Pool Builder Candidate records map to Recruit CRM Contact. We extract name, email, phone, source attribution, application stage, and any screening score custom fields. Resume attachments migrate as document references. The Contact record is the primary parent for all engagement and application history in Recruit CRM, so we resolve the Contact insert before any child object migration begins.

Talent Pool Builder Job postings map to Recruit CRM Position. We preserve job title, department, location, posting date, and the pipeline stage configuration. Stage names from Talent Pool Builder map to Recruit CRM pipeline stages; if stage names differ materially, we create matching stages in Recruit CRM during the pre-import schema configuration step.

Talent Pool Builder Requisitions map to Recruit CRM Requirement (or Requirement object within the Position module depending on Recruit CRM edition). We extract requisition status, hiring manager reference, and approval history as custom fields because these do not have a direct native equivalent in Recruit CRM's standard schema.

Talent Pool Builder Talent Pools map to Recruit CRM Talent Pool with pool name and description preserved. Pool membership — the list of Candidate IDs belonging to each pool — migrates as a bulk association file that Recruit CRM imports to link existing Contact records to the destination Talent Pool. Pool-specific custom fields (such as engagement score or source tier) map as custom fields on the Contact record if Recruit CRM supports custom Contact fields in the talent pool context.

Talent Pool Builder Application records (linking a Candidate to a Job with a timestamp and stage) map to Recruit CRM Application. We preserve the full application timeline including stage transitions and recruiter notes. Application status maps to Recruit CRM's application state enumeration with any non-standard statuses mapped to a custom field for manual resolution post-migration.

Interview scheduling data and structured score fields from Talent Pool Builder migrate to Recruit CRM Interview records linked to the Application. Free-text interview notes migrate as activity notes with a reference to the original field source so reviewers can trace provenance. Score fields that exceed Recruit CRM's field type limits are flagged as candidates for truncation or custom field creation.

Talent Pool Builder Offer records (template placeholders, offer status, digital signature state) map to Recruit CRM Offer records attached to the Application. We export the offer data and flag the digital signature status as a post-migration remediation item because signature state cannot be replicated across platforms without re-initiating the signing workflow in Recruit CRM.

Talent Pool Builder accounts frequently create custom fields for screening answers, rating scores, and source attribution. These fields vary significantly in naming and data type across accounts. During scoping we request a full field inventory from the source account, classify each by data type, and map to Recruit CRM custom fields of the equivalent type. Fields with no matching Recruit CRM type are logged as manual-entry candidates for post-migration remediation.

Email, SMS, and call logs from Talent Pool Builder migrate as individual activity records in Recruit CRM's communication timeline. Thread continuity is not guaranteed because Talent Pool Builder exports communication as discrete event records without guaranteed parent-child linkage. We export what is available, flag thread gaps in the data validation report, and recommend the customer communicate the limitation to hiring managers who rely on inbox history for interview context.

Resume files and uploaded documents from Talent Pool Builder migrate as document references or binary blobs depending on the export method available from the vendor-assisted data dump. File naming conventions vary by account and are preserved as-is. We verify each attachment is linked to the correct Contact record before marking the attachments phase as complete.