Migrate from SeamlessHR to Crelate

SeamlessHR's applicant records from SeamlessHiring map directly to Crelate's Candidate object. The full name, email, phone, current company, current title, source channel, and application date transfer 1:1. We resolve the Crelate Candidate unique ID at import time for use as the parent reference on all related objects. Any applicant with no email is flagged as a potential duplicate and held in a review queue before insert.

SeamlessHR Employee records do not map to any Crelate object. Crelate is an ATS/CRM with no HRIS or employee record layer. If the customer runs dual systems (Crelate for recruiting, SeamlessHR for payroll and HRIS), we document the split and advise the customer to provision a separate SeamlessHR Lite or Core instance for ongoing employee management. Historical employee records with performance data are flagged as not migratable to Crelate's schema.

SeamlessHR requisitions map to Crelate Jobs. The requisition title, description, location, employment type (full-time, contract), and department transfer. Job status (open, filled, on hold, closed) maps directly. We extract the workflow stage name and stage order from SeamlessHiring to rebuild the equivalent pipeline stage in Crelate's ATS pipeline configuration before migration.

SeamlessHiring stages are an ordered sequence tied to each applicant. We extract stage names, order index, and the stage each applicant has passed through, then configure matching pipeline stages in Crelate's ATS. The candidate's current stage migrates as a Crelate Activity note on the Candidate record since Crelate does not have a native workflow stage history object. Customers who rely on complex conditional stage routing document it during scoping for manual rebuild in Crelate's workflow automation.

SeamlessHR org chart and department hierarchy do not map to Crelate's schema. Crelate has no organizational structure object. If the customer uses departments as job classification metadata, we map the SeamlessHR department name to a Crelate custom field on the Job record. Parent-child reporting relationships are preserved as a written document for the customer's admin to re-establish in their retained HRIS platform.

SeamlessHR leave balances, entitlement policies, and request history have no Crelate equivalent. Crelate is ATS-only. Leave data is flagged as out-of-scope during discovery. If the customer uses SeamlessHR specifically for leave management and Crelate for recruiting, we recommend retaining SeamlessHR Lite for leave management or migrating leave data to a dedicated leave management platform as a parallel engagement.

Historical payslips and payroll runs do not map to Crelate's ATS schema. If the customer runs SeamlessHR payroll and Crelate recruiting in parallel, payroll records stay in SeamlessHR. We document the payroll module boundary explicitly in the migration scope and flag that compensation data attached to candidate records (for contractor or contract-to-hire placements) may need to be stored as a custom field on the Crelate Candidate record rather than in a native payroll object.

SeamlessHR custom fields on requisitions require schema extraction before migration. We retrieve the field definition list via API first (field name, field type), pre-create matching custom fields in Crelate Job, then pull the values per requisition record. If a custom field type (date, number, text, dropdown) has no direct Crelate equivalent, we map to the nearest Crelate type and flag the mapping in the reconciliation report. Customer must pre-create any custom fields in Crelate before the migration run begins.

SeamlessHR custom fields on employee profiles map to Crelate Candidate custom fields if the employee was previously an applicant in SeamlessHR. We extract the field definition list first, pre-create matching custom fields in Crelate Candidate, then import values. This mapping applies only to applicants with an existing SeamlessHR candidate record; pure HRIS custom fields on employee-only records are out of scope.

Candidate documents (resumes, cover letters, portfolio files) attached to SeamlessHR applicant profiles migrate as Crelate Candidate attachments. We extract document metadata and binary blobs, map the file name, and attach to the corresponding Crelate Candidate record. Large attachments (over 10 MB per file) are flagged for manual re-upload if Crelate's file size limits are encountered. We preserve the original file name and upload timestamp.

SeamlessHR performance and potential ratings, review cycles, and goal data do not map to Crelate's ATS schema. This data is available on SeamlessHR Core tier and above. We flag it as out-of-scope and recommend the customer retains SeamlessHR Core or migrates performance data to a dedicated performance management platform (Lattice, BambooHR, Workday) as a parallel engagement.

SeamlessHR approval chains and routing logic do not migrate. We do not migrate workflow definitions. We deliver a written inventory of every configured approval chain in SeamlessHR (which stages require approval, who the approver role is, what conditions trigger escalation) so the customer's admin can rebuild equivalent automation in Crelate's workflow builder post-migration.