HRMS migration

Migrate from Aotal to Zoho Recruit

Field-level mapping, validation, and rollback between Aotal and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.

Aotal logo

Aotal

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

77%

10 of 13

objects map 1:1 between Aotal and Zoho Recruit.

Complexity

CModerate

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Aotal to Zoho Recruit is a cross-platform migration from a New Zealand-focused talent management suite into a globally-used recruitment ATS and CRM. Aotal stores employee records, role histories, competency profiles, and performance cycles with effective-date tracking; Zoho Recruit models its data around Candidates, Job Openings, Clients, and Contacts with a modular lookup relationship. We extract the full Aotal record set in dependency order (Departments before Employees, Roles before Training Records), resolve foreign-key references to their Zoho Recruit equivalents, and load using the Zoho Recruit API with field-level type checking against mandatory fields like Last Name on Candidates. Custom Aotal talent fields and competency profiles that have no direct Zoho Recruit equivalent are flagged in a written configuration handoff for the customer's admin to recreate as custom fields in Zoho Recruit. Workflows, automations, and performance review cycles do not migrate; we deliver an inventory of these for rebuild in Zoho Recruit's workflow builder.

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

Aotal logo

Aotal

What's pushing teams away

  • No publicly listed pricing — pricing requires a sales quote, which is friction for small NZ businesses comparison-shopping against published per-employee SaaS plans.
  • Limited public review footprint compared to global HRIS players — minimal G2/Capterra reviews makes due diligence hard for procurement teams that rely on peer feedback.
  • Regional focus means organizations expanding beyond Australia/New Zealand often outgrow the platform and migrate to global vendors like Workday, SAP SuccessFactors, or BambooHR.
  • Two-product surface area (SnapHire ATS + Talent App Store) can be confusing — customers unsure which product covers a given function may end up duplicating capabilities or buying apps they do not need.
  • Lack of public API documentation makes building custom integrations harder than with platforms that publish OpenAPI specs.

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 Aotal objects map to Zoho Recruit

Each row shows how a Aotal 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.

Aotal

Employee

maps to

Zoho Recruit

Candidate

1:1
Fully supported

Aotal Employee records map to Zoho Recruit Candidate records. We extract name fields (First Name, Last Name), contact information, and any competency or skill properties into Zoho Recruit's standard Candidate fields or custom fields. Last Name is a mandatory field in Zoho Recruit; any Aotal records without a last name are flagged during scoping and assigned a placeholder value (not provided) per Zoho Recruit's import requirements. The Candidate's Email field becomes the primary deduplication key during import.

Aotal

Department

maps to

Zoho Recruit

Department (standard module)

1:1
Fully supported

Aotal Departments map to Zoho Recruit's built-in Department module. Department is loaded first in the migration sequence because it has no incoming lookup dependencies, and it is referenced by Role and Employee records downstream. We preserve the department hierarchy as stored in Aotal and map it to Zoho Recruit's flat Department list, noting that Aotal's hierarchical parent-child relationship requires manual recreation as a custom field in Zoho Recruit if the hierarchy needs to be preserved visually.

Aotal

Role

maps to

Zoho Recruit

Job Opening

1:1
Fully supported

Aotal Role records (job titles, position descriptions) map to Zoho Recruit Job Opening records. The Aotal Role's associated Department maps to the Zoho Recruit Job Opening's Department field via lookup. Job Opening is loaded before Candidate records so that the Job Opening lookup field on Candidate is satisfied at insert time. Status fields (Active, Filled, On Hold) from Aotal map to Zoho Recruit's Job Opening status values.

Aotal

Training Record

maps to

Zoho Recruit

Custom Module or Note Attachment

lossy
Fully supported

Aotal Training Records represent historical employee development data that does not have a native Zoho Recruit equivalent. We assess whether the customer's Zoho Recruit plan includes Custom Modules (Enterprise plan required for full customization with 300 fields per module). If yes, we create a Training History custom module with fields for Course Name, Date Completed, Expiry Date, and Issuer, linked to the Candidate via a lookup relationship. If the destination plan does not include custom modules, training records are migrated as Notes attached to the Candidate record with structured body text and the relevant dates preserved in the Note body.

