Migrate from Occupop to Recruit CRM & ATS

Occupop Jobs map to Recruit CRM Positions. Each Job carries title, description, department, location, and status (active/closed). We preserve the original Occupop Job ID as source_job_id__c for audit traceability. Active Jobs are imported with their status; closed Jobs are imported with a Closed status flag and excluded from the active pipeline count. Board-distribution history (Indeed, LinkedIn, Reed, etc.) is exported as a structured JSON list per Job and surfaced as a separate sidecar file post-migration for your team to re-create postings in Recruit CRM's multi-posting interface.

Occupop Candidate records map to Recruit CRM Candidates. Standard fields (name, email, phone, current company, current title, LinkedIn URL, source) migrate directly. The AI screening score and rank within the Job's candidate pool migrate as numeric fields to Recruit CRM's candidate rating or custom score fields. Candidates are linked to their destination Position during import using the Job slug-to-position-id lookup resolved at migration time.

Each Occupop Job defines an ordered stage sequence (e.g. Applied, Screening, Interview, Offer). We export the full stage sequence per Job and map stage names to Recruit CRM pipeline stages. If Recruit CRM's default stage set does not match the customer's naming convention, we configure custom stages during the schema design phase. Stage probabilities are preserved if stored in Occupop and mapped to Recruit CRM stage weight fields.

Occupop Users with Admin, Hiring Manager, Recruiter, and Viewer roles map to Recruit CRM Team Members. We export by email match and flag any Occupop role with no direct Recruit CRM equivalent. The customer's admin provisions the matching user accounts in Recruit CRM before migration so that OwnerId references are satisfied at import time. Inactive Occupop users are mapped to inactive Recruit CRM users to preserve historical assignment.

CV files linked to Occupop Candidates are exported as raw files alongside the candidate mapping. We re-attach each CV to the corresponding Recruit CRM Candidate record using the candidate slug resolved at migration time. File naming uses the convention candidate_[id]_cv.[ext] for traceability. If Occupop stores multiple attachments per Candidate, each is mapped individually to the Candidate record.

Occupop interview notes and scorecard responses are stored per Candidate per stage. Recruit CRM does not expose a native interview-feedback object; we land the full feedback text and numeric scores as Notes on the Candidate record with a note type field indicating the stage (e.g. Interview - Screening, Interview - Final Round). The original interviewer name and date are preserved in the note body for audit purposes.

Occupop Custom Fields are arbitrary tenant-defined key-value pairs on Candidate records. We inspect the source tenant's custom field definitions during scoping, count them against the target Recruit CRM plan limit (15 on Pro, 150 on Business and Enterprise), and flag any overage before migration begins. If the count exceeds Pro's limit, the customer upgrades to Business or Enterprise. We map each Occupop custom field to an equivalent Recruit CRM custom field by type (text, number, date, picklist), preserving field labels as configured in Recruit CRM.

Occupop's AI screening score (0-100) and candidate rank within a Job's pool migrate as structured fields on the Recruit CRM Candidate record. The score lands in a numeric custom field (e.g. ai_screening_score__c), and the rank lands as candidate_rank__c. If Recruit CRM's native rating field (1-5 stars) is preferred, we normalise the score to the 1-5 scale using the customer's agreed conversion formula during the transform phase.

Offer letters, employment contracts, and onboarding workflow state live in Cezanne HR's broader suite post-acquisition and are not accessible via Occupop's ATS export. We do not migrate offer or onboarding records. The customer exports these directly from Cezanne HR before migration begins. This exclusion is documented in the migration scope and signed off before data extraction starts.

Occupop tracks which job boards each Job was distributed to (Indeed, LinkedIn, Reed, Glassdoor, etc.) and the posting date. Recruit CRM does not natively store board-distribution history per job. We export this as a structured JSON sidecar file keyed by Job ID and also append it as a formatted note on the Position record so recruiters can re-create distributions manually in Recruit CRM's multi-posting channel without losing the original board list.