Migrate from Checkwriters to Bullhorn ATS & CRM

Checkwriters employee records map to Bullhorn Candidate profiles using name, email, phone, address, and employment status fields. Hire date and termination date from Checkwriters transfer to Bullhorn Candidate custom fields dateHired and dateTerminated. Employment status (active, terminated, re-hire) maps to a Bullhorn custom status field. We use the Candidate email address as the dedupe key during import. Note that Checkwriters employees include full HR data (pay rates, deductions, accruals) that does not have a native Bullhorn equivalent and must be stored as custom fields or excluded from the ATS migration scope.

For Checkwriters employees who have a client-facing role (account managers, sales leads, or HR contacts at client organizations), we map the employee record to Bullhorn Contact. This applies when the migration scope includes internal Checkwriters users who should become Bullhorn users or when internal HR staff are tracked as Contacts in the Bullhorn CRM for client management purposes.

Checkwriters company-level records (the employer organization and any subsidiary companies tracked in the platform) map to Bullhorn ClientCorporation. Company name, address, and EIN map to ClientCorporation name, billingAddress, and a custom field for tax ID. If Checkwriters stores client or vendor companies alongside the employer organization, we separate employer records from external client records before Bullhorn import to avoid client-corporation contamination.

Checkwriters payroll rates are stored with effective check-date ranges (a rate active until 12/31/2100 indicates currently active). We translate these to Bullhorn custom date fields rateEffectiveDate and rateExpirationDate on the Candidate record, with the current hourly or salary rate stored as a numeric custom field. Multi-tier pay structures and spot bonuses from Checkwriters map to additional custom fields (payTier, bonusType, bonusAmount) with an explanatory notes field. If the customer uses Checkwriters for payroll post-migration, we recommend a Bullhorn-to-payroll integration rather than storing live payroll rates in the ATS.

Checkwriters accrual balances (PTO earned, PTO used, sick time balance) map to Bullhorn Candidate custom fields. Accrual policy type (carry-forward vs. annual reset) is stored in a text custom field accrualPolicyType. If the customer has complex accrual histories with multiple accrual types and carry-forward amounts, we create a Bullhorn Accrual custom object with a lookup to Candidate to handle the multi-row-per-employee structure that cannot flatten onto a single Candidate record.

Checkwriters benefit elections (pre-tax, post-tax deductions, health plan enrollment, FSA, HSA) map to a Bullhorn custom object BenefitElection with a lookup to Candidate. Each election record carries plan type, carrier, contribution amount, and effective date. We resolve the carrier and plan ID from Checkwriters' benefit plan records and store them as text fields in Bullhorn because Bullhorn does not have a native benefits carrier management object. Open enrollment period and qualifying life event flags migrate as metadata on each election record.

Historical Checkwriters time-off requests (approved, denied, pending) migrate to Bullhorn Task records with a custom task type TimeOffRequest. Request dates, status, and approver name transfer as custom fields on each Task. Running balance adjustments from approved requests are reconciled against the accrual balance migration. Active pending requests at cutover are flagged for the customer's admin to process in the destination system rather than migrated in a pending state.

Checkwriters Document Center files (offer letters, signed agreements, I-9s) are extracted as file references and re-uploaded to Bullhorn as ContentDocument records linked via ContentDocumentLink to the corresponding Candidate record. Visibility restrictions on Checkwriters documents are noted and mapped to Bullhorn ShareType settings where the platform supports it. I-9 and OSHA compliance documents may have legal retention requirements; we flag these for the customer's HR admin to verify document access and retention policies in Bullhorn post-migration.

Historical pay stub and payroll register data from Checkwriters is extracted via Report Writer CSV export (no API is available for this extraction). We coordinate with the customer to define the correct report types and date ranges before extraction. Pay stub records map to a Bullhorn custom object PayrollHistory with a lookup to Candidate, containing earnings, taxes withheld, deductions, and net pay for each pay period. Because Bullhorn does not have a native payroll object, PayrollHistory is created as a read-only reference dataset. Live payroll runs and W-2 generation must continue in Checkwriters or a separate payroll platform.

Checkwriters custom fields (text, date, dropdown, numeric) created at the company level and assigned to employee profiles require HR Admin-level access to enumerate. We request admin-level access during scoping to discover all active custom field definitions. Each Checkwriters custom field maps to a Bullhorn custom field of the matching type on the target object (Candidate, Contact, or ClientCorporation). Multi-select dropdowns in Checkwriters map to Bullhorn multi-select picklist custom fields. Custom fields with conditional visibility rules cannot be preserved in Bullhorn without manual rebuild.

Checkwriters onboarding workflows (document e-signature collection, step tracking) are available on HR Premier and above and are tied to Checkwriters' workflow engine. Bullhorn does not have a native onboarding workflow engine equivalent. We document the onboarding steps, document collection status, and e-signature completion status for each candidate or employee as a written handoff for the customer's admin to rebuild in Bullhorn's document collection tools or a separate onboarding platform. We do not migrate onboarding as executable code.

Checkwriters Performance Reviews (an add-on module) store completed review records in a proprietary format tied to Checkwriters' review workflow engine. There is no publicly documented export endpoint for review content. We do not attempt automated migration of review templates, writing-assist suggestions, or completed review records because the format is not documented and the risk of corrupted or incomplete records is high. We flag this to customers upfront and recommend a parallel manual review process in Bullhorn or a dedicated performance management platform.