Migrate from Sesame HR to Crelate

Sesame HR employee records with active recruitment activity map to Crelate Person (Contact). We extract first name, last name, email, phone, department, job title, hire date, employment status, and contract type. Employment status (active, inactive, contractor) and contract type (full-time, part-time) are stored as Crelate tags on the Person record. The Person record is the anchor for all candidate and employee data in Crelate's schema.

Sesame HR candidate records associated with open vacancies map directly to Crelate Person records. We extract full name, email, phone, application date, current pipeline stage, source channel, and any notes. Crelate's Person object holds the candidate's profile; the vacancy association is handled through the Opportunity linkage.

Sesame HR vacancies map to Crelate Opportunities. We extract job title, job description, department, location, employment type, salary range, and vacancy status. Crelate Opportunity.Name is required; we use the vacancy title as the Opportunity Name and store the original Sesame HR vacancy ID in a custom field. Vacancy status (open, closed, on-hold) maps to Crelate Opportunity stage values that we configure in the destination during schema setup.

Each Sesame HR vacancy pipeline maps to a Crelate Opportunity pipeline with custom stage values. We configure the stage names, probability weights, and stage order during Crelate setup before migration begins. Closed Won maps to placement or hired status; Closed Lost maps to rejection or decline. Stage sequence is preserved to maintain pipeline integrity.

Crelate links candidates (People) to jobs (Opportunities) through a submission or application record. We create the Person-to-Opportunity association at migration time by resolving the Person ID from the candidate import and the Opportunity ID from the vacancy import. This linkage is critical for tracking which candidates applied to which roles and preserving pipeline history.

Sesame HR stores employment status (active, inactive, contractor) and contract type as properties on Employee and Candidate records. We extract these values and create Crelate tags under the Default category. Contract type (permanent, temporary, freelance) becomes a tag on the Person record. We deduplicate tags during scoping and confirm the customer's preferred taxonomy before import.

Sesame HR employee properties (nationality, date of birth, emergency contact, employee ID) that have no direct Crelate standard field become custom fields on the Person record. We create the custom fields during schema setup before migration, then populate them from Sesame HR API responses. Crelate supports Text, Number, Date, and Picklist custom field types via its Settings | Core Records | Contacts path.

Clock-in/out records, overtime flags, and break deductions have no native Crelate equivalent. We export time entries as a structured CSV with employee identifier, date, clock-in timestamp, clock-out timestamp, hours worked, overtime hours, and break deductions. The CSV schema is documented and handed off for the customer's admin to ingest into their time-tracking or payroll system.

Leave request history, balance snapshots, and absence type records are exported as CSV. Fields include employee identifier, leave type, start date, end date, status (approved, pending, rejected), and remaining balance. Crelate's ATS schema does not include a native PTO or absence management layer, so these records are delivered as a reference package rather than live objects.

Sesame HR employee documents (contracts, ID copies, certifications) are extracted as binary files from the API. We create a Crelate Note on the corresponding Person record and attach the file, preserving the original filename and upload date. Crelate's file attachment model uses ContentDocument and ContentDocumentLink; we resolve the Person ID before attaching to ensure the document links to the correct record.

Sesame HR exposes a hierarchical org chart structure. We extract it as a flat list of manager-subordinate relationships and create Crelate tags on Person records to represent reporting lines. Each Person record receives a manager tag indicating their direct supervisor. Crelate does not have a native organizational chart visualization; we use tagging to encode the hierarchy so it is searchable within the platform.

Sesame HR payroll preparation exports (hours worked, overtime accruals, deductions, net pay estimates) are exported as structured CSV. Fields include employee identifier, pay period, regular hours, overtime hours, gross pay, deductions by category, and net pay. Crelate has no payroll processing layer; the CSV is packaged with the migration and documented for ingestion into the customer's external payroll system.

Sesame HR department assignments and job titles are extracted from Employee records and mapped to Crelate tags on the Person record. Department becomes a tag; job title maps to the standard Crelate Person.Title field where available. We validate department values against the destination to avoid orphan entries and deduplicate before import.

Sesame HR custom fields on Employee records are read during discovery and mapped to Crelate custom fields on Person. Picklist and multi-select custom properties use Crelate Picklist custom fields with explicit value options agreed with the customer during scoping. Boolean and date custom properties map directly to Crelate's corresponding field types.