Migrate from Occupop to Crelate

Occupop Jobs map to Crelate Position records. Each Job carries its title, description, department, location, and active/closed status. We preserve the original Occupop Job ID as a Crelate custom field for audit traceability. Board distribution history (Indeed, LinkedIn, Reed, etc.) is exported as a structured list and surfaced post-migration for manual re-posting since Crelate does not track board distribution natively.

Occupop Candidates map to Crelate Person records. We preserve name, email, phone, address, stage history, and the original Occupop Candidate ID. Each Candidate is linked to the corresponding Crelate Position via a Job Application relationship. Stage history (Applied, Screening, Interview, Offer) migrates as structured data mapped to Crelate's stage configuration.

Occupop's AI screening score is a numeric value computed from CV-to-job-description matching. Crelate has no native AI scoring object, so we create a custom numeric field on the Person (Contact) record before migration. The score migrates as a whole number with the original Occupop rank preserved as a secondary custom field. This allows the customer's team to re-evaluate scores using Crelate's own AI tools post-migration.

CV files are exported as raw binary files with the candidate's email as the filename key. We import each CV as an attachment on the corresponding Crelate Person record. Crelate's document storage supports PDF and common office formats. We validate file integrity post-migration by spot-checking attachment presence against the source export manifest.

Occupop's stage sequence per Job (e.g. Applied, Phone Screen, Interview, Offer) maps to Crelate's Pipeline stage configuration. We read the ordered stage list from each Occupop Job, create the corresponding stages in Crelate's Pipeline settings, and map candidate movement records to stage entries with timestamps. Customers choose whether to preserve historical stage-entry timestamps or use the migration date.

Occupop Users (Admin, Hiring Manager, Recruiter, Viewer) map to Crelate Users by email match. We flag any Occupop role with no Crelate equivalent (e.g. Viewer in Occupop) and recommend the closest Crelate role during scoping. Occupop's unlimited-seat model means large hiring teams may have more users than the Crelate 5-seat minimum; we reconcile this with the customer before migration to avoid provisioning users that will not be activated.

Interview scorecard responses and free-text feedback from Occupop migrate to Crelate Notes attached to the Person record. We preserve the feedback author, date, and score values as structured Note metadata fields. Crelate does not have a native interview-feedback object; Notes provide the closest equivalent for maintaining evaluation history.

Occupop Custom Fields are arbitrary key-value pairs defined per tenant. We detect all custom field definitions during export, map them to Crelate custom fields on the Person record (as Text, Numeric, Date, or Picklist types per the data), and pre-create them in Crelate before any data loads. Occupop's unlimited custom fields per Candidate may exceed typical Crelate usage; we flag any field that requires a non-standard type mapping.

Occupop tracks which job boards a Job was distributed to and the posting date. This board-distribution data is not a standard field in Crelate. We export it as a structured sidecar JSON file per Job and deliver it alongside the migration so the customer's admin can re-create distributions manually in Crelate's job posting tool or via API.

The AI screening rank (where the Candidate sits within the Job's candidate pool) migrates as a custom numeric field alongside the raw score. Both score and rank are non-destructive: they preserve the Occupop evaluation context without requiring the customer's team to re-score manually in Crelate.

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 API. We explicitly exclude these from migration scope and direct customers to export them directly from Cezanne HR before initiating any data migration. This is a platform boundary, not a data loss gap.

Occupop stage-triggered workflow configurations do not migrate as automation code. Crelate's workflow builder uses a different trigger-and-action model. We audit every active Occupop workflow configuration and deliver a written inventory with each workflow's trigger, conditions, actions, and the recommended Crelate equivalent. The customer's Crelate admin rebuilds these post-migration.