HRMS migration
Field-level mapping, validation, and rollback between Back Track Screening and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Back Track Screening
Source
Zoho Recruit
Destination
Compatibility
10 of 12
objects map 1:1 between Back Track Screening and Zoho Recruit.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Back Track Screening to Zoho Recruit connects a purpose-built background screening vendor to a full-cycle ATS. Back Track Screening operates without a documented public API, so migrations rely on structured file exports and Zoho Recruit's bulk import tools. The critical constraint is FCRA compliance: consent and disclosure records must migrate first and retain their original signed-date timestamps so the employer can reconstruct the adverse action window at the destination. SSN trace address history is a mandatory migration object because it determines which county criminal searches were originally ordered; without it, the jurisdiction coverage cannot be replicated in Zoho Recruit or any downstream screening integration. We preserve all screening report objects (criminal, education, employment, drug test, credit) as custom fields or attachments against the Zoho Recruit Candidate record, and we deliver a written map of any active Back Track Screening workflows so the customer's admin can rebuild them in Zoho Recruit's Blueprint and Workflow modules post-migration.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Back Track Screening object lands in Zoho Recruit, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Back Track Screening
Candidate
Zoho Recruit
Candidate
1:1Back Track Screening Candidate records (containing name, date of birth, contact information, and SSN) map directly to Zoho Recruit Candidate records. We preserve the original SSN as a masked custom field (last four digits only) per FCRA data-minimization practices, with the full SSN held in a restricted-access compliance attachment. Consent and disclosure signed-date timestamps migrate as required fields on the Candidate record or as linked compliance documents to maintain the legal defensibility chain for adverse action decisions.
Back Track Screening
Screening Order
Zoho Recruit
Candidate + Custom Fields or Job Application
1:1Back Track Screening Screening Orders bundle a candidate with a specific check package (criminal, education, employment, drug, credit). We map each order to a Zoho Recruit Candidate record enhanced with custom fields recording package type, order date, order status (pending, in-progress, complete), and the ordering employer reference. If the screening was tied to a specific job requisition, we link it to the corresponding Job Application in Zoho Recruit via the Candidates_Jobs module relationship.
Back Track Screening
SSN Trace
Zoho Recruit
Custom Field: Address History
1:1SSN trace output from Back Track Screening produces an address history that determines county-level criminal search scope. This is a first-class migration object: we preserve the raw trace result and the derived address list as structured custom fields on the Zoho Recruit Candidate record. The address history validates that any migrated criminal record corresponds to a jurisdiction that was actually covered under the original SSN trace, which is critical for FCRA compliance reconstruction if adverse action is ever taken.
Back Track Screening
Criminal Records
Zoho Recruit
Custom Fields or Attachments on Candidate
1:1Criminal records returned per jurisdiction (county, state, federal) include charge details, disposition, and court references. We map each record to Zoho Recruit custom fields capturing jurisdiction, charge classification, disposition, and court name. The county-source of each record is validated against the migrated SSN trace address history. If Back Track Screening returns a PDF report, we attach it to the Zoho Recruit Candidate record as a compliance document rather than parsing fields that might lose nuance.
Back Track Screening
Education Verification
Zoho Recruit
Custom Fields on Candidate
1:1Education verification results include school name, degree, dates of attendance, and verification status (verified, unable to verify, in-progress). We map these to Zoho Recruit Candidate custom fields and preserve the verification call notes in a linked Candidate Note. If the candidate has multiple education records (e.g., undergraduate and graduate), we create separate custom field sets or use Zoho Recruit's Notes with tagged categorization to distinguish each institution.
Back Track Screening
Employment Verification
Zoho Recruit
Custom Fields on Candidate
1:1Employment verification results include employer name, title, dates of employment, salary (if disclosed by the employer), and reason for leaving. We map these to Zoho Recruit Candidate custom fields and preserve the raw employer response as a Note attached to the candidate. Multiple employment records are handled as repeating custom field groups or as separate Notes with consistent tagging. If salary data was included, we note it as sourced from employer disclosure for compliance awareness.
Back Track Screening
Drug Test Records
Zoho Recruit
Custom Fields on Candidate
1:1Drug test records include test type (urine, hair, DOT), collection date, lab result (negative, positive, dilute), and MRO (Medical Review Officer) review status. We map these to Zoho Recruit Candidate custom fields. DOT test records are flagged with a DOT-compliant notation. MRO review status is preserved because it is legally significant for FMCSA and DOT-regulated hiring positions.
Back Track Screening
Credit Reports
Zoho Recruit
Custom Fields on Candidate
1:1Credit reports returned for employment purposes include only permissible inquiry elements under FCRA (typically bankruptcy and sometimes public records). We map the returned elements to Zoho Recruit Candidate custom fields and flag non-permissible elements as excluded. The raw credit report PDF is attached as a restricted-access compliance document. We note the inquiry date and FCRA permissible purpose to support any future disputes.
Back Track Screening
Adverse Action Records
Zoho Recruit
Candidate Notes or Compliance Attachments
1:1Adverse action documentation (pre-adverse action notice, candidate response window, final adverse action letter) is migrated as a sequence of compliance documents attached to the Zoho Recruit Candidate record. Signed-date timestamps are preserved verbatim so the employer can demonstrate the legally required timing between notices. We sequence adverse action records after consent records and after screening results in migration order to maintain the FCRA defensibility chain.
Back Track Screening
Custom Check Types
Zoho Recruit
Custom Fields or Custom Module
lossyBack Track Screening offers customized solutions beyond standard packages. We treat each custom check type as a configuration object: if the custom check produces a structured result (e.g., a numeric score or a yes/no finding), we create Zoho Recruit custom fields on the Candidate record. If the custom check produces an unstructured report, we attach it as a compliance document. For organizations with more than five distinct custom check types, we recommend a Zoho Recruit Custom Module to consolidate them rather than proliferating custom fields on the standard Candidate layout.
Back Track Screening
FCRA Disclosure and Authorization Records
Zoho Recruit
Compliance Attachments on Candidate
1:1FCRA disclosure and authorization records are compliance-critical and must migrate before any screening results. We preserve the signed disclosure document and authorization record as separate attachments on the Zoho Recruit Candidate record, each with the original signed-date timestamp stored as a custom field. We flag whether each record is an individual disclosure or a summary disclosure under the applicable FCRA version at time of signing. These records are not merged with screening results in migration order because they must precede adverse action documentation in the compliance chain.
Back Track Screening
Screening Package Configuration
Zoho Recruit
Custom Fields on Job Opening or Candidate
lossyBack Track Screening packages define the scope of checks ordered for a role (e.g., criminal + education + employment, or criminal + drug + credit). We preserve the package name, included check types, and any tier or pricing tier associated with the package as custom fields on the corresponding Zoho Recruit Job Opening record or, if the package was applied per-candidate rather than per-job, on the Candidate record. This allows the customer's admin to reference the original package scope when rebuilding automated screening triggers in Zoho Recruit Workflow.
| Back Track Screening | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Candidate | Candidate1:1 | Fully supported | |
| Screening Order | Candidate + Custom Fields or Job Application1:1 | Fully supported | |
| SSN Trace | Custom Field: Address History1:1 | Fully supported | |
| Criminal Records | Custom Fields or Attachments on Candidate1:1 | Mapping required | |
| Education Verification | Custom Fields on Candidate1:1 | Fully supported | |
| Employment Verification | Custom Fields on Candidate1:1 | Fully supported | |
| Drug Test Records | Custom Fields on Candidate1:1 | Mapping required | |
| Credit Reports | Custom Fields on Candidate1:1 | Mapping required | |
| Adverse Action Records | Candidate Notes or Compliance Attachments1:1 | Fully supported | |
| Custom Check Types | Custom Fields or Custom Modulelossy | Mapping required | |
| FCRA Disclosure and Authorization Records | Compliance Attachments on Candidate1:1 | Fully supported | |
| Screening Package Configuration | Custom Fields on Job Opening or Candidatelossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Back Track Screening gotchas
FCRA consent and disclosure records are compliance-critical in migration
SSN trace address history drives the scope of county criminal searches
Background check industry has a pattern of hidden fees absent from base pricing
Zoho Recruit gotchas
Daily API rate limits are tier-gated and per-user capped
User import hard cap of 2,000 records
Attachment folder hierarchy must be preserved exactly
Resume parsing quota varies by plan and resets daily
Custom fields unavailable in Free and Standard editions
Pair-specific challenges
Migration approach
Discovery and export feasibility assessment
We audit Back Track Screening's available export formats (CSV, XML, PDF), data dictionary, and any record-level schema documentation. We inventory all candidate records, screening orders, SSN trace address histories, criminal records, education and employment verifications, drug test results, credit report elements, adverse action documents, custom check types, and FCRA disclosure records. We also assess the record volume, date range, and any known data quality issues (missing addresses, incomplete consent timestamps). This step produces a written export feasibility report and a request to Back Track Screening for their data export capability.
Consent and disclosure record extraction
We request FCRA disclosure and authorization records from Back Track Screening as a separate file export before any other object. We validate each record against the corresponding candidate record by name, DOB, and SSN last-four. We preserve the original signed-date timestamp, document type (individual disclosure, summary disclosure, authorization), and any version identifier. Consent records are staged in migration order so they load before any screening results.
SSN trace and criminal record validation schema
We extract SSN trace address history as a separate object and build a validation matrix that maps each county criminal record to its originating jurisdiction from the address list. This is not a field mapping exercise; it is a data integrity check that ensures every criminal record in the migration has a corresponding county search authorization in the SSN trace. Any criminal record without a matching jurisdiction is flagged for the customer's compliance team to decide whether to re-run the search in Zoho Recruit or document the gap.
Zoho Recruit schema design and sandbox import
We design the Zoho Recruit custom field schema for all screening objects (criminal, education, employment, drug test, credit, adverse action) and create any required Custom Modules for custom check types. We import into a Zoho Recruit Sandbox or a parallel development org first, validate record counts, spot-check mapped fields against source records, and confirm that compliance attachments (PDFs, consent forms) attach correctly to the Candidate record. The customer's Zoho Recruit admin reviews and approves the schema before production import begins.
Production migration in dependency order
We run production migration in compliance-aware order: FCRA consent and disclosure records first (as compliance-anchoring documents), then candidate profiles, then SSN trace address histories, then screening orders and results (criminal, education, employment, drug test, credit), then adverse action records. Custom check types load last. Each phase emits a row-count reconciliation report. We use Zoho Recruit's bulk CSV import for structured fields and manual file attachment for compliance PDFs. API-based imports are used for any custom module records.
Connector configuration handoff and workflow rebuild map
We deliver a written connector configuration guide for setting up the Accurate or Verified First background check integration in Zoho Recruit, including the package definitions that correspond to the migrated screening packages. We also deliver a written inventory of any active Back Track Screening workflows or direct-contact ordering processes that require rebuilding in Zoho Recruit's Blueprint and Workflow modules. We do not rebuild workflows as code inside the migration scope; we hand off the written map and the customer's Zoho Recruit admin or a Zoho partner implements the automation. We support a one-week hypercare window for reconciliation issues raised during the first hiring cycle.
Platform deep dives
Back Track Screening
Source
Strengths
Weaknesses
Zoho Recruit
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Back Track Screening and Zoho Recruit.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Back Track Screening: Not publicly documented.
Data volume sensitivity
Back Track Screening doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Back Track Screening to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Back Track Screening to Zoho Recruit migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Back Track Screening
Other ways to arrive at Zoho Recruit
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.