Aotal

Competency Profile

maps to

Zoho Recruit

Custom Fields or Skills Section

lossy
Fully supported

Aotal competency profiles (skills, certifications, ratings) have no direct Zoho Recruit equivalent. We evaluate the source competency fields and map them to Zoho Recruit's Skills multi-select picklist on the Candidate record for skill-level data. For certification and rating data, we create custom fields on the Candidate module (available on Professional and Enterprise plans with 50 and 300 fields per module respectively). If the customer is on the Standard plan, certification data is merged into structured Note attachments.

Aotal

Performance Cycle

maps to

Zoho Recruit

Not Migrated

1:1
Fully supported

Aotal performance review cycles are tied to the Performance module and do not have a native Zoho Recruit counterpart. Zoho Recruit is an ATS, not an HR performance management system. We do not migrate performance review scores, cycle dates, or reviewer feedback as structured records. We deliver a written inventory of all performance cycles in scope, including cycle name, review period, and the scoring fields used, for the customer to evaluate Zoho People or a dedicated performance management platform as a separate implementation.

Aotal

Client (staffing operations)

maps to

Zoho Recruit

Client

1:1
Fully supported

If Aotal stores client or vendor organization records for staffing operations, these map directly to Zoho Recruit's Client module. Client records are loaded before Job Openings and Candidates so that the Client lookup on Job Openings is satisfied. Client name, industry, website, and contact details map to Zoho Recruit's standard Client fields. Additional Aotal client properties migrate as custom fields if the destination plan supports them.

Aotal

Contact (client-facing)

maps to

Zoho Recruit

Contact

1:1
Fully supported

Aotal contact records associated with client organizations map to Zoho Recruit's Contact module. The Contact is linked to the corresponding Client record via the Client Name lookup field. Email, phone, title, and address fields migrate directly. Aotal contact roles or titles are preserved in the Contact's Title field or a custom field if the destination plan supports it.

Aotal

Engagement: Interview

maps to

Zoho Recruit

Interview

1:1
Fully supported

Aotal interview records (scheduled interviews, interview feedback) map to Zoho Recruit's Interview module. Interview date, time, interviewer name, and status migrate directly. Feedback scores and comments from Aotal map to Zoho Recruit's Interview Feedback Form fields if the destination plan includes this feature (Standard and above). Interview records are linked to the Candidate and Job Opening via Zoho Recruit's lookup relationships.

Aotal

Engagement: Task

maps to

Zoho Recruit

Task

1:1
Fully supported

Aotal task records (hiring tasks, follow-up items) map to Zoho Recruit's Task module. Subject, due date, assigned owner, and status migrate directly. We resolve the task owner by email match against Zoho Recruit users. Any Aotal task owner without a matching Zoho Recruit user goes to a reconciliation queue for the customer's admin to provision before the Task import phase begins.

Aotal

Engagement: Note

maps to

Zoho Recruit

Note

1:1
Fully supported

Aotal notes attached to employee or candidate records migrate to Zoho Recruit's Notes module linked to the corresponding Candidate, Client, or Job Opening record. Note title, body, and creation date migrate. If the Aotal note contains structured data (e.g., a formatted evaluation), we preserve the body as rich text and flag it for the customer's admin to reformat into Zoho Recruit's Interview Feedback Form or a custom field as appropriate.

Aotal

Onboarding Record

maps to

Zoho Recruit

Not Migrated

1:1
Fully supported

Aotal onboarding records (offer letters, document signing, onboarding task lists) are flagged as attachments-only and do not migrate as structured records. Binary documents and signed agreements stored in Aotal are exported as file attachments and delivered alongside the migration for the customer's admin to re-upload to Zoho Recruit's Document Library or attach to the relevant Candidate record manually, as their internal formats require case-by-case review.

Aotal

Custom Talent Fields

maps to

Zoho Recruit

Custom Fields (Enterprise plan)

lossy
Fully supported

