Migrate from Sloneek to Recruit CRM & ATS

Sloneek ATS Candidates map directly to Recruit CRM Candidates. We preserve the full candidate profile including name, contact details, current title, company, location, and any sourced resume. GDPR consent flags stored in Sloneek's ATS consent fields migrate to Recruit CRM's candidate_consent object with consent type and timestamp preserved. Pipeline stages from Sloneek (Applied, Screening, Interview, Offer, Hired, Rejected) map to equivalent Recruit CRM pipeline stages or custom stages that we configure before import.

Sloneek job positions (ATS module) map to Recruit CRM Jobs. The job title, job description, requirements, salary range, and location fields migrate directly. We map Sloneek job status (Active, Paused, Closed, Draft) to Recruit CRM job status equivalents. Active job positions are imported first so that candidate-to-job associations can be resolved at import time.

Sloneek's ATS pipeline stages (configurable per customer) map to Recruit CRM pipeline stages. We extract the customer's Sloneek pipeline configuration during scoping and create matching pipeline stages in Recruit CRM before any candidate import begins. Stage probability and stage ordering are preserved to maintain pipeline health reporting continuity.

Candidate resumes uploaded to Sloneek ATS migrate as file attachments in Recruit CRM. We extract resumes in their original format (PDF, DOCX, DOC) and attach them to the corresponding Candidate record. Sloneek's PDF-only document restriction applies to its Core HR trust box, not to the ATS resume upload module, so we import resumes in their source format without pre-conversion.

Sloneek employee profiles from Core HR (name, contact, job title, department, location) do not have a direct equivalent in Recruit CRM which is candidate and client-centric. If the migration scope includes internal recruiter profiles or hiring manager contacts, we map them to Recruit CRM Users or Contacts depending on whether they are system users or client-side stakeholders. Core HR employee data that is purely operational (payroll, benefits, manager hierarchy) is excluded as it has no Recruit CRM counterpart.

Sloneek Companies from Core HR map to Recruit CRM Clients when the company is a client of the recruitment agency. The company name, address, website, and industry fields migrate directly. If the Sloneek company is an employer brand or a candidate's current employer rather than a recruiting client, it may be stored as a candidate attribute or tagged note rather than a top-level Client record.

Sloneek trust box documents (employment contracts, compliance records, certifications) migrate as file attachments to the relevant Candidate or Contact record in Recruit CRM. Non-PDF documents stored in Sloneek must be pre-converted because Recruit CRM accepts multiple formats while the source Sloneek export may contain mixed-format files. We flag non-PDF documents before migration and alert the customer to pre-conversion requirements.

Sloneek absence records (time-off requests, accrual balances, approval statuses) have no equivalent object in Recruit CRM, which is an agency recruitment tool focused on candidates and placements rather than internal HR operations. We exclude absence data from the migration scope and document it in the handoff report so the customer's HR team can maintain absence records in a separate HR system post-migration.

Sloneek performance reviews, 360-degree feedback records, goals, and review cycles have no counterpart in Recruit CRM. These objects are excluded from the migration scope. If the customer has used Sloneek's ATS for performance-linked candidate assessments, those scoring records can be preserved as custom fields on the Candidate object rather than as standard performance review objects.

Sloneek payroll module salary, bonus, deduction, and compensation history records have no equivalent in Recruit CRM, which does not manage payroll or employee compensation. We exclude payroll data from the migration scope and note that any compensation data linked to placed candidates should be captured as candidate placement notes or a custom field rather than standard Recruit CRM objects.

Sloneek custom fields on ATS Candidates migrate to Recruit CRM custom fields on the Candidate object. We discover the full custom field schema during scoping, map each field to its Recruit CRM equivalent with matching field type (text, number, date, picklist, multi-select, checkbox), and create the destination fields before migration begins. Custom field values transfer as typed values without reformatting.

Sloneek attendance records are excluded from migration to Recruit CRM. Recruit CRM does not have an attendance or time-tracking module. Sloneek's parallel Attendance 2.0 schema migration (old and new attendance running simultaneously) is a source-side concern we flag during scoping but does not affect the destination object model.