Migrate from JobScore to Recruit CRM & ATS

JobScore Candidate records map directly to Recruit CRM Candidates with name, email, phone, address, and resume preserved. Tags migrate as Recruit CRM labels (multi-select or freeform depending on count). Notes migrate as Candidate notes. Phone-number collision detection runs before any write: for each candidate where a matching phone number already exists in the destination, we present a skip/merge/overwrite choice and document the outcome in the migration manifest. Owner assignment maps to the Recruit CRM recruiter field by email match.

JobScore Job records map to Recruit CRM Jobs with title, description, location, department, and employment type preserved. A scoping-stage check verifies all intended jobs are published in JobScore before export; unpublished jobs are flagged for manual supplementation. Status mapping: JobScore published maps to Recruit CRM active/open; archived maps to closed. Department and location fields map to Recruit CRM custom properties or standard fields depending on the account configuration.

JobScore Application records (the join between Candidate and Job) map to Recruit CRM applications tied to the candidate and job records. Application date, current stage, and stage-entry timestamps migrate. Custom form field responses map to Recruit CRM custom fields created during schema setup. Custom stage sub-stages from JobScore are collapsed into the nearest Recruit CRM pipeline stage and the most recent sub-stage name is preserved as a custom property for audit continuity.

JobScore Interview records map to Recruit CRM Interviews with date, time, duration, interview type, and interviewer assignment preserved. The parent Application is resolved at migration time using the Candidate-Job pair, and the interview is attached to the corresponding candidate record in Recruit CRM. Outcome and feedback fields migrate as Interview outcome properties.

JobScore Scorecard records (submitted ratings and comments from interviewers) map to Recruit CRM evaluation or scorecard records attached to the parent Interview. Ratings, comment text, and interviewer uid migrate as structured data. Scorecard responses are stored as evaluation records in Recruit CRM linked via the interview reference resolved during the migration.

JobScore Documents (resumes, cover letters, attachments linked to Candidates or Applications) are exported as raw file blobs and reattached to the corresponding Candidate record in Recruit CRM. Resume parsing in Recruit CRM processes the raw file on import. File type, original filename, and upload timestamp are preserved as document metadata.

JobScore Location records (address, city, state, country) map to the location fields on the corresponding Recruit CRM Job. Location is attached at the Job level rather than the Candidate level. If the destination account uses a shared location library, we check for existing locations by address match before creating duplicates.

JobScore's five standard stages (New, Active, Declined, Withdrawn, Hired) and any Active sub-stages map to Recruit CRM pipeline stages. We create a pipeline in Recruit CRM that reflects the JobScore stage hierarchy, collapsing sub-stages into the nearest named stage and preserving the sub-stage label as a custom field on the application record. Application Status disposition codes (Declined reasons, Withdrawn reasons) migrate as Recruit CRM custom disposition options.

JobScore Users who appear as interviewers, recruiters, or owners on any record map to Recruit CRM team members. Resolution is by email match. Any JobScore User without a matching Recruit CRM account is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive status is preserved.

JobScore Tags (freeform labels applied to Candidates) migrate as Recruit CRM tags on the candidate record. Unlimited tags are supported on both platforms, so no consolidation is required. Tags are written after candidate records are created so that tag associations can be attached to the correct destination record uid.

JobScore Email Templates (body, subject, trigger conditions) are exported with template name, subject line, and HTML/text body. We confirm Recruit CRM template compatibility (variable syntax support) during scoping and flag any template using JobScore-specific merge field syntax that requires manual adjustment in Recruit CRM. Trigger conditions are documented as a written handoff for the admin to reconfigure in Recruit CRM's workflow or automation layer.