Aotal custom talent fields (module-specific configurations that extend the standard schema) do not have direct Zoho Recruit equivalents. We assess each custom field's data type, associated module, and usage frequency. Fields that map to a supported Zoho Recruit field type (text, number, date, picklist, multi-select, checkbox) are recreated as custom fields on the corresponding Zoho Recruit module. Custom field creation is available on Professional and Enterprise plans. Standard plan customers receive a written field inventory for manual re-creation post-migration.

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.

Aotal logo

Aotal gotchas

High

Data lives in multiple microservices across the Talent App Store

Medium

SnapHire ATS and Talent App Store are distinct products with different data shapes

Medium

Vendor-assisted extraction is likely required given no public API docs

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

  • Aotal custom talent fields require manual re-creation in Zoho Recruit

    Aotal stores custom talent fields and module-specific configurations that have no native equivalent in Zoho Recruit's standard schema. We flag each custom field during scoping, assess whether it maps to a supported Zoho Recruit field type, and note whether the destination plan supports custom fields at the required module (50 per module on Professional, 300 per module on Enterprise, none on Standard). Standard plan customers who need custom fields must upgrade to Professional before migration or accept that these fields will be delivered as a written configuration inventory for manual post-migration setup.

  • Zoho Recruit Candidate import fails silently on missing Last Name

    Last Name is a mandatory field on the Zoho Recruit Candidate record. If the Aotal export contains candidate records without a last name, those records are ignored during import with no error message returned by the Zoho Recruit import wizard. We detect missing Last Name values during the pre-migration data audit, assign a placeholder value (not provided) to those records, and document the substitution in the migration report so the customer's admin can correct the names post-migration if needed.

  • Aotal onboarding records and signed documents do not migrate as structured data

    Aotal onboarding records include offer letters, signed agreements, and document attachments that are stored in binary format. Zoho Recruit's Document Library accepts file uploads but does not have a structured onboarding record type. We export these documents as attachment files and deliver them alongside the migration for manual re-upload. The customer admin reviews each document for format compatibility (PDF, DOCX preferred) and re-attaches them to the relevant Candidate record in Zoho Recruit. Binary format documents that cannot be opened are flagged individually.

  • Performance review cycles are out of scope for Zoho Recruit

    Aotal performance cycles (review periods, scores, reviewer feedback) have no equivalent in Zoho Recruit's ATS data model. Zoho Recruit is designed for talent acquisition, not ongoing performance management. We do not migrate performance cycle data as structured records. We deliver a written inventory of all performance cycles in scope, including cycle names, review periods, and the scoring fields used, so the customer's HR team can evaluate Zoho People or a dedicated performance management platform as a separate implementation. This is a known architectural gap between a talent management suite and a recruitment ATS.

  • Existing Zoho Recruit users cannot be re-imported into a different org

    Per Zoho Recruit's import documentation, users who already have a separate Zoho Recruit account cannot be migrated into the customer's corporate Zoho Recruit account until they close their existing individual account. We identify any Aotal owner records whose email matches an existing Zoho Recruit user during the pre-migration audit and flag them for the customer's admin to resolve before the Owner import phase. This is a Zoho Recruit platform constraint, not a migration methodology issue.

Migration approach

