Migrate from SnapHire to Crelate

SnapHire Candidate records map directly to Crelate Contact records. The candidate's name, email, phone, address, current company, and title transfer as standard Contact fields. Application history and stage progression are preserved in Crelate's Activity timeline as Event and Task records. We map candidate status (Active, Rejected, Withdrawn) to Crelate's internal status taxonomy and preserve any rejection reason in a custom field.

SnapHire Job records (title, department, location, description, pipeline) map to Crelate Job records. The hiring pipeline in SnapHire becomes an Employment Search Workflow in Crelate, with stage names mapped explicitly during scoping. Job categories from SnapHire transfer as tags or custom fields in Crelate depending on reporting needs.

SnapHire custom candidate data fields with validation rules and multi-choice options (dropdowns, checkboxes) require individual field mapping. Each custom field is created as a Crelate Contact custom field of the equivalent type (Text, Number, Picklist, Checkbox). Multi-choice option sets are mapped explicitly to Crelate picklist values. The full field inventory is requested from the customer during scoping since SnapHire does not publish a schema export.

Each candidate's SnapHire stage movement history (Application, Screening, Interview, Offer, Hired, Rejected) is preserved in Crelate as dated Task and Event records on the Contact's Activity timeline. Stage transition timestamps and any associated notes transfer as Activity notes, maintaining the audit trail for compliance and reporting.

SnapHire's Candidate Match feature stores match scores between talent community candidates and job profiles. We preserve these scores as read-only numeric custom fields on the Crelate Contact record (e.g., snaphire_match_score__c). The matching algorithm itself cannot be replicated in Crelate; if Crelate's sourcing tools or a third-party partner are needed for ongoing matching, the customer's admin configures this post-cutover.

SnapHire rejection reasons are organization-defined freeform or predefined lists. These map to a Crelate Contact custom field (rejection_reason__c) as a picklist or text field depending on the destination schema. The customer's admin reviews and finalizes the rejection reason taxonomy in Crelate post-migration.

SnapHire's configurable hiring-stage workflows do not migrate as code to Crelate. We document the existing SnapHire workflow configuration (stages, actions, conditions) and deliver it as a written handoff document. The customer's Crelate admin rebuilds the workflow as an Employment Search Workflow using Crelate's builder, and rebuilds any associated Activity Forms with field mappings to Contact, Company, and Opportunity core records.

SnapHire job-specific categories used for reporting map to Crelate Tags or a custom field depending on reporting requirements. Categories that represent job type or department are preserved as tags for filtering; categories that represent compliance or sourcing channel may warrant a dedicated custom field for segmentation.

Candidate and job attachments (resumes, cover letters, assessment files) download from SnapHire and upload to Crelate with the same record association. Crelate's Resume Toolbox feature stores parsed and unparsed resume versions. We re-upload binary attachments and ensure the Contact record's primary resume field is set correctly.

SnapHire's onboarding automation pushes hired candidate data to intelliHR (Humanforce). This integration configuration is SnapHire-native and does not have a Crelate equivalent. We extract the onboarding workflow configuration for documentation and recommend rebuilding it as a Crelate Workflow or webhook-based integration to the customer's HRIS post-cutover. The customer should coordinate with intelliHR separately if the downstream HR record creation continues.

SnapHire Owner records map to Crelate User accounts. We resolve owners by email match against the Crelate destination instance. Any SnapHire Owner without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before the record import proceeds.

SnapHire company records associated with candidates map to Crelate Company records. Company name, address, industry, and website transfer as standard Crelate Company fields. Company is created before Contact import so that the Company lookup relationship is satisfied at the moment of Contact insert.