Migrate from 100Hires to Crelate

100Hires Candidate records map directly to Crelate People (the contact-side of the CRM). All standard fields (name, email, phone, address, work history, education) migrate as-is. Custom Candidate properties in 100Hires map to Crelate custom fields on the Person record, with value-mapping for picklist fields. Candidates imported via the 100Hires Chrome extension may have duplicate email entries; we run a deduplication pass on email addresses before insert and flag any duplicate pairs for customer review.

100Hires Job records map to Crelate Job with job title, description, department, location, employment type, and posting status preserved. The 100Hires pipeline stage definitions on each Job map to Crelate's pipeline stages and workflow stages, which we configure before migration. Job board posting distribution settings do not migrate; these are destination-specific and require reconfiguration in Crelate's job distribution settings.

100Hires Application records link a Candidate to a Job and track pipeline stage progression. We map Application to Crelate Application, preserving stage history, submission timestamps, rejection reasons, and custom disqualification reasons. The Application record holds the link to both the migrated Person (from Candidate) and the migrated Job, requiring both parent records to exist before Application import. We validate that every Application's Candidate and Job references resolve before inserting.

100Hires Interview records (scheduled dates, times, interviewers, interview types, calendar integration status) map to Crelate Interview or Activity records. We preserve interviewer assignment by resolving the 100Hires User reference to the migrated Crelate User. Interview status and outcome migrate as custom fields. If 100Hires used G Suite calendar integration, the meeting link migrates as a custom field rather than as a native calendar event.

100Hires custom evaluation scorecards map to Crelate Activity Forms (for interviewer scorecards) and Application Forms (for candidate stage-gate evaluations). We export the form structure and all submitted scores, but custom scoring rubrics (e.g., 1-5 scale vs pass/fail, custom criteria with non-standard weightings) require explicit mapping to Crelate form fields. Unmapped custom criteria are flagged in the pre-migration audit for customer resolution before form reconstruction.

100Hires Notes attached to Candidates or Applications migrate to Crelate Notes. Note content, author (User), and creation timestamp transfer directly. Notes attached to Applications link via the migrated Application record. Notes with no parent record (orphaned) are flagged and held for customer review.

100Hires Message records (email conversations tied to Candidates or Applications) migrate to Crelate Activity records or email thread equivalents. External email threads that originated in Gmail, LinkedIn, or the 100Hires Chrome extension may require thread re-association in Crelate if the thread root is outside the 100Hires system. We preserve message content, metadata, and timestamps; the CRM link attaches to the migrated Person record.

100Hires Users (recruiters and team members) map to Crelate Users. We resolve by email match. Role and permission assignments are destination-specific and require reconfiguration by the customer's admin post-migration. Any 100Hires User without a matching Crelate User goes to a reconciliation queue.

100Hires Attachments (resumes, cover letters, portfolio files) linked to Candidates or Applications migrate as Crelate Resume or Attachment records. Binary files download and re-upload with filenames and parent record associations (Person, Application) preserved. Resume parsing in Crelate Business tier (Premium Resume Parsing) applies automatically to migrated resume files.

100Hires Skills taxonomy migrates as a flat list and maps to Crelate Skills. We run a case-insensitive match against existing Crelate Skills and create new entries for unmatched values. Skills on Candidates migrate as linked Skill records on the migrated Person.

100Hires Departments taxonomy maps to Crelate Departments, used to categorize Jobs and User assignments. Department assignments on Jobs migrate as the Department reference on the Job record.

100Hires Locations taxonomy maps to Crelate Locations, used to specify Job location and Candidate location preferences. Location entries migrate with address details where present.

100Hires Email Templates (body content, subject lines, placeholder tokens) migrate as Crelate Email Templates. Dynamic placeholder tokens from 100Hires syntax are preserved as raw text and flagged for the customer's admin to re-apply using Crelate's template token syntax post-migration.

100Hires Nurture Campaigns cannot be migrated as active sequences because recipient opt-out states and delivery timestamps are tightly coupled to the 100Hires email infrastructure. We export campaign definitions (names, step definitions, email template references) as a written inventory document. Active in-flight campaigns are paused before migration and resumed in Crelate's Automation and Sequencing (Business Plus tier) by the customer's admin using the inventory as a rebuild guide.