Migrate from Sloneek to Crelate

Sloneek ATS Candidates map to Crelate Contact records. Candidate name, email, phone, resume, GDPR consent flags, and application stage migrate directly. The Sloneek candidate record's pipeline stages (Applied, Screening, Interview, Offer, Hired) map to Crelate's Job Applicant Status on the submission record. GDPR consent storage from Sloneek's ATS module migrates to the Contact's custom consent field, preserving the original consent timestamp and scope. Candidate notes migrate as Crelate Note records attached to the Contact.

When a Sloneek ATS Candidate includes current employer or organization data, we split that into a separate Crelate Company record linked to the Contact via the Company lookup on Contact. The Sloneek candidate's application history against specific job positions migrates as Crelate Opportunity records (representing placements or submissions) with a Job reference. This split is important because Crelate separates person records (Contacts) from organization records (Companies) with a relational model that Sloneek's flat candidate profile does not enforce.

Sloneek Employee records (name, contact info, job title, department, location, hire date, termination date) map to Crelate Contact records with a custom Sloneek migration field (sloneek_employee_id__c) preserving the source reference. Employee reporting lines and department assignments map to Crelate Company records representing the employer organization. Active employee status is preserved; terminated employees are migrated as inactive Contacts with sloneek_status__c = Terminated. The Sloneek organizational hierarchy (departments, cost centers, reporting lines) maps to Crelate Company and hierarchy where the customer uses Crelate for internal employee tracking alongside recruiting.

Sloneek's trust-box documents (contracts, certifications, IDs) migrate as Crelate file attachments linked to the Contact record. We flag every non-PDF attachment during scoping and alert the customer that Sloneek accepts PDF files only for upload — any scanned documents, Word files, or images in the source data must be pre-converted or uploaded manually post-migration. Crelate does not have a native trust-box equivalent; document storage relies on standard Salesforce ContentDocument which lacks built-in e-signature lifecycle tracking. If e-signature tracking is required, the customer should configure DocuSign or similar integration separately.

Sloneek absence records (time-off type, balance, accrual, approval status) migrate to Crelate Activity Forms with custom fields capturing the absence type (Vacation, Sick, Personal), current balance, accrual rate, and original approval date. Sloneek leave types are enumerated during discovery and mapped to Crelate Activity Form categories. Crelate does not have a native time-off accrual engine; we carry the balance snapshot as of the migration date as a read-only custom field on the Activity Form record. Accrual resets post-migration are managed by the customer's HR admin in Crelate's absence management or a connected payroll system.

Sloneek is actively transitioning from the old attendance module to Attendance 2.0, and both schemas coexist in live tenants. We detect which schema applies to each record at export time by inspecting the field structure (old schema uses legacy field names; Attendance 2.0 uses updated field names per Sloneek's December 2025 release notes). Both schemas map to Crelate Activity Forms capturing clock-in, clock-out, total hours, and absence flag. The schema detection step adds a pre-migration data audit of 1-3 business days before the export begins. No attendance history is dropped during the transition window.

Sloneek ATS job positions map to Crelate Job records (position title, department, location, job description) plus an Opportunity record representing the active requisition or headcount opening. Sloneek's position status (Open, On Hold, Filled, Closed) maps to Crelate's Job status. The Opportunity in Crelate tracks the hiring pipeline and is linked to the Job. This split reflects Crelate's recruiting workflow where Jobs represent the position definition and Opportunities represent the active sourcing effort against that position.

Sloneek payroll and compensation records (salary, bonuses, deductions, payroll history) migrate to custom fields on the Crelate Contact record (crelate_salary__c, crelate_bonus__c, crelate_last_raise_date__c). Access depends on the customer's Sloneek plan tier — payroll module access requires the appropriate plan. We verify module availability during discovery and exclude non-existent compensation records from the migration contract upfront. Crelate does not have a native payroll module; compensation data is stored as read-only custom fields for reference by the recruiting team.

Sloneek departments, cost centers, and org chart hierarchies map to Crelate Company records with parent-company hierarchy configured where the customer's org structure has multi-level reporting. Employee reporting lines from Sloneek migrate as Contact-to-Company relationships. Department cost center codes are preserved in custom fields on the Company record. Org chart visualization is not native to Crelate; the customer may configure a third-party org chart tool or use Crelate's reporting to reconstruct the hierarchy.

Sloneek approval chains for time-off, expenses, and document signing do not migrate as code into Crelate because the workflow models are structurally different. We document every Sloneek approval chain during scoping (trigger, conditions, approvers, escalation path) and deliver a written inventory recommending equivalent Crelate configurations using Crelate's Workflow settings, Activity Forms with approval routing, and any third-party approval tools the customer adopts. The customer's admin rebuilds approval rules in Crelate's Settings area post-migration.

Sloneek custom fields on Employee profiles and ATS Candidate records migrate to custom fields on Crelate Contact (the primary recipient object). Crelate supports custom fields on Contact, Company, and Opportunity (the three core record types). We discover the full custom field schema during scoping, map field types to their Crelate equivalents (text, number, date, picklist, checkbox), and pre-create fields in Crelate's Settings | Core Records area before migration begins. Crelate limits Advanced Custom Fields to 10 on the Business plan; Enterprise unlocks higher limits.

Sloneek company assets assigned to employees (equipment, access cards, licenses) are exported as a mapping table (asset ID, asset type, assigned employee, assignment date). In Crelate, we attach this as a structured Note record on the Contact with asset details, or as custom text fields if the asset list is small and static. Crelate does not have a native asset tracking module; the mapping table is delivered as a CSV alongside the migration for the customer's admin to maintain in a separate asset management system.