Migrate from Checkwriters to Crelate

Checkwriters job postings map to Crelate Job Post records. The job title, description, location, employment type, and department fields transfer directly. Job board distribution settings do not carry forward because Crelate manages its own job distribution integrations. We extract the posting date and close date from Checkwriters Report Writer exports and set the Crelate Job Post status accordingly. Any active job postings in-flight at cutover are prioritized in the first migration batch.

Checkwriters candidate profiles map to Crelate Person records. Core fields including name, email address, phone number, current employer, and current title transfer directly. Application status history stored in Checkwriters as a series of status-change events is collapsed into the most recent status and stored as a custom field on the Crelate Person record for audit. Source attribution (where the candidate originated) migrates to a Crelate custom field.

Checkwriters applications link a candidate to a specific job posting and track status through the hiring pipeline (Applied, Screening, Interview, Offer, Hired, Rejected). We map these status values to Crelate's Application status taxonomy. Application date and last-modified date transfer as Crelate creation and modification timestamps. Notes attached to an application in Checkwriters migrate as Crelate Activity Notes linked to the Application record.

Interview notes, interviewer feedback, and scoring records stored in Checkwriters migrate as Crelate Note records. We resolve the note's parent record by matching the interview's candidate and job references from the Checkwriters export. Interviewer attribution (name, role, date) maps to Crelate's note metadata fields. Score values and rating fields migrate to custom fields on the Crelate Note or Application record depending on the customer's review structure.

Checkwriters custom fields on employee and candidate profiles require HR Admin-level permissions to enumerate in full. We request admin-level access to the Checkwriters tenant during scoping to extract the complete custom field registry before designing the Crelate destination schema. Each Checkwriters custom field type (text, date, dropdown, numeric) maps to the equivalent Crelate custom field type on the matching core record. Dropdown values from Checkwriters become Crelate picklist options, and we validate that all values in the migrating dataset are represented in the destination picklist before import.

Resume files, cover letters, portfolio attachments, and signed forms stored in the Checkwriters Document Center and attached to candidate records migrate as Crelate File Attachments linked to the corresponding Person record. We extract file references and the original file name and restore them in Crelate. Visibility restrictions on documents in Checkwriters are not enforceable in Crelate's permission model and are flagged to the customer's admin during the permissions handoff.

Employee records (demographics, job title, department, hire date, employment status, salary, pay frequency) are Checkwriters HRMS core data. Crelate is an ATS and recruiting CRM that does not have a payroll, benefits, or employee relations data model. We do not migrate employee HRMS data into Crelate. The customer maintains Checkwriters or a dedicated HRMS for all employee records and uses Crelate for recruiting only. We document this boundary explicitly in the scoping report and confirm the customer's parallel-system strategy before migration begins.

Payroll items, time-off accruals, benefit elections, deduction histories, and pay stub records are Checkwriters HRMS data with no equivalent object in Crelate's recruiting schema. These records cannot be migrated into Crelate and must remain in Checkwriters or a replacement HRMS. We flag this boundary clearly in the discovery report and recommend the customer retains Checkwriters access for payroll history and compliance records or selects a parallel HRMS before cutover.

Checkwriters onboarding task records and completed document signatures do not export through any documented path. Completed onboarding tasks in Checkwriters cannot be reconstructed as structured records in Crelate. We flag this to customers during discovery and recommend a parallel manual onboarding setup in Crelate using their onboarding templates. Checkwriters onboarding document files can be extracted and attached to the corresponding Crelate Person record as part of the document migration, but the step-completion workflow history does not carry forward.

Performance review templates, writing-assist content, and completed review records are stored in a proprietary Checkwriters format with no documented export API. We do not attempt an automated migration of performance review content because it produces incomplete or corrupted records. We flag this to customers with the Performance Reviews upgrade and recommend a parallel review cycle setup in their destination HRMS or performance management tool post-migration.

Time-off request history and accrual balances are HRMS records managed through Checkwriters. Crelate does not have a time-off tracking or accrual management data model. These records remain in Checkwriters or a replacement HRMS. Request records with pending or in-progress status at cutover are flagged as requiring admin resolution before the Checkwriters access is adjusted.

The Report Writer report definitions built by the customer's HR Admin serve as our extraction blueprint during migration. We capture the full list of Report Writer exports the customer has built for recruiting data and use them to reproduce the data pull in Crelate's reporting environment post-migration. The report definitions themselves do not transfer because Crelate's reporting engine uses a different data model and field structure.