Migrate from BeyondPay to Zoho Recruit

BeyondPay employee records map to Zoho Recruit Candidate profiles. We extract first name, last name, email, phone, address, job title, department, hire date, employment status, and salary from the BeyondPay export and populate the corresponding Zoho Recruit Candidate fields. Any employee without a last name must be set to 'not provided' or similar placeholder because Last Name is a mandatory field in Zoho Recruit; records with no last name value are skipped during import. We resolve employees without email addresses by generating a placeholder using [email protected] syntax for candidate creation.

The job title stored in BeyondPay migrates to the Current Title field on the Zoho Recruit Candidate record. If multiple employees share identical titles, no conflict occurs because Zoho Recruit Candidates are individual records. Title variations are preserved exactly as exported from BeyondPay.

BeyondPay department assignments have no native Zoho Recruit equivalent on the Candidate object. We create a Department custom field (single-select picklist) in Zoho Recruit during setup, populate it from the BeyondPay department export, and scope it to the Candidate module. If BeyondPay uses custom department names not yet defined in the picklist, we add them to the picklist values before migration.

Bank routing numbers and account numbers for direct deposit are migrated as encrypted or restricted notes on the Candidate record. Because Zoho Recruit is an ATS and does not store banking details natively, we attach direct deposit information as an internal note with restricted visibility. The note is prefixed with a header identifying it as migrated direct deposit data from BeyondPay and includes the bank name, routing number, and account type (checking or savings) if available from the export.

If BeyondPay contains any active job requisitions or approved headcount positions (common in organizations where BeyondPay is used for HR alongside payroll), these map directly to Zoho Recruit Job Opening records. We map job title, department, employment type, and job description from the BeyondPay export to the corresponding Zoho Recruit Job Opening fields. Job Opening status and assigned recruiter map to the Zoho Recruit Opening Status and Assigned Recruiter fields.

Year-to-date wage totals, pay period earnings, deductions, and tax withholdings are the highest-value data in BeyondPay but have no native ATS equivalent in Zoho Recruit. We flag payroll history as out of scope for the Zoho Recruit migration and recommend pairing with Zoho People and Zoho Payroll to preserve payroll continuity. Historical W-2 data, YTD earnings, and benefit deduction records are documented in the excluded-data inventory and remain available in BeyondPay until the customer chooses a full payroll platform migration.

Federal, state, and local tax codes, withholding rates, and filing statuses configured in BeyondPay do not map to Zoho Recruit because Zoho Recruit does not process payroll tax. We document the tax configurations in the excluded-data inventory. Organizations requiring payroll tax continuity should evaluate Zoho Payroll (available in the Zoho ecosystem) or a dedicated payroll migration to Rippling, Paylocity, or Gusto.

Health, dental, vision, and retirement benefit elections and coverage levels are BeyondPay data that have no ATS representation in Zoho Recruit. We flag benefit elections as excluded from the migration scope and document the current election snapshot in the excluded-data inventory. If the customer adopts Zoho People, benefit elections can be configured there post-migration.

Court-ordered garnishments, voluntary deductions, HSA contributions, and FSA elections do not map to Zoho Recruit's data model. These are flagged as out-of-scope in the migration inventory. Active garnishments should be reconciled against the BeyondPay export before account closure to ensure no active legal orders are missed.

Workers compensation class codes, rates, and carrier information from BeyondPay are migrated as a custom WC Class Code single-line text field on the Candidate record if the information is available in the employee export. If BeyondPay stores WC data at the company level rather than the employee level, we create an organization-level custom field in Zoho Recruit during setup and document the WC configuration in the excluded-data inventory.

BeyondPay configures custom fields per client with no public schema. We request a complete field inventory from the BeyondPay implementation team during discovery and map each BeyondPay custom field to a Zoho Recruit custom field of the appropriate type (text, number, date, picklist, or checkbox). Fields without a clear destination equivalent are flagged for manual review and either mapped to a Zoho Recruit custom field or excluded with documentation in the inventory.

BeyondPay user accounts map to Zoho Recruit User records by email match. Any BeyondPay user without a corresponding Zoho Recruit User is held in a reconciliation queue for the customer's admin to provision. Migration cannot proceed past record import because OwnerId is required on most standard Zoho Recruit modules.

BeyondPay does not expose a documented report export or template API. Custom payroll reports, scheduled reports, and saved report configurations are not migratable and are listed in the excluded-data inventory. Zoho Recruit Standard and above include built-in reporting templates and custom report builders that the customer's admin uses to rebuild relevant reports post-migration.

BeyondPay payroll-triggered automations (payroll processing notifications, tax filing alerts, direct deposit confirmations) do not map to Zoho Recruit's workflow model. We do not migrate workflows or automations as code. The written workflow inventory documents each BeyondPay automation with its trigger, conditions, and actions for the customer's admin to evaluate for Zoho Recruit Workflow Rule rebuild.