Migrate from Ceipal ATS to Crelate

Ceipal Applicants map to Crelate People records. The Ceipal applicant record carries structured contact fields (name, email, phone, address), skills, work history, and education parsed from the resume. We preserve parsed fields via API transfer with resume files pushed through Crelate's parsing pipeline, avoiding the CSV bypass issue that leaves Ceipal candidates un-indexed. Ceipal's encrypted applicant_id is recorded in a migration_reference__c field in Crelate for downstream lookup during submission and placement mapping.

Ceipal Submissions link an Applicant to a Job with submission status, submission date, and recruiter assignment. Crelate does not have a dedicated Submission object; instead, submissions are represented as Activity records linked to both the Person and the Job. We resolve the Person and Job foreign keys at migration time via ID-mapping tables, then create Activity records of type Submission linked to both parents. The submission status and date migrate as Activity properties.

Ceipal Job Postings (requisitions) map directly to Crelate Jobs. The Job record carries title, description, location, requirements, and pipeline stages. We map Ceipal job stages to Crelate pipeline stages during migration, with the pipeline stages pre-provisioned in Crelate's settings before data load begins. Ceipal's encrypted job_id is stored in migration_reference__c on the Crelate Job for lookup during submission and placement resolution.

Ceipal Client records (company name, contact info, billing details) map to Crelate Organization records. Organization is created before Person import so that the lookup relationship is satisfied at the moment of Person insert. Address data, industry, and client status migrate as Organization properties. Ceipal's encrypted client_id is preserved in migration_reference__c on the Organization.

Ceipal Leads are distinct from Clients and carry different status fields and source attribution. Crelate does not have a separate Lead object; leads are represented as Organizations or Persons depending on the customer's workflow. We preserve lead status in a custom field ceipal_lead_status__c on the destination record and source attribution in ceipal_lead_source__c for segmentation and reporting in Crelate.

Ceipal Placements tie an Applicant to a Job under a Client, carrying start date, compensation, and billing information. In Crelate, the placement outcome is recorded as an Activity of a designated Placement type linked to the Job, with the Person and Organization referenced through the ID-mapping tables built during scoping. Compensation and start date migrate as Activity custom properties.

Ceipal WorkForce module stores employee profiles, compensation, department, and location as a separate data model from the ATS applicant records. WorkForce is a separate paid tier in Ceipal. If WorkForce data is in scope, we provision a Crelate People profile with HR-specific fields (department, manager, hire date, compensation) mapped from Ceipal WorkForce employee records. The customer chooses whether to create separate ATS (recruiting) and HR (workforce) profiles in Crelate during scoping.

Ceipal WorkForce timesheet records track hours per employee per period with period, hours, and approver metadata. Crelate represents timesheet data as Activity records with time-tracking properties. We map period, hours, and approver to Crelate Activity properties during migration. This object is only in scope if the WorkForce module is active in Ceipal and the customer uses Crelate's time-tracking feature.

Expense tracking in Ceipal WorkForce captures amount, category, employee, and submission date. We migrate expense records with full line-item detail as Activity records of type Expense in Crelate, mapping categories to Crelate's expense category equivalents. This object is only in scope if the WorkForce module is active and the customer uses Crelate's expense feature.

Ceipal stores documents against applicants, jobs, and placements (resumes, offer letters, contracts). We transfer documents as binary blobs via API where supported, falling back to URL-based document references in the Crelate record. Resume files are re-uploaded to trigger Crelate's parsing pipeline for searchable structured data. Other document types attach as linked files to the relevant Person, Job, or Organization record.

Ceipal allows admins to add custom columns to grids and custom properties on Applicants, Jobs, and Placements. These are organization-specific and must be enumerated during discovery. We map each custom field to an equivalent Crelate custom property, preserving the field type (text, number, date, picklist) and any applicable picklist values. Ceipal's per-module custom fields (TalentHire vs. WorkForce) are kept in separate scoping buckets and mapped independently.

Ceipal Owners (recruiters, team leads) map to Crelate User records. We resolve owners by email match against Crelate's user directory. Any Ceipal Owner without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before Person import resumes. Ceipal's encrypted owner_id is preserved in migration_reference__c on the User for audit.