HRMS migration
Field-level mapping, validation, and rollback between Apploi and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Apploi
Source
Zoho Recruit
Destination
Compatibility
8 of 12
objects map 1:1 between Apploi and Zoho Recruit.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Apploi to Zoho Recruit is a migration from a healthcare-specific hiring platform with no public API to a general-purpose ATS with a documented CSV import wizard. Apploi does not expose a REST or bulk-export API, so migration depends on database-level exports or manual CSV extraction coordinated with Apploi's data team before the account closes. We extract Jobs, Candidates, Applications, Offers, and healthcare credential data from Apploi, restructure them to satisfy Zoho Recruit's mandatory field requirements (Last Name on Candidates is required and cannot be blank), and import them in dependency order: Users first, then Job Openings, then Candidates, then Applications linked to the correct Job. Healthcare credentials stored as Apploi custom fields are mapped to Zoho Recruit custom fields or a dedicated Certificates custom module on Professional and Enterprise plans. Apploi's shift scheduling data is not retained in any exportable form and is scoped out. Workflows, onboarding templates, and job board posting configurations do not migrate; we deliver a written inventory of these for your admin to rebuild in Zoho Recruit's Blueprints and Workflows builder.
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 Apploi 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.
Apploi
Job Posting
Zoho Recruit
Job Opening
1:1Apploi Job records (title, description, location, department, employment type, status) map directly to Zoho Recruit Job Opening records. Active and closed jobs migrate with their original status preserved. We use the Zoho Recruit Job Opening import template and map Apploi's job_department to Zoho Recruit's Department picklist. Post-migration, your team configures job board distribution in Zoho Recruit's Job Board Settings, as Apploi's multi-posting configuration is stored as account-level settings rather than job data and does not transfer.
Apploi
Candidate
Zoho Recruit
Candidate
1:1Apploi Candidate records map to Zoho Recruit Candidates. Zoho Recruit requires a Last Name value on every Candidate import; Apploi records without a last name are flagged during scoping and populated with 'Not Provided' per Zoho Recruit's import documentation. Email address, phone, address, and employment history migrate as typed fields. The Apploi source_candidate_id is preserved in a custom field for reconciliation. Any Apploi Candidate without an email address is flagged as a partial record requiring manual review before Zoho Recruit activation.
Apploi
Application
Zoho Recruit
Candidate subform or Tag
lossyApploi Application records (linking a Candidate to a Job with stage status: Applied, Screening, Interview, Offer, Hired, Rejected) are mapped to Zoho Recruit's candidate-job association. In Zoho Recruit, Candidates are linked to Job Openings through the Applications section of the Candidate record. We preserve application stage timestamps by adding them as Notes or custom fields on the Candidate record. Multiple applications per candidate are supported in Zoho Recruit's Professional and Enterprise tiers; the Standard tier's 100-active-job limit applies to open positions rather than application records.
Apploi
Offer
Zoho Recruit
Offer (or custom module)
1:1Apploi Offer records (compensation details, start date, offer status) map to Zoho Recruit's Offer module if the Professional or Enterprise plan is selected. Offer letters stored as attachments in Apploi migrate as ContentDocument records linked to the Offer or Candidate. Compensation fields vary by customer Apploi configuration; we map each identified compensation field to a Zoho Recruit custom field on the Offer object and flag any fields without a clear Zoho Recruit destination for the customer's admin to review.
Apploi
Healthcare Credential (CNA, RN, LPN, license numbers)
Zoho Recruit
Custom Fields or Certificates custom module
1:1Apploi stores healthcare credentials as unstructured custom fields on Candidate records. We map each Apploi credential field (certification type, license number, expiration date, issuing state) to Zoho Recruit custom fields on the Candidate module. For customers on Professional or Enterprise, we recommend creating a dedicated Certificates custom module with lookup to Candidate and mapping fields: Certification Name, Issue Date, Expiry Date, Issuer, and License Number. We flag each credential for manual validation against original documentation post-migration to catch expired or mis-typed license numbers. Custom fields and custom modules are not available on the Zoho Recruit Free tier.
Apploi
Onboarding Task
Zoho Recruit
Tasks or custom onboarding module
1:1Apploi onboarding tasks (I-9, background checks, credential verifications) map to Zoho Recruit Tasks linked to the Candidate record. Apploi's template-based onboarding structure (automated task lists for CNAs, nurses, administrative staff) does not migrate as templates; we deliver a written inventory of each Apploi onboarding task with its assignee, due date, and completion status for your admin to rebuild using Zoho Recruit Blueprints or Workflows.
Apploi
Employee Record
Zoho Recruit
Candidate (converted) or Contact
lossyHired Apploi Employee records (basic profile, hire date, job title, department) map to Zoho Recruit Candidates marked with Employee Conversion enabled on Professional and Enterprise plans. Benefits, PTO, and payroll data do not live in Apploi's ATS module and are out of scope for migration to Zoho Recruit ATS. If the customer uses Zoho People for HRMS, employee data migration to Zoho People is a separate scope.
Apploi
Interview Scorecard
Zoho Recruit
Interview Feedback Form
1:1Apploi interview evaluations and scorecards stored as attachments or notes within the Application record are exported as files and mapped to Zoho Recruit Interview Feedback Forms. The Zoho Recruit Interview Feedback Form is available from Standard tier. We import completed scorecard files as ContentDocument records attached to the Interview record. Blank or incomplete scorecard templates do not migrate; we document the Apploi scorecard structure for the customer's admin to re-create in Zoho Recruit's form builder.
Apploi
User / Team Member
Zoho Recruit
User
1:1Apploi team members (recruiters, hiring managers, administrators) map to Zoho Recruit Users. We match by email address. Per Zoho Recruit's migration documentation, users who already have an existing separate Zoho Recruit account cannot be imported; they must close their existing account first. We identify any duplicate email scenarios during scoping and escalate to the customer's admin for resolution before the User import phase begins.
Apploi
Job Board Account Settings
Zoho Recruit
Not migrated
lossyApploi's multi-job-board posting configuration (account credentials for Indeed, ZipRecruiter, LinkedIn, and healthcare job sites) is stored as Apploi account-level settings and does not export as candidate or job data. We do not migrate job board credentials. The customer's admin re-enters these credentials in Zoho Recruit's Job Board Settings post-migration. We provide a list of active job board integrations identified during scoping to assist with this step.
Apploi
Shift Schedule (current and upcoming)
Zoho Recruit
Not migrated
lossyApploi's shift scheduling module stores only current and recently completed schedules; historical shift data is purged on a rolling basis and is not available for export. We migrate current and upcoming schedules as Task records in Zoho Recruit with shift date, time, and location if the customer requests it during scoping, but we flag that Apploi's schedule history will not transfer regardless of migration method. Zoho Recruit ATS does not include a native shift scheduling module; customers needing shift management after migration typically integrate Zoho People or a third-party scheduling tool.
Apploi
Attachment (resume, license copy, certificate)
Zoho Recruit
ContentDocument (File)
1:1Apploi file attachments on Candidate and Application records (resumes, healthcare license scans, certification documents) migrate as ContentDocument records in Zoho Recruit's file storage. We use Zoho Recruit's Attachments import and map the original file type and upload date. Attachments exceeding 25 MB per file require chunked upload handling. Resume parsing in Zoho Recruit (available from Standard tier with 250 parses per day on Standard, 500 on Professional, unlimited on Enterprise) activates on import for any Candidate with a parsed resume file.
| Apploi | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Job Posting | Job Opening1:1 | Fully supported | |
| Candidate | Candidate1:1 | Fully supported | |
| Application | Candidate subform or Taglossy | Fully supported | |
| Offer | Offer (or custom module)1:1 | Fully supported | |
| Healthcare Credential (CNA, RN, LPN, license numbers) | Custom Fields or Certificates custom module1:1 | Fully supported | |
| Onboarding Task | Tasks or custom onboarding module1:1 | Fully supported | |
| Employee Record | Candidate (converted) or Contactlossy | Fully supported | |
| Interview Scorecard | Interview Feedback Form1:1 | Fully supported | |
| User / Team Member | User1:1 | Fully supported | |
| Job Board Account Settings | Not migratedlossy | Fully supported | |
| Shift Schedule (current and upcoming) | Not migratedlossy | Fully supported | |
| Attachment (resume, license copy, certificate) | ContentDocument (File)1:1 | 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.
Apploi gotchas
Apploi has no public API for data export
Historical shift schedule data is not retained
Healthcare credential data is stored as unstructured custom fields
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
Scoping and Apploi data extraction assessment
We audit the Apploi environment: active Jobs, Candidate volume, Application history, Offer records, custom field inventory (especially healthcare credentials), and team member count. We assess the customer's Apploi access level to determine whether CSV export is available through the admin interface, requires Apploi-managed file delivery, or needs IT-assisted database extraction. We also confirm the target Zoho Recruit edition (Free, Standard, Professional, or Enterprise) because custom field limits, custom modules, and Blueprint availability constrain the migration mapping. The scoping output is a written data map and an Apploi extraction plan with a deadline aligned to the customer's Apploi account closure date.
Zoho Recruit schema setup and field mapping design
We design the Zoho Recruit destination schema in a sandbox or staging org. This includes configuring Job Opening fields, Candidate custom fields (mapped from Apploi healthcare credential fields), Offer fields if applicable, and any Certificates custom module. We map Apploi application stage timestamps to Zoho Recruit Notes or custom date fields on the Candidate record. We configure Department picklist values to match Apploi's department taxonomy. We verify that the required Last Name field is present in all Apploi Candidate records and flag any records requiring a placeholder value. Schema setup happens in Zoho Recruit's Setup > Customization > Modules before any data import.
Apploi CSV extraction and data transformation
We extract Apploi data in CSV format for each object: Jobs, Candidates, Applications, Offers, and attachments. Apploi's admin export produces one file per module; we combine and restructure to match Zoho Recruit's import template format. We transform Apploi application stage values to Zoho Recruit's stage picklist, populate missing Last Name fields with 'Not Provided', and map Apploi date formats (ISO 8601 preferred) to Zoho Recruit's accepted date format. Healthcare credentials are extracted as separate columns and mapped to Zoho Recruit custom fields or the Certificates module per the schema design. We produce a reconciliation report: row count per Apploi object before transformation versus the transformed import file row count.
User import and duplicate resolution
We import Apploi team members as Zoho Recruit Users in dependency order (Users must precede Candidates and Jobs because OwnerId is a required reference). We match by email address and identify any accounts with existing Zoho Recruit users. The customer's admin resolves duplicate Zoho Recruit accounts before we proceed. Per Zoho Recruit's migration documentation, we ensure at least two users exist in the destination org before importing, as some Zoho Recruit functions require a minimum user count. Owner assignments on all migrating records are resolved against the imported User table.
Job Opening and Candidate bulk import
We import Job Openings first (from Apploi Jobs), then Candidates, then Applications linked to the correct Job Opening and Candidate. Job Opening import uses Zoho Recruit's Job Openings module template; we map Apploi job_department to the Department picklist and preserve active or closed status. Candidate import uses Zoho Recruit's Candidates module with the custom credential fields active. Application associations are created by importing Candidates with the Job Opening ID pre-linked or by running a secondary association import after both modules are live. We use Zoho Recruit's Data Migration wizard for structured imports and run row-count reconciliation after each module import.
Offer, attachment, and credential validation
Offer records are imported if the Professional or Enterprise plan is active; otherwise, we deliver an Offer import file and a written handoff for the customer's admin to complete manually. File attachments (resumes, license scans, certificates) are uploaded via Zoho Recruit's ContentDocument import. We validate that all healthcare credential fields landed in the correct Zoho Recruit custom fields and flag any records where license expiration dates fall within 90 days for compliance review. Completed interview scorecards are attached to Interview records as ContentDocument files.
Cutover, final reconciliation, and onboarding template handoff
We freeze Apploi write access during cutover (or confirmApploi is already locked) and run a final delta import of any records created or modified during the migration window. We deliver a reconciliation report comparing Apploi source record counts to Zoho Recruit destination record counts for each module. We enable Zoho Recruit as the system of record and provide the onboarding template inventory document listing each Apploi task, assignee, and recommended Zoho Recruit Blueprint or Workflow Rule equivalent for the customer's admin to rebuild. We support a one-week post-cutover reconciliation window for data issues raised within the first five business days of Zoho Recruit operation.
Platform deep dives
Apploi
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 Apploi 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
Apploi: Not publicly documented.
Data volume sensitivity
Apploi 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 Apploi to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Apploi 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 Apploi
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.