Migrate your Occupop data
Cloud ATS built for SMBs hiring in volume, with unlimited users, 1-click job distribution, and AI-driven candidate scoring in a straightforward, affordable package.
In its favor
Why people choose Occupop
The signal that keeps Occupop on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Unlimited user seats mean hiring teams of any size can access Occupop without per-seat billing surprises — common in enterprise ATS platforms.
1-click posting to dozens of job boards simultaneously reduces manual effort for high-volume recruiting teams that previously managed each channel separately.
AI-powered CV screening and candidate scoring give small HR teams a triage layer without needing a dedicated sourcer for every open role.
Responsive support and a straightforward pricing model appeal to SMB buyers who have been burned by hidden costs or tier-locked features in Workday or Greenhouse.
The platform was purpose-built for SMBs hiring 50–1000 employees, making its UX and feature set more focused than enterprise ATS products scaled down for small teams.
Advanced reporting and deep analytics lag behind enterprise HCM platforms, frustrating People teams that need custom dashboards or cross-pipeline trend analysis.
Occupop's feature set narrows as hiring needs scale beyond mid-market volume, pushing fast-growing companies toward platforms like Greenhouse, Lever, or Workday ATS.
Integration catalogue is smaller than competitors — teams with established HRIS, payroll, or background-check tools may face manual re-entry or custom integration work.
The acquisition by Cezanne HR (March 2025) introduces uncertainty about roadmap direction, pricing continuity, and long-term product independence, prompting some customers to evaluate alternatives proactively.
Reasons to switch
Why people leave Occupop
The recurring reasons buyers give for replacing Occupop. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Occupop fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Occupop pricing overview
Occupop's pricing is described as straightforward and affordable with no per-seat billing for unlimited users. Specific tier pricing is not publicly documented in available sources; prospective customers are directed to request a quote. A 2-week free trial with no credit card is available.
Professional
Tier 1 of 4
$190/month or $1,900/year
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Occupop's schedule — see our quote-based pricing →
What gets migrated
Occupop object support
Object-by-object support for Occupop migrations. Per-pair details surface during scoping.
Jobs (Positions)
Fully supportedJobs are the top-level container in Occupop. Each Job holds its title, description, department, location, and status. We export Jobs with their active/closed state and preserve the original job ID as a reference for re-associating Candidates during import.
Candidates (Applicants)
Fully supportedCandidates are the primary record. Each Candidate links to a Job and carries name, email, phone, CV file reference, stage history, and a score from AI screening. We export all candidate fields, stage transitions, and timestamped events. Custom fields added via Occupop's Custom Fields feature are included as key-value pairs.
Workflow Stages
Fully supportedEach Job has an ordered list of stages (e.g. Applied, Screening, Interview, Offer). We export the full stage sequence per Job. When importing into a destination ATS, we map stages by name or allow customers to define a custom stage mapping table.
Users (Hiring Team Members)
Mapping requiredUsers in Occupop have names, emails, and role-based permissions (Admin, Hiring Manager, Recruiter, Viewer). We export all users and map them to equivalent roles in the destination system, flagging any permissions that have no direct equivalent for manual review.
CVs and Attachments
Fully supportedCVs are stored as file references linked to Candidate records. We export the raw CV files alongside the candidate mapping so they can be re-attached in the destination ATS or stored as linked documents in a DMS.
Interview Feedback and Notes
Mapping requiredInterview notes and scorecard responses are stored per Candidate per stage. Not all ATS platforms expose a native interview-feedback object; we export the full text and scores and land them as notes, comments, or custom fields depending on the destination's schema.
Custom Fields
Mapping requiredOccupop introduced Custom Fields allowing companies to define arbitrary key-value pairs on Candidate records. We detect any custom field definitions in the export, include them as structured data, and map them to matching custom properties in the destination where supported.
Job Posting Distribution History
Mapping requiredOccupop tracks which job boards (Indeed, LinkedIn, Reed, etc.) a Job was posted to and the posting date. We export this as a structured list per Job. The destination may not track board distribution natively, so we surface it as a custom Job property or note for the customer to act on manually.
Score and Ranking Data
Fully supportedThe AI screening feature assigns a score to each Candidate based on CV-to-job-description matching. We preserve the raw score and rank within the Job's candidate pool. This is exported as a numeric field on the Candidate record.
Offer and Onboarding Records
Not in this platformOffers and onboarding steps live in Cezanne HR's broader suite post-acquisition and are not part of Occupop's ATS core. We do not migrate offer letters, contracts, or onboarding workflow state. Customers should handle these in Cezanne HR directly.
| Object | Support | Notes |
|---|---|---|
| Jobs (Positions) | Fully supported | Jobs are the top-level container in Occupop. Each Job holds its title, description, department, location, and status. We export Jobs with their active/closed state and preserve the original job ID as a reference for re-associating Candidates during import. |
| Candidates (Applicants) | Fully supported | Candidates are the primary record. Each Candidate links to a Job and carries name, email, phone, CV file reference, stage history, and a score from AI screening. We export all candidate fields, stage transitions, and timestamped events. Custom fields added via Occupop's Custom Fields feature are included as key-value pairs. |
| Workflow Stages | Fully supported | Each Job has an ordered list of stages (e.g. Applied, Screening, Interview, Offer). We export the full stage sequence per Job. When importing into a destination ATS, we map stages by name or allow customers to define a custom stage mapping table. |
| Users (Hiring Team Members) | Mapping required | Users in Occupop have names, emails, and role-based permissions (Admin, Hiring Manager, Recruiter, Viewer). We export all users and map them to equivalent roles in the destination system, flagging any permissions that have no direct equivalent for manual review. |
| CVs and Attachments | Fully supported | CVs are stored as file references linked to Candidate records. We export the raw CV files alongside the candidate mapping so they can be re-attached in the destination ATS or stored as linked documents in a DMS. |
| Interview Feedback and Notes | Mapping required | Interview notes and scorecard responses are stored per Candidate per stage. Not all ATS platforms expose a native interview-feedback object; we export the full text and scores and land them as notes, comments, or custom fields depending on the destination's schema. |
| Custom Fields | Mapping required | Occupop introduced Custom Fields allowing companies to define arbitrary key-value pairs on Candidate records. We detect any custom field definitions in the export, include them as structured data, and map them to matching custom properties in the destination where supported. |
| Job Posting Distribution History | Mapping required | Occupop tracks which job boards (Indeed, LinkedIn, Reed, etc.) a Job was posted to and the posting date. We export this as a structured list per Job. The destination may not track board distribution natively, so we surface it as a custom Job property or note for the customer to act on manually. |
| Score and Ranking Data | Fully supported | The AI screening feature assigns a score to each Candidate based on CV-to-job-description matching. We preserve the raw score and rank within the Job's candidate pool. This is exported as a numeric field on the Candidate record. |
| Offer and Onboarding Records | Not in this platform | Offers and onboarding steps live in Cezanne HR's broader suite post-acquisition and are not part of Occupop's ATS core. We do not migrate offer letters, contracts, or onboarding workflow state. Customers should handle these in Cezanne HR directly. |
Gotchas
What to watch for in Occupop migrations
Issues we've hit on past Occupop migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Cezanne HR acquisition may change data residency and contract terms
Offer and onboarding data lives outside Occupop's ATS scope
Custom Fields schema varies by tenant and may require mapping
Job posting board-distribution history does not map to standard ATS fields
| Severity | Issue |
|---|---|
| Medium | Cezanne HR acquisition may change data residency and contract terms |
| Medium | Offer and onboarding data lives outside Occupop's ATS scope |
| Low | Custom Fields schema varies by tenant and may require mapping |
| Low | Job posting board-distribution history does not map to standard ATS fields |
Leaving Occupop?
Where Occupop customers move next
5 destinations Occupop can migrate to.
How a Occupop migration works
Four steps, Occupop-specific
Connect
Not publicly documented into Occupop. Scopes limited to read-only on the data we move.
Map
We translate Occupop-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Occupop quirks before production.
Migrate
Full migration with Occupop rate-limit handling. Rollback available throughout.
FAQ
Occupop migration FAQ
Answers to the questions buyers ask most during Occupop migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Occupop migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate Occupop.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Occupop setup and destination — written quote back within a business day.