Migrate from Fingercheck to Recruit CRM & ATS

Fingercheck Employee records map to Recruit CRM Candidate profiles as the primary migration anchor. We extract FirstName, LastName, PersonalEmail, MobilePhone, Address, and DateOfBirth. The Employee HireDate maps to a custom Candidate field original_hire_date__c as a reference marker, not an active employment field. SSN and DOB cannot migrate via Recruit CRM's import API due to PII policy; we deliver these in an encrypted secure file and document the employee self-service re-entry workflow required post-migration. Employment status (FullOrPartTime, ExemptFromOT) maps to custom Candidate fields. Pay rates, PayType, and tax withholding elections have no equivalent in Recruit CRM's candidate schema and are flagged in the gap report.

Fingercheck Divisions represent organizational units (departments, locations, business segments) assigned to each Employee via DivisionID. Recruit CRM has no native Division equivalent, so we map Division names to Candidate Tags or to a custom multi-select field division__c. Where the customer uses Division for multi-state workforce segmentation, we recommend creating a corresponding Recruit CRM Tag group and applying tags during import. If more than 5 Divisions exist, we discuss scope trade-offs between tag density and usability.

Fingercheck PayGroup determines pay structure (salaried vs. hourly) and drives payroll tax logic. Recruit CRM has no native pay structure field on Candidate. We create a custom field pay_group__c (text or picklist) on Candidate and migrate the PayGroup label as a string value. The customer decides whether to expose this field in Recruit CRM's candidate pipeline view or keep it as a hidden reference field.

Fingercheck supports up to 5 Cost Center fields per Employee for job costing and labor allocation. Recruit CRM has no native cost center or job costing structure on Candidate records. We create up to 5 custom fields (cost_center_1__c through cost_center_5__c) or map them to Candidate Tags depending on the customer's intended use. If the staffing agency uses cost centers to track placements by client division, the customer may prefer Tags mapped to Recruit CRM's Client object instead.

Fingercheck Custom Fields are customer-defined in name, type, and required status. We export all custom field definitions and their values per Employee record during discovery. We create matching custom fields in Recruit CRM with equivalent data types (text, number, date, picklist, checkbox) and populate values during the Candidate import. Custom fields that contain payroll, tax, biometric, or benefits data are flagged in the gap report as having no candidate-management use in Recruit CRM and may be omitted from migration at customer discretion.

Fingercheck HR Documents (I-9s, certifications, policy acknowledgements, onboarding paperwork, employment contracts) are stored per Employee. Recruit CRM's document model is limited to candidate resume attachments and portal-uploaded files. HR document files cannot migrate into Recruit CRM's document architecture. We recommend the customer exports HR documents as a separate file archive (PDF bundle per employee) for retention and compliance purposes outside the ATS migration scope.

Fingercheck Time Card records capture punch-in/out timestamps, breaks, overtime flags, and job costing associations per pay period. Recruit CRM has no time tracking module and no fields to store punch history, overtime calculations, or timesheet data. Time card data does not migrate. The migration gap report documents the date range and total hours per employee for the customer's payroll records to carry forward manually into their payroll system post-migration.

Fingercheck scheduling handles shift assignments, conflict detection, and shift notes for office and field workers. Recruit CRM does not have a scheduling module. Schedule records do not migrate. If the customer uses Recruit CRM for placement tracking and needs to reference historical schedule data for temp-to-hire records, we create a custom text field shift_notes__c on the Candidate record as a free-text container for a summary of recent schedule history.

Fingercheck stores state and federal tax withholding elections per Employee, including state-specific table references and allowances. Recruit CRM has no tax withholding module. Tax election data cannot migrate. A documented Fingercheck bug affecting Connecticut tax table saves caused null withholding elections in some Employee records; we audit tax fields during export and flag any null or incomplete state tax election records for the customer to correct manually post-migration before running payroll in the destination payroll system.

Fingercheck tracks PTO accrual rates, carryover rules, and current balances per Employee. Recruit CRM has no PTO or accrual management module. Accrual balance data cannot migrate into Recruit CRM. We export accrual balances as of the migration date and deliver them as a separate reference file for the customer's payroll or standalone PTO administration system. If the customer adopts a new payroll platform post-migration, the accrual file supports balance carryforward entry.

Fingercheck integrates with QuickBooks Online for payroll journal exports. These export configurations (accounting codes, export type, company mapping) are Fingercheck-specific and have no equivalent in Recruit CRM, which is an ATS not a payroll system. We document the existing export configurations as a reference file for the customer's accountant or bookkeeper to re-establish in their new payroll system. QuickBooks integration should be migrated separately if the customer adopts a new payroll platform.

Fingercheck Workflow Automations handle hiring sequences, onboarding triggers, offboarding tasks, expense approvals, and HR notifications. Workflow definitions do not export via the Fingercheck API. We document the full list of active workflows, their trigger conditions, and downstream actions during discovery so the customer can rebuild them manually in their new system. This is scoped as a customer-admin action item, not a FlitStack AI deliverable.