Migrate from Checkwriters to Recruit CRM & ATS

Checkwriters stores applicants within or alongside employee records. We extract applicant profile fields (name, contact information, work authorization, EEOC data) and map them to Recruit CRM Candidate records. Custom fields on the employee profile discovered with HR Admin access migrate to Recruit CRM custom Candidate fields. Checkwriters hire date, department, and job title map to Candidate custom fields if the employee has been hired; otherwise these remain candidate-stage metadata.

Checkwriters open positions tracked in the recruiting module map to Recruit CRM Job Orders. Position title, department, location, employment type, and job description migrate. Active versus closed status maps to the Recruit CRM job order status field. Checkwriters job categories and openings by location map to Recruit CRM job fields and placement location.

For staffing agencies using Checkwriters, any client organizations tracked in Checkwriters map to Recruit CRM Company records. Company name, address, and industry migrate. For in-house HR teams, the organization itself does not need a Company record in Recruit CRM unless client relationship tracking is desired.

Employee personal and work contact details (email, phone, address) map to Recruit CRM Contact records linked to the relevant Company. For in-house recruiting migrations, employees being tracked as candidates for internal roles map to Candidate records with a separate Contact created for personal emergency contact data.

Checkwriters time-off request records include request date, requested dates, status, and approver. These do not map to a native Recruit CRM object because Recruit CRM is a recruiting platform, not an HRMS. We map time-off request history as timestamped Candidate Notes for internal audit purposes, or as custom date fields on the Candidate record at the customer's direction. PTO balances and accrual data do not migrate to Recruit CRM.

Checkwriters custom fields created at the company level (text, date, dropdown, numeric) are discovered with HR Admin-level access during scoping. Each custom field maps to a Recruit CRM custom Candidate field of the equivalent type. Dropdown fields in Checkwriters migrate as picklist fields in Recruit CRM with the same value options. We require admin-level access to Checkwriters before mapping begins so that no custom field definition is missed.

Checkwriters Document Center stores offer letters, signed agreements, I-9s, and onboarding documents per employee. We extract file references and URLs and map them as attachments on the corresponding Recruit CRM Candidate record. Document visibility restrictions from Checkwriters are preserved as a note. Documents must be exportable from Checkwriters in a supported format (PDF, DOCX) before import.

Checkwriters onboarding workflows (step tracking and document e-signature collection) are available on HR Premier and above. We document every completed onboarding step, the associated document, and the completion timestamp as Candidate Notes and Tasks in Recruit CRM. Recruit CRM does not natively replicate Checkwriters' onboarding workflow engine; we create a checklist structure of onboarding tasks that the recruiting team rebuilds in Recruit CRM and mark each with a note linking to the Checkwriters source record.

Pay stub history and payroll register data in Checkwriters are accessed via the Report Writer module, not a bulk API. Historical payroll data (earnings, taxes, deductions, W-2 history) does not map to any Recruit CRM object because Recruit CRM does not manage payroll. We recommend retaining payroll records in Checkwriters or exporting via Report Writer to a separate payroll archive. We do not attempt to load payroll data into a recruiting platform.

Performance review content (completed reviews, templates, writing-assist suggestions) is an upgrade add-on in Checkwriters and is stored in a proprietary format tied to Checkwriters' review workflow engine. There is no publicly documented export endpoint for review content. We flag this to customers upfront and recommend a parallel manual review process in the destination rather than attempting an automated migration that would produce incomplete or corrupted records.

Checkwriters Report Writer allows admins to build custom reports across multiple report types and export to Excel or CSV. We coordinate with the customer to define the correct report types and date ranges for applicant data extraction, then transform the exported CSV into Recruit CRM's bulk import format. This includes field mapping, type normalization (date formats, picklist values), and deduplication checks before import.

PTO and sick time accrual balances tracked per employee in Checkwriters do not map to any native Recruit CRM object. Recruit CRM is a recruiting and applicant tracking platform and does not manage leave balances or accrual policies. We recommend retaining accrual data in Checkwriters or exporting it to a separate HR archive. If the customer needs accrual records for compliance or audit purposes, we flag this as a separate data extraction task outside the ATS migration scope.