Migrate from Fingercheck to Zoho Recruit

Fingercheck Employee records map to Zoho Recruit Candidate profiles for the name block (FirstName, LastName, MiddleName), contact fields (Email, Phone, Mobile, Address), and employment metadata (HireDate becomes CurrentEmployer start date or most recent position; Department, Division, JobTitle). However, employment status (Active/Terminated), exempt-from-OT designation, and pay type (Salaried/Hourly) have no native Zoho Recruit Candidate fields and must be stored in custom candidate fields pre-created during schema design, or omitted if the customer's Zoho Recruit plan does not include custom field slots.

Fingercheck custom fields defined in SETUP > HR > Custom Fields map to Zoho Recruit custom fields on the Candidate module. We export the full custom field definition schema (name, data type, required flag, picklist values) during discovery, then create matching fields in Zoho Recruit's field builder before migration. Custom field types must be mapped by compatible type: Fingercheck text custom fields map to Zoho Recruit single-line text; picklist custom fields map to Zoho Recruit picklists with values preserved; date custom fields map to Zoho Recruit date fields. Multi-select or checkbox custom fields require pre-creation of multi-select picklists in Zoho Recruit before the import runs.

Fingercheck SSN and DOB are stored in the Employee object but cannot be bulk-imported into Zoho Recruit's Candidate module — Zoho Recruit does not expose these fields in its standard candidate import schema and treats them as sensitive PII that employees enter directly in a self-service portal. We export both fields to a separate encrypted file delivered via secure transfer, document the re-entry workflow required at Zoho Recruit (Employee Self Service portal or admin data-entry screen), and flag the date of export so the customer's HR admin can initiate re-entry before go-live. This is not a FlitStack AI deliverable — it is a customer action item documented in the migration handoff.

Fingercheck Divisions represent organizational units stored as DivisionID on the Employee record. We map Division to a Zoho Recruit custom Candidate field (e.g., Department or HiringTeam) pre-created during schema design. If the organization has hired through Fingercheck, the Division assignment carries forward as a candidate tag. Note that Zoho Recruit does not have a native Divisions or organizational hierarchy module — this metadata is flattened into a candidate attribute.

Fingercheck PayGroup determines pay structure (Salaried vs. Hourly, weekly vs. biweekly cycle) and drives payroll tax logic. Zoho Recruit has no PayGroup equivalent. We map PayGroup to a custom Candidate field (CompensationType or PayFrequency) pre-created in Zoho Recruit's field builder. The value is informational for recruiters evaluating candidates and does not feed any downstream Zoho Recruit payroll integration.

Fingercheck supports up to 5 Cost Center fields per employee for labor allocation and job costing. Zoho Recruit has no native cost center or job-costing module. We map CostCenter fields to candidate custom fields (CostCenter1 through CostCenter5) or Zoho Recruit Tags depending on the customer's reporting needs. The mapping strategy is confirmed during discovery — if the customer uses Zoho Recruit's client billing features, cost center tags may map to Client custom fields instead.

Fingercheck Time Card records (punch-in/out timestamps, break durations, overtime flags, job costing associations) have no native equivalent in Zoho Recruit's ATS schema. We export Time Card records by date range aligned to the migration cutoff as a structured CSV and JSON package and deliver it alongside the candidate migration. If the customer has provisioned a separate payroll HRMS to run alongside Zoho Recruit post-migration, this data package is the intake file for that system. Time Card records are not deleted from Fingercheck — the export is a copy.

Fingercheck scheduling handles shift assignments, conflict detection, and notes for deskless and field workers. Zoho Recruit's scheduling module covers candidate interview availability and recruiter calendar coordination only — it does not handle workforce shift management. We export active schedule records as a structured CSV with employee assignment, date/time, and shift notes for the customer to intake into their replacement scheduling or HRMS system. Schedule data is not migrated as part of the ATS migration scope.

Fingercheck HR Documents (I-9s, certifications, policy acknowledgements, onboarding paperwork) stored per Employee can be migrated to Zoho Recruit as Candidate attachments. We export document metadata (filename, type, upload date, employee association) during discovery and attach documents to the matching Candidate record during import. Documents that do not have a clear candidate association (company-wide policies, benefits guides) are exported as a separate document package for the customer's admin to organize post-migration. Large document volumes (over 1 GB total) require a separate document migration scope with dedicated upload tooling.

Fingercheck PTO and accrual balances (accrual rates, carryover rules, current balances as of migration date) are HRMS data with no ATS equivalent. Zoho Recruit does not manage leave balances or time-off approvals. We export accrual balances as a structured CSV with employee identifier, leave type, balance, accrual rate, and carryover rule, and deliver it as a data package for intake into the customer's replacement HRMS or payroll system. This is a lookup deliverable, not a Zoho Recruit migration.

Fingercheck stores federal and state tax withholding elections per Employee, including state-specific tax table data. The documented Connecticut tax table save bug (where CT tax elections returned null and blocked employee activation) is audited during discovery: we flag any Employee record with a null or incomplete state withholding election before migration so the customer can confirm the correct election. Tax table data has no Zoho Recruit ATS destination and is excluded from candidate import scope. A reconciliation summary of tax election completeness is included in the migration handoff.

Fingercheck payroll export configurations (QuickBooks Online integration settings, export types, journal codes) are per-customer accounting integration settings. Zoho Recruit is an ATS and does not process payroll exports. We document the existing QuickBooks export configuration during discovery as a configuration inventory deliverable for the customer's accounting team to reconfigure in their new payroll system post-migration.

Fingercheck Workflow Automations (hiring sequences, onboarding triggers, offboarding tasks, expense approvals, HR notifications) do not export via API and have no Zoho Recruit equivalent in the migration scope. We document every active Fingercheck Workflow during the discovery call — trigger conditions, downstream actions, and associated employee groups — and deliver this as a written Workflow Inventory. Zoho Recruit's Workflow Builder (recruitment-stage triggers, email alerts, task creation, candidate status updates) is a separate rebuild for the customer's admin team. Workflow definitions are explicitly out of scope for FlitStack AI migration delivery.