Six steps for a successful Aotal to Zoho Recruit data migration

  1. Discovery and data audit

    We audit the Aotal environment across all modules in scope: Employees, Roles, Departments, Training Records, Competency Profiles, Performance Cycles, Onboarding Records, and any client or contact records used for staffing operations. We produce a data volume estimate (record counts per module), identify custom talent fields and their data types, flag records with missing mandatory fields (notably Last Name equivalents in Aotal), and assess the binary document inventory for onboarding attachments. The discovery output is a written scope document with module-level record counts, a custom field inventory, and a Zoho Recruit plan recommendation based on the migration's custom field and custom module requirements.

  2. Schema design and field mapping specification

    We design the Zoho Recruit destination schema based on the discovery output. This includes confirming the Zoho Recruit edition (Standard, Professional, or Enterprise), creating any required custom modules (Training History) and custom fields (competency profiles, certification fields) before data migration begins, and mapping Aotal module fields to their Zoho Recruit equivalents with explicit type checking. The mapping specification covers both standard field-to-field mappings and configuration notes for fields that require manual post-migration setup. Schema is validated against the Zoho Recruit field type constraints before any data is extracted from Aotal.

  3. Data export and transformation

    We extract data from Aotal in the correct dependency order: Departments first (no dependencies), then Roles (depends on Department), then Employees (depends on Department and Role), then Training Records (depends on Employee), then Competency Profiles (depends on Employee), then engagement history (Tasks, Interviews, Notes). We transform each record to match the Zoho Recruit field type requirements (date formatting, picklist value normalization, text truncation for fields with length limits) and apply the missing Last Name placeholder substitution. The transformed dataset is validated against the mapping specification before upload.

  4. Staged import with lookup resolution

    We run a staged import into the Zoho Recruit environment using the Zoho Recruit API. Modules are loaded in dependency order so that parent records exist before child records that reference them. Department is loaded first, followed by Job Openings (linked to Department), then Client and Contact records, then Candidate records (with Last Name substitution applied), then Tasks, Interviews, and Notes. For each phase, we run a row-count reconciliation against the Aotal source and resolve any Zoho Recruit validation errors before proceeding to the next module. Any Aotal owner records without a matching Zoho Recruit user are held in a reconciliation queue for the customer's admin to provision.

  5. Custom field and training record post-processing

    After the staged import completes, we create any remaining custom fields that were not part of the initial import (competency profile fields, certification fields) in Zoho Recruit, using the custom field inventory from discovery. For customers on Enterprise plan, we create the Training History custom module with the required fields and link existing training records to the corresponding Candidate records via the lookup field. For Standard plan customers, we deliver the training records as structured Note attachments. We produce a post-migration reconciliation report showing record counts in Aotal versus Zoho Recruit per module.

  6. Cutover and inventory handoff

    We freeze Aotal write access during cutover, run a final delta migration of any records modified during the migration window, and hand off Zoho Recruit as the system of record. We deliver the Workflow and Automation Inventory document listing any Aotal workflows or automated hiring processes that require rebuilding in Zoho Recruit's Workflow Rules or Blueprint builder. We deliver the Performance Cycle Inventory listing performance review data for evaluation in Zoho People or an alternative performance management platform. We support a one-week hypercare window for reconciliation issues. Post-migration admin support, training, and workflow rebuild are outside standard scope and can be scoped as separate engagements.

Platform deep dives

Context on both ends of the pair

Aotal logo

Aotal

Source

Strengths

  • Local NZ-based vendor with regional support, valued by Aotearoa corporates
  • Microservices model in Talent App Store lets customers buy only the modules they need
  • Broad functional coverage across ATS, onboarding, performance, learning, payroll, time, analytics, benefits, and self-service
  • SnapHire ATS has a long track record in the NZ corporate recruiting market
  • Pre-integrated app architecture reduces typical HR-tech integration headache

Weaknesses

  • No published pricing — every quote is sales-led
  • Limited public review footprint and small community resources
  • Regional focus limits suitability for multi-region/multi-country employers
  • Two-product split (SnapHire + Talent App Store) can confuse buyers
  • Public API documentation is not indexed, complicating custom integration builds
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?

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

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Aotal and Zoho Recruit.

  • Object compatibility

    C

    4 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

    Aotal: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Aotal 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 Aotal to Zoho Recruit data migrations

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

Can't find your answer?

Walk through your Aotal to Zoho Recruit migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations complete in two to four weeks for accounts with up to 5,000 candidate records, fewer than 50 job openings, and no complex competency profile or training record transformations. Migrations involving custom module creation (Training History), competency profile mapping to custom fields, historical training record imports, or large engagement volumes (over 100,000 activity records) extend to five to eight weeks because of custom field creation, lookup resolution, and Zoho Recruit API batch handling. The Zoho Recruit migration wizard supports CSV uploads that can be completed in a few days for straightforward imports, but the pre-migration audit, schema design, transformation work, and reconciliation testing add time for non-trivial migrations.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Aotal.
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