HRMS migration

Migrate from Back Track Screening to Zoho Recruit

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 logo

Back Track Screening

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

83%

10 of 12

objects map 1:1 between Back Track Screening and Zoho Recruit.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Back Track Screening logo

Back Track Screening

What's pushing teams away

  • Pricing is not disclosed publicly — every prospect must contact sales for a quote, blocking side-by-side comparison with vendors like Checkr or Sterling that publish per-check rates.
  • Limited public review footprint compared to top-tier screening vendors makes vendor due diligence harder, especially for procurement teams that require third-party validation.
  • Smaller vendor scale than national providers may limit international coverage and specialty searches outside US jurisdictions.
  • Background check industry generally carries hidden fees (county search surcharges, rush processing, international add-ons) that are not visible until contract — Backtrack's quote-based model exposes the same risk.
  • Self-service portal capability appears limited compared to API-first competitors, with most ordering flowing through direct vendor contact or ATS integration rather than a standalone client portal.

Choosing

Zoho Recruit logo

Zoho Recruit

What's pulling them in

  • Lowest cost entry point of any major ATS — a free tier with Candidates, Clients, Contacts, Interviews, and a career site lets small teams validate before committing to a paid plan.
  • Deep Zoho ecosystem integration — if the team already uses Zoho CRM, Sheets, or Analytics, candidate data flows between modules without re-keying or third-party middleware.
  • Customizable pipelines and stages — both agency and corporate editions let users define custom pipeline stages and assign candidates through drag-and-drop visual boards.
  • AI-assisted features via Zia — resume parsing, candidate summarization, and job-candidate matching are built in on paid tiers, reducing manual screening time.
  • Job board aggregation at no extra cost — paid tiers include postings to major job boards, extending reach without purchasing separate job ad bundles.

Object mapping

How Back Track Screening objects map to Zoho Recruit

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

maps to

Zoho Recruit

Candidate

1:1
Fully supported

Back 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

maps to

Zoho Recruit

Candidate + Custom Fields or Job Application

1:1
Fully supported

Back 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

maps to

Zoho Recruit

Custom Field: Address History

1:1
Fully supported

SSN 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

maps to

Zoho Recruit

Custom Fields or Attachments on Candidate

1:1
Mapping required

Criminal 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

maps to

Zoho Recruit

Custom Fields on Candidate

1:1
Fully supported

Education 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

maps to

Zoho Recruit

Custom Fields on Candidate

1:1
Fully supported

Employment 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

maps to

Zoho Recruit

Custom Fields on Candidate

1:1
Mapping required

Drug 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

maps to

Zoho Recruit

Custom Fields on Candidate

1:1
Mapping required

Credit 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

maps to

Zoho Recruit

Candidate Notes or Compliance Attachments

1:1
Fully supported

Adverse 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

maps to

Zoho Recruit

Custom Fields or Custom Module

lossy
Mapping required

Back 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

maps to

Zoho Recruit

Compliance Attachments on Candidate

1:1
Fully supported

FCRA 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

maps to

Zoho Recruit

Custom Fields on Job Opening or Candidate

lossy
Fully supported

Back 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.

Gotchas + challenges

What specifically takes care here

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 logo

Back Track Screening gotchas

High

FCRA consent and disclosure records are compliance-critical in migration

High

SSN trace address history drives the scope of county criminal searches

Medium

Background check industry has a pattern of hidden fees absent from base pricing

Zoho Recruit logo

Zoho Recruit gotchas

High

Daily API rate limits are tier-gated and per-user capped

High

User import hard cap of 2,000 records

Medium

Attachment folder hierarchy must be preserved exactly

Medium

Resume parsing quota varies by plan and resets daily

Low

Custom fields unavailable in Free and Standard editions

