Migrate from SeamlessHR to Recruit CRM & ATS

SeamlessHR applicant records map to Recruit CRM Candidates. We pull the full applicant profile including contact details, employment history, skills, and any attached documents. Recruit CRM's AI resume parsing is applied post-import rather than migrated as parsed data, since the parsed output is generated at import time. Candidate status from SeamlessHR (application stage) maps to Recruit CRM's pipeline stage with the original stage name preserved in a custom field for audit.

SeamlessHR job requisitions map to Recruit CRM Job records. We extract requisition title, description, requirements, department, location, salary range, and any posted date. Custom fields on requisitions require schema extraction first — SeamlessHR does not generate an automatic import template for custom properties, so we retrieve the field definition list via API, construct the mapping table, and apply it before the data import run. Any custom field not pre-created at the destination is flagged and skipped unless the customer creates it.

SeamlessHiring workflow stages are an ordered sequence stored separately from the requisition record. We preserve stage names, stage order, and the stage history for each applicant — which stages each candidate has passed through and when. Recruit CRM's Kanban pipeline stages are configured to mirror the SeamlessHR stage names and order so the existing workflow is recognizable post-migration. Stage probability and stage-level automation triggers are noted separately for the customer's admin to configure in Recruit CRM.

If SeamlessHR stores client companies for recruitment purposes, they map to Recruit CRM Client records. The mapping depends on how SeamlessHR structures its recruitment client data — some SeamlessHR deployments use the Company object for both internal HRIS and external recruitment clients. We separate internal organization structure (mapped to Recruit CRM's Organization object) from external recruitment clients during scoping. The customer confirms the split during discovery.

SeamlessHR's core Employee object has no native equivalent in Recruit CRM, which tracks candidates and jobs rather than internal staff records. We do not migrate active employee profiles into Recruit CRM. For organizations that used SeamlessHR to store both candidate records and employee records, we extract active employees as an archived CSV with field mapping, flag them for import into a separate HRMS destination, and document the mapping for the customer's HR admin to action post-migration.

Exited employees in SeamlessHR use a separate export path from active employees — a known gotcha where exited records require a distinct menu action and can be missed if not explicitly requested. We pull exited records with termination date, final compensation, and any attached documents. These export as an archived dataset with full field mapping rather than loading into Recruit CRM, since Recruit CRM does not model exited employee status. Historical payroll records tied to exited profiles are flagged for separate archival handling.

Leave balances, entitlement policies, accrual rates, and leave request history are not migratable to Recruit CRM because Recruit CRM has no leave management module. We extract leave data as a structured CSV export for the customer to load into their chosen HRMS destination or archive for compliance purposes. Pending leave requests are flagged at cutover so the customer's HR admin can resolve them before or after migration.

Historical payslips, payroll runs, and compensation data live in SeamlessHR's integrated payroll module and have no equivalent in Recruit CRM's ATS-and-CRM architecture. We do not migrate payroll records into Recruit CRM. We extract payroll data as a structured export with full compensation history, payslip metadata, and statutory deduction records for archival. The customer should verify payroll data retention requirements in their jurisdiction before finalizing the export scope.

Performance ratings, review cycles, goals, and potential matrix data from SeamlessHR's Core tier do not map to Recruit CRM, which has no performance management module. We extract review cycle data and rating history as a structured export. Succession planning visibility and performance history should be preserved in a separate HRMS destination if required for compliance or talent management purposes.

SeamlessHR's org chart and hierarchy (parent-child reporting relationships and department assignments) map to Recruit CRM's Organization object. We preserve department names, reporting chains, and hierarchy levels as structured data. Where SeamlessHR stores internal organizational structure separately from recruitment client data, we ensure the two are not conflated during import.

Employee documents such as contracts, ID copies, and qualifications attached to SeamlessHR profiles migrate to Recruit CRM Documents where the related object is a Candidate or Job. We extract document metadata and binary blobs where the API supports attachment retrieval, and map them to the destination document management structure. Documents attached to exited employees or internal HR records that do not have a Recruit CRM equivalent are exported as an archived package.