Migrate from Namely to Crelate

Namely Employee records map to Crelate Contact records. We extract employee demographics (name, email, phone, address, hire date, termination date, employment status, job title, department) and write them to Crelate Contact fields. The Contact's Status field is set to Hired to reflect the employment relationship. Employee ID from Namely is preserved as an external ID field for cross-reference. We do not convert Employees into Crelate Job Candidates unless the customer specifically wants to track former employees as talent pipeline contacts.

Namely compensation history (salary, bonus, equity, compensation effective-dates) does not have a native Crelate equivalent. We extract the full compensation timeline as a JSON-structured document, attach it as a Note on the corresponding Contact record, and preserve effective-dates as a readable table within the note body. Year-to-date earnings at termination (for offboarded employees) migrate as a separate note with type = Compensation Summary.

Namely benefit elections (health, dental, vision, 401k) reference carrier-specific plan IDs that have no equivalent at Crelate. We extract enrollment records and produce a Benefits Summary note on each Contact listing the election types and coverage tiers. We flag this as a re-enrollment prerequisite: the customer must configure equivalent benefit plans at their new carrier before importing enrollment data. Benefits data is not migrated into Crelate because Crelate has no benefits administration module.

Namely payroll runs (earnings, deductions, taxes, direct deposit details, YTD figures) do not map to any Crelate object. We export payroll history as a structured CSV and PDF per employee, attach the summary as a Note to the Contact record, and deliver the full payroll history archive as a separate file set. The customer's new payroll platform (ADP, Gusto, Rippling, Paychex) is the authoritative destination for payroll data. We flag payroll export as a prerequisite discovery item before migration.

Namely PTO, sick leave, and accrual balances migrate as a Note on each Contact. For accrual-based policies, we export current balance, accrual rate, and accrual history. For unlimited PTO policies, there is no balance record to export since no tracking occurs in Namely; we recommend exporting a policy summary letter as a placeholder. Crelate has no time-off tracking module; balance data is preserved as a reference document for the customer's new HRMS or payroll platform.

Namely departments, cost centers, and reporting hierarchies map to Crelate Company records for organizational units and Contact hierarchy links for reporting relationships. The top-level department becomes a Crelate Company with type = Department; child departments become child Companies. Manager relationships (employee to manager) are established via the Contact's ReportsTo field. We preserve the full org chart structure as a Crelate Company hierarchy for reference.

Namely performance ratings, review cycles, goals, and feedback do not have a Crelate equivalent. We extract review history as a structured document per employee and attach it as a Note with type = Performance Summary on the Contact record. The note includes rating scores, review period, reviewer name, and goal completion status. Crelate is a recruiting ATS and does not support performance management workflows; the review archive is preserved for reference in the new HRMS.

Namely employee documents (I-9s, tax forms W-4 and I-9, offer letters, contracts, performance reviews) are stored as file attachments in the Documents module. File naming in Namely follows inconsistent conventions. We normalize naming during extraction using employee ID and document type conventions (e.g., [NamelyEmployeeID]_I9.pdf). Document metadata (upload date, uploader) is preserved as a JSON sidecar. Each file attaches to the corresponding Crelate Contact record via the Document module. Binary blob integrity is verified by checksum before and after transfer.

Namely supports custom properties on employee records. We discover all active custom field definitions via the Namely API before migration and map them to Crelate Contact custom fields. Crelate supports custom fields on Contact, Company, and Opportunity via its custom forms and field mapping feature. We pre-create the equivalent custom fields in Crelate (with type matching: text, number, date, picklist, checkbox) before importing any employee data. Field-level validation rules in Crelate are temporarily relaxed during migration to prevent import rejection.

Namely approval chains and automation rules are not structurally portable to Crelate or any other ATS. We export a written inventory of every active Namely Workflow specifying its trigger conditions, approval steps, assigned approvers, and automation actions. The inventory is delivered as a structured document that the customer's HR and IT teams use to rebuild equivalent workflows in their new HRMS (not in Crelate, which lacks HR workflow automation). This inventory is out-of-scope for migration but is included in the handoff package.

If the customer used Namely's onboarding module to create job postings or track requisitions, we map these to Crelate Job records. The Namely job title, department, hiring manager, and requisition status map to Crelate Job Title, Department, Hiring Manager (as Contact), and Status fields. Open and closed date from Namely map to Crelate's date fields. Inactive or completed jobs are migrated as archived Job records for historical reference.

If the customer used the optional Namely ATS module for candidate tracking, we map Namely candidate applications to Crelate Candidate records and their associated Job submissions. The mapping preserves candidate contact information, application status, source, and submission date. Interview stages from Namely map to Crelate pipeline stages. Interview notes and scorecards are preserved as Note attachments on the Crelate application record.