HRMS migration
Field-level mapping, validation, and rollback between Kula and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Kula
Source
Zoho Recruit
Destination
Compatibility
10 of 12
objects map 1:1 between Kula and Zoho Recruit.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Kula to Zoho Recruit is a migration from an AI-first ATS built for mid-market sourcing teams to a tiered recruiting platform that spans staffing agencies and corporate HR. Kula's in-house AI resume scoring and interview summarization are preserved as text fields in Zoho Recruit since the destination does not replicate Kula's AI scoring model. Kula's Candidate, Job, Application, and Interview records map directly to Zoho Recruit's equivalent modules, but Zoho Recruit enforces API credit limits and concurrency limits that vary by edition and require batch chunking during large migrations. Pipeline stage configurations migrate as custom stage definitions on each Job Opening rather than as a reusable global template. Workflows, sourcing automations, and career site configurations do not migrate; we deliver a written inventory of every active sourcing sequence and workflow for your admin to rebuild in Zoho Recruit's workflow 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 Kula 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.
Kula
Candidate
Zoho Recruit
Candidate
1:1Kula Candidate records map to Zoho Recruit Candidates. The Kula candidate profile includes contact information, work history, sourced profile data, and AI-generated scores. We map Name, email, phone, LinkedIn URL, current title, current company, and skills directly. Kula's AI resume scores import as a custom multi-line text field since Zoho Recruit has no native AI scoring equivalent. The original AI scores are preserved as read-only reference data so interviewers can see the pre-migration evaluation without manual re-entry.
Kula
Job (Requisition)
Zoho Recruit
Job Opening
1:1Kula Job records map to Zoho Recruit Job Openings. The job title, department, location, employment type, and description migrate directly. Active versus closed status is preserved using Zoho Recruit's Job Opening status field. The hiring manager and recruiter owner assignments map from Kula user emails to Zoho Recruit User lookups.
Kula
Application
Zoho Recruit
Candidate-Job Opening Association
1:1Kula Application records link a Candidate to a Job and track stage progression. In Zoho Recruit, this association is represented by the Candidate record's link to a Job Opening plus any Interview records attached to that association. We preserve the submission date, current stage, rejection or offer outcome, and application source attribution as custom fields on the Candidate record.
Kula
Interview
Zoho Recruit
Interview
1:1Kula Interview records (scheduled rounds, interviewer assignments, interview type) map to Zoho Recruit Interviews. The scheduled date and time, interviewer names, round type, and interview format migrate. Reviewer notes and scorecard feedback from Kula transfer as Interview Feedback Form responses in Zoho Recruit, though the scorecard template structure may require manual recreation as Zoho Recruit's form builder uses a different field architecture.
Kula
Scorecard and AI Summary
Zoho Recruit
Interview Feedback Form (Custom)
1:1Kula generates AI-powered interview summaries and candidate scores stored as structured fields on interview records. These migrate as text fields on the Zoho Recruit Interview Feedback Form. The scorecard rating scale (Kula's internal rubric) maps to Zoho Recruit's rating field or a custom numeric field, with a note that the original Kula scoring rubric is preserved as a PDF attachment for reference. Re-scoring via Zoho Recruit's native assessment tools is a separate step after migration.
Kula
Pipeline Stages
Zoho Recruit
Job Opening Stages
lossyKula's customizable pipeline stages per job are extracted from the source instance and recreated in Zoho Recruit as stage definitions on each Job Opening. We preserve the stage order and probability percentages. Stages that exist across multiple jobs are configured individually since Zoho Recruit stores stage definitions at the Job Opening level rather than as a reusable global pipeline template.
Kula
Custom Fields
Zoho Recruit
Custom Fields
lossyKula custom fields on Candidates, Jobs, and Applications are extracted with their data types and values. We create matching custom fields in Zoho Recruit using Zoho Recruit's field builder, preserving field labels, data types (text, number, date, picklist), and default values. Any Kula picklist values that do not match Zoho Recruit's picklist options are mapped to the nearest Zoho Recruit equivalent with a note in the migration log.
Kula
Tags and Source Attribution
Zoho Recruit
Tags
1:1Kula tags (referral, sourced-linkedin, applied-direct) migrate as Zoho Recruit Tags. We preserve the tag vocabulary and assign tags to the matching Candidate records. Zoho Recruit supports tag-based filtering and hotlists, so the tag taxonomy maps directly. Tags that exceed Zoho Recruit's character limit are truncated with a note.
Kula
User and Team Assignments
Zoho Recruit
Users
1:1Kula recruiter owners, hiring managers, and interviewers are mapped by email address to Zoho Recruit Users. We resolve each Kula user to their Zoho Recruit counterpart and assign Owner or Interviewer permissions based on the Kula role. Any Kula user without a matching Zoho Recruit account goes to a reconciliation queue for your admin to provision before the record import phase.
Kula
Email and SMS Templates
Zoho Recruit
Email Templates
1:1Kula outreach templates migrate to Zoho Recruit Email Templates. We transfer the template body text, subject lines, and conditional merge fields where the field names have a direct Zoho Recruit equivalent. Rich formatting (HTML styling, conditional logic branches) may require manual reconstruction in Zoho Recruit's template editor since the template data models differ. We deliver a list of any templates that require manual review before activation.
Kula
Interviewer Pool
Zoho Recruit
Interviewer Pool
1:1Kula's interviewer pool feature (balancing scheduling load across available team members) maps to Zoho Recruit's Interviewer Pool where this feature is available. Pool membership records transfer as Zoho Recruit interviewer assignments on each Job Opening. Availability settings and scheduling rules are destination-specific and require manual configuration post-migration.
Kula
Career Site Configuration
Zoho Recruit
Not Migrated
1:1Kula's branded career site builder with drag-and-drop templates is not migratable via API. The career site content, styling, job posting copy, and URL structure are excluded from standard migration scope. We deliver a written inventory of each active career site page and recommend that your team copy the content manually or engage Zoho Recruit's implementation team for career site setup.
| Kula | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Candidate | Candidate1:1 | Fully supported | |
| Job (Requisition) | Job Opening1:1 | Fully supported | |
| Application | Candidate-Job Opening Association1:1 | Fully supported | |
| Interview | Interview1:1 | Fully supported | |
| Scorecard and AI Summary | Interview Feedback Form (Custom)1:1 | Fully supported | |
| Pipeline Stages | Job Opening Stageslossy | Mapping required | |
| Custom Fields | Custom Fieldslossy | Mapping required | |
| Tags and Source Attribution | Tags1:1 | Mapping required | |
| User and Team Assignments | Users1:1 | Mapping required | |
| Email and SMS Templates | Email Templates1:1 | Mapping required | |
| Interviewer Pool | Interviewer Pool1:1 | Fully supported | |
| Career Site Configuration | Not Migrated1: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.
Kula gotchas
AI-generated scores do not carry over as live metrics
Reporting exports require a separate manual step
Frequent platform updates can change field behavior
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 field mapping audit
We audit the source Kula instance for all active objects (Candidates, Jobs, Applications, Interviews), custom fields, pipeline stage configurations, tags, and user assignments. We extract AI score fields, interviewer pools, and any scorecard templates. We pair this with a Zoho Recruit edition assessment: Standard covers basic candidate and job management; Professional adds Boolean search, custom fields, and unlimited email templates; Enterprise adds semantic search, unlimited source boosters, and advanced analytics. The discovery output is a written migration scope with field-level mapping for every Kula field.
Zoho Recruit schema pre-configuration
We create the destination schema in Zoho Recruit before any data moves. This includes provisioning custom fields on Candidate and Job Opening modules, configuring stage definitions per pipeline, setting up Tags, and creating the Interview Feedback Form structure to receive scorecard data. We configure the Zoho Recruit User records and role permissions to match the Kula team structure. Schema is validated in a Zoho Recruit sandbox or trial org before production migration begins.
Owner reconciliation and user provisioning
We extract every distinct Kula user referenced on Candidate, Job, Application, and Interview records and match by email against the Zoho Recruit User table. Any Kula owner without a matching Zoho Recruit User goes to a reconciliation queue for your admin to provision. Migration cannot proceed past user resolution because Zoho Recruit requires a valid Owner lookup on Job Opening and Interview records.
Staged data migration with API credit pacing
We run production migration in dependency order: Users (validated manually), Job Openings (base records), Candidates (with last-name substitution for any missing values), Applications (linked to Job Opening and Candidate), Interviews (linked to Candidate and Job Opening), Scorecard data (as Interview Feedback Form responses), and Tags (assigned to Candidates). We chunk all write operations into 100-record batches and pace the import to respect the Zoho Recruit API credit limits for the customer's selected edition. Each phase emits a row-count reconciliation report before the next phase begins.
AI score and scorecard post-processing
We attach the Kula AI-generated resume scores and interview summaries as read-only text notes on the Candidate and Interview records. We deliver a scorecard reconciliation report listing every candidate with a Kula AI score and recommending whether a Zoho Recruit reassessment is warranted based on the score's age and the hiring stage at migration time. This step closes the gap between Kula's live AI metrics and Zoho Recruit's static data model.
Cutover, validation, and workflow inventory handoff
We freeze Kula writes during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho Recruit as the system of record. We deliver the workflow and sourcing sequence inventory document to your admin team for rebuilding in Zoho Recruit's workflow builder or Zoho Deluge. We support a one-week hypercare window to resolve reconciliation issues. We do not rebuild Kula workflows as Zoho Recruit automations inside the migration scope.
Platform deep dives
Kula
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 Kula 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
Kula: Not publicly documented.
Data volume sensitivity
Kula exposes a bulk API — large-volume migrations stream efficiently.
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 Kula to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Kula 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 Kula
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.