Pair-specific challenges

  • FCRA consent records must migrate before screening results

    Under the FCRA, employers must retain signed disclosure and authorization records for each candidate screened before running any check. If these records are not migrated or are migrated out of order relative to the screening results, the employer loses their legal defensibility for adverse action decisions. We flag consent and disclosure records as mandatory first-phase migration objects, sequence them before screening results, and preserve the original signed-date timestamp so the compliance window can be reconstructed at the destination. Back Track Screening does not expose these via API, so they must be requested as file exports and validated against candidate records during scoping.

  • SSN trace address history is required for criminal record validation

    Back Track Screening uses SSN trace output to determine which counties to search for criminal records. If the SSN trace address history is not migrated, the destination system cannot replicate the jurisdiction coverage that was originally ordered. We treat the SSN trace address history as a first-class migration object and validate that every migrated criminal record is matched to a jurisdiction from that address list. Without this validation, a criminal record might be attributed to an unsearched county, creating a false negative risk for the employer's compliance posture.

  • Back Track Screening has no public API; file exports require vendor coordination

    Back Track Screening does not publish a public REST or bulk API. All data exports must be coordinated directly with the vendor as structured file downloads (CSV, XML, or PDF). This means export scoping depends on Back Track Screening's internal data extraction capability, turnaround time for export requests, and whether they can produce exports in a schema that supports automated field mapping. We request the full data dictionary and export schema during scoping before committing to a migration timeline. If Back Track Screening cannot produce a machine-readable export within the project timeline, we escalate to manual record extraction or reject the migration as infeasible under standard scope.

  • Background check ordering does not automatically resume in Zoho Recruit

    Zoho Recruit's background check integrations (Accurate and Verified First) are configured as new-order workflows, not as import pipelines for historical screening data. After migration, the customer's admin must configure the background check connector, authenticate with their Accurate or Verified First account, and define the screening package and workflow trigger in Zoho Recruit's Blueprint or Workflow module. Historical screening results from Back Track Screening do not automatically link to new screening orders in Zoho Recruit; we document the linkage manually and advise the admin on setting up connector triggers for future hiring.

  • Custom check types may require a Zoho Recruit Custom Module

    Back Track Screening's customized screening packages can include industry-specific verifications or unusual search scopes that do not map cleanly to Zoho Recruit's standard Candidate custom fields. If an organization has more than five distinct custom check types with structured results, we recommend a Zoho Recruit Custom Module rather than proliferating custom fields. Custom Module creation requires Zoho Recruit Professional or Enterprise (not Standard) and is a configuration step the customer's admin performs post-migration with our written schema specification.

Migration approach

Six steps for a successful Back Track Screening to Zoho Recruit data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Back Track Screening logo

Back Track Screening

Source

Strengths

  • Covers standard screening types: criminal (county, state, federal), SSN trace, education, employment, drug, and credit
  • Modular and customizable screening packages allow employers to tailor scope to role and risk profile
  • Positions explicitly on FCRA compliance and EEOC guidance, aligning with regulated hiring workflows
  • Offers customized solutions for clients with non-standard screening requirements
  • Operates with a direct-contact sales model, suggesting SMB and mid-market focus

Weaknesses

  • No publicly documented API — integrations rely on manual file exchange or vendor-specific connectors
  • Pricing is not published on the website; quotes are requested per-client, obscuring cost predictability
  • Very limited public documentation, reviews, or technical references compared to major screening vendors
  • No self-service portal apparent from public site — ordering and results appear to be handled via direct interaction
  • Smaller vendor with less market presence, which may affect global coverage breadth compared to Checkr or First Advantage
Zoho Recruit logo

Zoho Recruit

Destination

Strengths

  • Free tier includes full candidate management with a hosted career site, making it viable for very small staffing operations.
  • Multi-edition architecture splits agency and corporate HR workflows, with tier-gated features that scale predictably with headcount.
  • Per-user API rate limits (500–1000/day) are generous for mid-size migrations compared to competitors that gate by total org quota.
  • Zoho's own data migration tool supports CSV import from Bullhorn, CATS, Jobdiva, and Workable, validating interoperability with common ATS formats.
  • 45-day money-back guarantee and 15-day full-feature trial reduce financial risk for teams evaluating the platform.

Weaknesses

  • Free edition excludes custom fields, lookup relationships, and formula fields, making data model extensibility unavailable until a paid tier is purchased.
  • Resume parsing quotas are capped: 250/day on Standard, 500/day on Professional, unlimited only on Enterprise — bulk imports of large candidate pools will hit these limits.
  • No bulk/batch API endpoint for inserts or updates — large migrations rely on looping single-record API calls within daily rate limit windows.
  • Custom modules cannot be imported from external ATS; only standard modules (Users, Candidates, Clients, etc.) are in the supported migration list.
  • Attachments require a rigid folder hierarchy to re-associate with records, and any deviation in folder structure during extraction causes silent disassociation.

Complexity grading

How hard is this migration?

Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Back Track Screening and Zoho Recruit.

  • Object compatibility

    B

    1 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Back Track Screening: Not publicly documented.

  • Data volume sensitivity

    B

    Back Track Screening doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Back Track Screening to Zoho Recruit migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Back Track Screening to Zoho Recruit data migrations

Answers to the questions buyers ask most during Back Track Screening to Zoho Recruit migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between three and five weeks for organizations with up to 2,000 candidate records and standard screening packages (criminal, education, employment). Migrations with high adverse action volumes, multi-package custom check types, or jurisdictions requiring county-level jurisdiction documentation move to seven to ten weeks because of SSN trace address history validation, consent record sequencing, and the time required to design and test the Zoho Recruit custom field schema. The primary timeline variable is Back Track Screening's data export turnaround, which is not automated and depends on vendor coordination.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Back Track Screening.
Land in Zoho Recruit, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day