Migrate from Talent Pool Builder to Crelate

Talent Pool Builder Candidate records map to Crelate Person records. Name, contact information, application status, source attribution, and stage history transfer as typed fields. Resume attachments migrate as document references attached to the Person record. Any per-account custom screening fields map to Crelate custom properties, with data type mismatches flagged for manual remediation before production migration.

Job postings migrate to Crelate Jobs with job title, department, location, posting date, and associated pipeline stages preserved. Job board posting history does not transfer as a structured record but is noted in the scope document for the customer's admin to reconfigure in Crelate's distribution settings.

Application records link Candidates to Jobs with a timestamp and stage. The full application timeline, including stage transitions and recruiter notes, migrates as activity history attached to the Job Application record. Stage names map to Crelate's pipeline stage values where a direct match exists; custom stage names map to custom fields or stage labels based on Crelate's configurable pipeline setup.

Talent Pool Builder Requisitions track hiring manager requests and approvals before a job is opened. Stage and status fields vary by account configuration. We map these to Crelate's Job statuses and include a custom field requisition_status__c to preserve the original Talent Pool Builder requisition state. If the destination Crelate account has a dedicated requisition object configured, we map directly to that.

Talent Pool Builder talent pools are segmented candidate lists used for long-term engagement. Pool membership and associated tags migrate to Crelate as a combination of a named Talent Pool record and tag assignments on each Person record. Pool-specific custom fields require per-field mapping to Crelate's custom property schema. Active talent pool engagement status migrates as a Person custom property so re-engagement campaigns can resume immediately in Crelate.

Interview scheduling data and structured scores migrate as Activity records in Crelate with evaluation scores mapped to custom numeric or rating fields. Free-text interview notes may require truncation or cleaning depending on Crelate's field character limits. Interviewer assignment migrates as a User reference on the Activity record, with any unmatched interviewer emails flagged for admin provisioning before production cutover.

Offer records include template placeholders, compensation details, status, and digital signature state. We migrate offer data to Crelate's offer tracking mechanism where one exists, or to Activity records with a custom offer status field. Digital signature state is exported as a text flag and a note indicating the signature status at time of export; post-migration follow-up is required to confirm or re-collect signatures in Crelate.

Per-account custom fields for screening answers, rating scores, source attribution, and compliance data map to Crelate custom properties on the Person record. We request a full field inventory from the Talent Pool Builder account before migration scoping begins, type each custom property against Crelate's supported data types, and create the destination custom properties in Crelate before any data loads. Custom fields with no Crelate equivalent are logged as manual-entry candidates for post-migration data entry.

Email, SMS, and call logs attached to Candidate records migrate as individual Activity records in Crelate. Communication thread context is not preserved because Talent Pool Builder exports these as discrete events rather than threaded conversations. We flag thread gaps in the data validation report and recommend that the customer communicate this limitation to hiring managers who rely on inbox history for interview preparation context.

Resume files and uploaded documents export as file references or binary blobs from Talent Pool Builder. File naming conventions vary by account and are preserved as-is. We attach files to the corresponding Person or Job Application record in Crelate. Any file that cannot be matched to a migrated Person record is held in a reconciliation queue for the customer's admin to resolve.

Talent Pool Builder Owners referenced on Candidates, Applications, Offers, and Interview Records resolve by email match against the Crelate destination User table. Any Owner without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated records is set after User provisioning is confirmed.

Talent Pool Builder's seniority date and union membership fields are platform-specific features that do not activate equivalent compliance logic in Crelate. We export both fields as custom Person properties in Crelate (seniority_date__c and union_membership__c) so the raw data is preserved. Activation of compliance rules in Crelate based on these fields requires a separate configuration step by the customer's IT or legal team post-migration.