Migrate from Fingercheck to Crelate

Fingercheck Employee records with a hiring-stage status (applicant, new hire, onboarding) map to Crelate Candidate records. The Fingercheck HireDate becomes the Crelate application date, and the employment status property determines whether the record enters Crelate as an active candidate or a placed candidate. We flag records where the Fingercheck employment status indicates an active employee versus an applicant, because the mapping semantics differ: Fingercheck bundles all employee statuses in one object, while Crelate separates candidates (pre-placement) from placed placements.

Fingercheck Employee fields for name, address, phone, email, and date of birth map to the corresponding Crelate Candidate fields. Fingercheck's demographic and background data (where captured in the application form) migrates to Crelate's candidate profile fields. SSN and DOB are flagged for secure file delivery rather than bulk import because Crelate's candidate import API does not accept SSN and most ATS platforms require re-entry of sensitive identifiers through the employee self-service portal.

Fingercheck job postings created in the Hiring module map to Crelate Job Orders. The posting title, description, department assignment, and job board distribution settings export from Fingercheck and import into Crelate as active Job Orders with status, internal/external flag, and hiring lead preserved. We map the Fingercheck division or department assignment to a Crelate Department custom field or tag since Crelate Job Orders do not have a native department hierarchy.

Fingercheck captures application form responses during the hiring process. These map to Crelate Submissions, which represent the association between a Candidate and a Job Order with an application status and timestamp. We map the Fingercheck application status (applied, screened, interview, offer, hired, rejected) to the corresponding Crelate Submission status value. Historical submission records are preserved with their original application dates.

Fingercheck Custom Fields defined in SETUP > HR > Custom Fields (which include hiring-specific fields like source, referral, and background check status) map to Crelate custom fields. We export the full custom field schema including field type (text, dropdown, date, checkbox) and required status, then pre-create the matching Crelate custom fields before import. Customers with more than 20 custom fields in Fingercheck should expect a mapping review session to confirm which fields apply to the recruiting scope versus general HR data that has no Crelate analog.

Fingercheck HR Documents (resumes, I-9s, certifications, onboarding paperwork, policy acknowledgements) stored per Employee map as attachments to the corresponding Crelate Candidate record. We export the document file, filename, and document type, then attach to the Candidate in Crelate via the file upload API. I-9 and government ID documents are handled separately from the bulk import as secure-delivery files requiring the customer's HR admin to re-upload directly in Crelate.

Fingercheck Divisions and Cost Centers (up to 5 fields per employee) represent organizational and labor allocation structures. Crelate has no native Division or Cost Center object. We export all Division and Cost Center values and map them to Crelate Tags on the Candidate record, or to a custom multi-select field if the customer prefers structured filtering over tag-based segmentation. The customer chooses the strategy during scoping.

Fingercheck Pay Groups (salaried, hourly, contractor) drive payroll tax calculation logic in Fingercheck but have no equivalent in Crelate's ATS data model. We export Pay Group values as a custom candidate field (pay_type__c) if the customer needs the historical payroll classification visible on the Candidate record in Crelate. We explicitly document that Crelate does not use this data for any payroll processing and the payroll implication must be handled at the destination payroll system.

Fingercheck PTO accrual balances and carryover rules do not migrate to Crelate. Crelate is an ATS and recruiting CRM with no HR or benefits administration module. We export a read-only accrual snapshot as a CSV deliverable for the customer's HR admin to retain or import into their payroll destination. We flag this as a data gap during scoping so the customer can plan for parallel PTO tracking during the migration window.

Fingercheck Time Card records (punch-in/out timestamps, overtime flags, break data, and job costing associations) do not migrate to Crelate. Crelate has no time tracking module and time card data would be meaningless in the ATS context. We export a date-range-bounded time card export as a CSV deliverable for the customer's payroll records. The customer confirms the export date range during scoping aligned to the current pay period boundary.

Fingercheck Workflow Automations for hiring sequences, onboarding triggers, offboarding tasks, and HR notifications do not export via API and have no direct Crelate equivalent in the Business base tier. We document every active Fingercheck Workflow with its trigger, conditions, downstream actions, and a recommended Crelate Automation or Sequence rebuild approach for customers on Business Plus or Enterprise. This is a customer action item delivered as part of the migration handoff package, not a FlitStack AI deliverable to rebuild automations.

Fingercheck state and federal tax withholding tables per employee do not migrate to Crelate. Crelate is an ATS with no payroll tax processing capability. The Connecticut tax table bug documented in Fingercheck (null state tax election blocking employee activation) is audited during the export phase: we flag any Employee record with missing or null state tax withholding data before migration so the customer can correct elections in Fingercheck before exporting.