Migrate from BeyondPay to Crelate

BeyondPay Employee records map to Crelate Contact records with the Contact type set to Candidate. We map first name, last name, email, phone, address, job title, department, and hire date to the corresponding Crelate Contact fields. BeyondPay's employee status (active, terminated, on leave) maps to a custom Contact status field since Crelate's standard Contact model uses pipeline stages rather than employment status. We flag terminated employees for manual review before loading if the customer wants to exclude them from the active candidate pool. Custom fields from BeyondPay map to Crelate custom fields on Contact; any BeyondPay fields without a Crelate equivalent are flagged for review.

BeyondPay custom fields are per-client and lack a public schema, so we request a complete field inventory from the BeyondPay implementation team during discovery. We map each BeyondPay custom field to a Crelate custom field on the appropriate Core Record (Contacts, Companies, or Opportunities), matching the field type (text, number, date, dropdown). Fields without a Crelate equivalent are flagged for manual review and either dropped from the initial migration scope or held for post-migration custom field creation in Crelate. The customer decides on field disposition during the scoping call.

BeyondPay Company records (if configured as a client or organizational entity) map to Crelate Company records. Company name, address, and industry map directly. We use Company name as the dedupe key during import to prevent duplicate Company records if the customer has already configured Crelate Companies. If BeyondPay does not store separate Company records (common in pure payroll configurations), this object is skipped and employee records are loaded as standalone Contacts.

Year-to-date wage totals, pay period earnings, deductions, and tax withholdings are BeyondPay's most migration-critical data for payroll continuity, but Crelate is an ATS and recruiting CRM — it has no schema for payroll histories, pay periods, or wage records. Payroll history does not migrate to Crelate. We recommend the customer maintains BeyondPay access (or migrates to a dedicated payroll platform) to retain payroll history for W-2 accuracy, tax audits, and benefit verification. We do not migrate payroll history to Crelate under any scope configuration.

Federal, state, and local tax codes, rates, and filing statuses configured in BeyondPay have no equivalent in Crelate's ATS schema. Crelate does not handle payroll tax withholding, W-2 generation, or tax filing. Tax configurations do not migrate. The customer must retain a payroll platform (BeyondPay or a replacement) to maintain tax compliance. We flag this as out-of-scope during the first scoping call so the customer does not expect payroll data to land in Crelate.

Health, dental, vision, and retirement benefit elections and coverage levels stored in BeyondPay do not map to Crelate's candidate record schema. Crelate tracks candidate status and engagement through the recruiting pipeline but does not maintain benefit enrollment records. We migrate benefit elections as a current-state snapshot note on the Contact record if the customer explicitly requests it, but this is a manual annotation rather than a structured field migration. Benefit administration requires a dedicated HRIS or benefits platform post-migration.

Court-ordered garnishments, voluntary deductions, and HSA or FSA contributions are payroll-specific records in BeyondPay that have no Crelate equivalent. Crelate's ATS schema does not include garnishment, deduction, or benefits enrollment fields. These records do not migrate to Crelate. We recommend the customer retains BeyondPay or migrates garnishments and deductions to a payroll platform that supports these record types. We do not migrate garnishment records under standard scope.

Bank routing numbers and account numbers for employee direct deposit are encrypted payroll data that does not belong in an ATS. Migrating bank account information to Crelate would place sensitive financial data in a system designed for candidate and client management, which creates unnecessary compliance exposure. Direct deposit information does not migrate. The customer retains this data in BeyondPay or transfers it to their chosen payroll platform.

WC class codes, rates, and carrier information configured in BeyondPay are payroll insurance settings with no Crelate equivalent. Crelate does not handle workers compensation configuration, insurance carrier data, or class code assignments. These settings do not migrate to Crelate. If the customer's organization uses workers comp tracking for placed contractors or temporary employees, we recommend maintaining those records in a payroll or HRIS system separate from Crelate.

Hourly employee time entries, overtime calculations, and accrual balances are payroll transaction records that Crelate's ATS schema does not support. Crelate's Activity records (calls, emails, meetings, tasks) track candidate engagement, not time worked or PTO accrual. Time tracking data does not migrate. We note that PTO and leave accrual tracking is a common point of confusion when migrating from payroll platforms to ATS platforms — the customer should verify their time-tracking needs are met by a dedicated payroll system post-migration.

BeyondPay's custom reports, scheduled reports, and saved report configurations are not migratable. Crelate provides Advanced Reports and Analytics on the Business plan, which the customer's team configures post-migration. We do not rebuild BeyondPay reports as Crelate reports inside the migration scope. We deliver a written inventory of BeyondPay report names and the data they reference so the customer's Crelate admin can reproduce them in the new platform.

BeyondPay does not expose a documented automation or workflow API, and the service-bureau model relies on implementation-assisted configuration rather than self-service automation builders. Any BeyondPay workflow configurations (typically limited to payroll processing workflows rather than recruiting pipelines) do not migrate to Crelate. Crelate's Automation and Sequencing features (available on Business Plus and Enterprise plans) are configured by the customer's team post-migration. We do not migrate automations as code and do not rebuild BeyondPay configurations inside the migration scope.