Migrate from 100Hires to Recruit CRM & ATS

100Hires Jobs map directly to Recruit CRM Job Orders. Job title, description, department, location, and posting status migrate as text fields. Pipeline stage definitions from 100Hires map to Recruit CRM pipeline stages which we configure before migration. Job Order status (Open, On Hold, Closed) migrates to the equivalent Recruit CRM status. Job board posting associations (LinkedIn, Indeed, ZipRecruiter) are exported as metadata references and must be re-established manually in Recruit CRM's job board integrations.

100Hires Candidates map to Recruit CRM Candidates. All standard profile fields (name, email, phone, work history, skills from taxonomy) migrate directly. Custom Candidate properties migrate as Recruit CRM custom fields. Before import we run an email-based deduplication pass because the 100Hires Chrome extension can create duplicate Candidate profiles when the same person is imported from both LinkedIn and Gmail. We merge matching records on email address and flag any remaining near-duplicates with different email variants for admin review.

100Hires Applications (the join table linking Candidate to Job with pipeline stage) map to Recruit CRM Applications. We preserve the full stage history with timestamps, the current stage, rejection reasons, and any custom disqualification reasons. Pipeline stage names from 100Hires map to Recruit CRM pipeline stages which we configure before the Application import to ensure stage continuity.

100Hires Interview records (scheduled date, time, interviewers, interview type, calendar integration status) map to Recruit CRM Calendar Events. Interviewer assignments migrate as event invitees. We note that Recruit CRM's Google Calendar sync does not reflect deleted meetings back to Google Calendar according to Reddit reports; this is a destination-side limitation to communicate to users post-migration.

100Hires Evaluation scorecards attached to Interviews map to Recruit CRM Candidate Scorecards. We export the form structure (criteria names and types) and all submitted scores, but flag any custom evaluation rubrics that use non-standard scales (e.g., pass/fail versus 1-5 numeric) for explicit mapping during the migration. Custom criteria without a Recruit CRM equivalent are documented for admin-side reconstruction.

100Hires Notes (free-text records attached to Candidates or Applications by team members) migrate to Recruit CRM Notes with author attribution and creation timestamp preserved. We set the parent record reference to the migrated Candidate or Application ID. Note content migrates as plain text with any embedded formatting converted to plain text equivalents.

Attachments including resumes, cover letters, and portfolio files linked to Candidates or Applications in 100Hires are downloaded and re-uploaded to Recruit CRM. We preserve the original filename, file type, and parent record association (Candidate or Application). Binary files are re-uploaded via Recruit CRM's file upload mechanism during the migration window.

100Hires Users (recruiters and team members) map to Recruit CRM Users by email match. Role and permission assignments are destination-specific and must be reconfigured by the customer's admin post-migration. Any 100Hires User without a matching email in the Recruit CRM destination goes to a reconciliation queue for manual provisioning before record import.

100Hires structured taxonomy for Skills, Departments, and Locations exports as flat lists. Recruit CRM does not have a dedicated taxonomy management layer; Skills and Locations migrate as Recruit CRM custom fields or tags depending on the customer's chosen configuration. We flag any taxonomy entries that cannot be cleanly represented in Recruit CRM's flat-field model for admin resolution during scoping.

100Hires Email Templates (body content, subject lines, placeholder tokens) migrate as raw text with token syntax preserved. Dynamic field tokens from 100Hires (e.g., [candidate.first_name]) must be translated to Recruit CRM's token syntax by the admin post-migration. We document the full token mapping as part of the migration deliverable.

Active in-flight Nurture Campaigns cannot be safely migrated mid-sequence from 100Hires because recipient opt-out states and delivery timestamps are tightly coupled to 100Hires' email infrastructure. We export campaign names, step definitions, and current paused state. Active campaigns are paused before migration cutover. The customer must confirm email consent records are current before re-activating sequences in Recruit CRM. We deliver the campaign definitions as a written document for the admin to rebuild in Recruit CRM's automation tools.

The hosted 100Hires Career Site URL is tied to the organization's account and cannot be exported or redirected. We export all job listing content (descriptions, requirements, benefits text) as structured data for reconstruction on Recruit CRM's hosted career site. The public-facing URL, branding, and site configuration must be rebuilt by the customer's admin post-migration. Job postings that reference the 100Hires career site URL must be updated to point to the new Recruit CRM career site once it is live.