HRMS migration
Field-level mapping, validation, and rollback between Mitratech Circa and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Mitratech Circa
Source
Zoho Recruit
Destination
Compatibility
7 of 12
objects map 1:1 between Mitratech Circa and Zoho Recruit.
Complexity
BStandard
Timeline
5-8 weeks
Overview
Moving from Mitratech Circa to Zoho Recruit means trading a compliance-specific ATS built for federal contractors and DEIB programs for a general-purpose recruitment platform with a lower per-seat price and a documented REST API. Circa has no published public API, so all extraction relies on CSV exports from the application UI, which requires careful sequencing to preserve the relationships between Jobs, Applicants, Outreach Records, and Community Partners that Circa stores as separate linked entities rather than nested objects. We run a denormalization step during transform to flatten Outreach history and AAP metrics into Zoho-compatible formats — either as notes attached to Job Openings and Candidates, or as custom fields — so that compliance-adjacent sourcing history remains accessible after cutover. Workflows, automations, ESDS posting configurations, and AAP plan generators do not migrate; we deliver a written inventory of these for the customer's admin to rebuild in Zoho.
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 Mitratech Circa 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.
Mitratech Circa
Job
Zoho Recruit
Job Opening
1:1Circa Job records map to Zoho Recruit Job Openings. Title, location, department, job description, employment type, and job status migrate directly. Circa's EEO-1 job group classification and posted date migrate as custom fields since Zoho Recruit does not have a native EEOC-1 category field. Active job status maps to Zoho's Open status; Closed and Draft map directly. We verify that the number of Job records in the Circa CSV matches the number of Job Openings inserted in Zoho before proceeding to Applicants.
Mitratech Circa
Applicant
Zoho Recruit
Candidate
1:1Circa Applicant records map to Zoho Recruit Candidates with name, email, phone, stage, source, and application date preserved. Diversity sourcing tags captured during Circa's intake workflow migrate to custom Candidate fields that we create during schema setup. Circa's applicant source attribution migrates to Zoho's Source field. Zoho requires a Last Name value on every Candidate import; records without a last name in the Circa export receive 'Not Provided' as a placeholder per Zoho's data migration documentation.
Mitratech Circa
Outreach Record
Zoho Recruit
Note or Task
lossyCirca stores Outreach Records as separate entities linked to Jobs by ID rather than embedded within the job or applicant. During migration we denormalize outreach history into Zoho Notes attached to the corresponding Job Opening, preserving outreach date, partner name, outreach method, and response status as Note content. We also write the original Circa outreach record ID into a custom field so the relationship can be reconstructed in Zoho's reporting if needed. If the customer requires structured outreach tracking, we create a custom Outreach module in Zoho and map outreach records there.
Mitratech Circa
Community Partner
Zoho Recruit
Contact or Custom Module
1:1Circa Community Partner Directory entries — external organizations and contacts receiving job postings and diversity outreach communications — map to Zoho Recruit Contacts or a custom Community Partner module. We extract partner name, contact name, email, phone, organization, diversity focus tags, and outreach history. If the partner organization has an associated Account in Zoho, the Contact is linked to that Account; otherwise, the partner organization is created as an Account and the contact is linked accordingly. Diversity focus tags migrate to a multi-select custom field.
Mitratech Circa
Affirmative Action Plan
Zoho Recruit
Custom Fields + Report
lossyCirca AAP data is derived from applicant flow logs and workforce composition snapshots and includes job group analysis, placement goals, and contractor veteran and disability metrics. Zoho Recruit has no native AAP engine. We export the AAP as a structured CSV and create custom fields on the Job Opening object (or a custom AAP module) to hold key metrics such as placement goal, job group, and veteran/disability utilization rates. The full AAP report is delivered as a written inventory document for the customer's compliance team to re-enter or link as an external report in Zoho.
Mitratech Circa
Job Board
Zoho Recruit
Reference Configuration
1:1Circa's ESDS automated job board posting configurations and posting history are tracked internally per job. Zoho Recruit has its own job board integration layer connecting to Indeed, LinkedIn, Glassdoor, and other major boards. We extract the job board subscription configuration and posting history from Circa as a reference dataset and deliver it as a written handoff document listing which boards were active per job so the customer's admin can reconfigure postings in Zoho's job board integration settings post-migration.
Mitratech Circa
Resume Database
Zoho Recruit
Candidate Attachment + Custom Field
1:1Circa maintains a searchable resume repository with parsed candidate profiles and source attribution. Zoho Recruit supports resume attachment on the Candidate record. We export resume file metadata and attachments from Circa and attach the resume file to the corresponding Candidate record in Zoho. Source attribution for each resume migrates to a custom field since Zoho's standard source field applies to the application rather than the resume itself.
Mitratech Circa
Employer Profile
Zoho Recruit
Custom Fields + Job Opening Description
lossyCirca Employer Profile settings include company description, diversity commitments, featured tags, and branding applied to job postings. We extract the profile text, tag configurations, and diversity statement as structured data and either apply this content to the Job Opening description template in Zoho or store it in a custom Employer Profile record. The profile is recreated in Zoho's Career Page settings as part of the post-migration configuration handoff.
Mitratech Circa
User Account
Zoho Recruit
User Provisioning Inventory
1:1Circa user accounts include name, role, and access level per activated feature module. We export the full user roster with role assignments as a provisioning inventory. User accounts do not map directly to Zoho User records because Zoho requires account provisioning through its own user management interface. We deliver a written user provisioning guide mapping each Circa role to the corresponding Zoho Recruit profile and role, with the customer's admin responsible for creating the actual Zoho User records before the production migration runs.
Mitratech Circa
Custom Field
Zoho Recruit
Custom Field
lossyCirca supports custom fields on Jobs, Applicants, and Community Partners depending on the active feature tier. We audit the full custom field schema from an account with full feature access during discovery, catalog every active custom field with its data type, and create matching custom fields in Zoho Recruit before any record import begins. Circa's per-tier field gating means fields created under a premium tier may not appear in exports taken from a lower-privilege account; we verify field counts against record counts to catch silent drops.
Mitratech Circa
Diversity Badge / Sourcing Tag
Zoho Recruit
Custom Multi-Select Field
lossyCirca's Diversity Badge system captures sourcing channel and diversity category at the applicant level. These badges have no native equivalent in Zoho Recruit. We create a custom multi-select picklist field on the Candidate object with options derived from the customer's active Circa badge set, and map the badge values from each applicant record into this field during the Candidate import phase.
Mitratech Circa
Interview / Assessment Record
Zoho Recruit
Candidate Activity + Custom Field
1:1Circa interview scores and assessment data linked to applicants migrate to Zoho's Interview or Candidate Activity records, with structured scores stored in custom numeric fields. If Circa stores interview as a linked entity rather than a sub-object, we denormalize the score, interviewer name, date, and feedback into a Note or a custom Interview record attached to the Candidate in Zoho.
| Mitratech Circa | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Job | Job Opening1:1 | Fully supported | |
| Applicant | Candidate1:1 | Fully supported | |
| Outreach Record | Note or Tasklossy | Fully supported | |
| Community Partner | Contact or Custom Module1:1 | Fully supported | |
| Affirmative Action Plan | Custom Fields + Reportlossy | Fully supported | |
| Job Board | Reference Configuration1:1 | Fully supported | |
| Resume Database | Candidate Attachment + Custom Field1:1 | Mapping required | |
| Employer Profile | Custom Fields + Job Opening Descriptionlossy | Fully supported | |
| User Account | User Provisioning Inventory1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| Diversity Badge / Sourcing Tag | Custom Multi-Select Fieldlossy | Fully supported | |
| Interview / Assessment Record | Candidate Activity + Custom Field1: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.
Mitratech Circa gotchas
Circa pricing is per feature, not per user
Public API documentation is not publicly available for Circa
Custom fields vary by feature tier and can be silently dropped on export
Outreach and AAP data are loosely coupled to Jobs, not embedded
Post-acquisition portfolio overlap creates dual-system risk
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 extraction method assessment
We audit the customer's active Circa deployment to confirm which feature modules are licensed (Job Posting, Outreach Management, Diversity Powered, Compliance Pro, etc.), estimate active record counts across Jobs, Applicants, Community Partners, Outreach Records, and resume attachments, and identify the available extraction method. Because Circa has no public API, extraction typically relies on application-UI CSV exports. We assess whether the customer has direct database access or a partner portal export option, and confirm feature-tier access to ensure all custom fields are visible in the export. The discovery output is a written scoping document with record volume estimates, extraction method, and migration timeline.
Zoho schema design and custom field creation
We design the Zoho Recruit target schema based on the Circa feature set in scope. This includes creating custom fields for EEOC-1 job group classification, diversity sourcing tags and Diversity Badge values, outreach history denormalization fields, and AAP metric fields on Job Openings. If Community Partner Directory is in scope, we create a custom Community Partner module or configure the standard Contacts module with the required tag fields. We also configure the Zoho job board integration settings to match the boards active in Circa, noting any ESDS-specific postings that require manual reconfiguration post-migration. Custom fields are created and validated in a Zoho Sandbox before production schema work begins.
Sandbox migration and mapping validation
We run a full migration into a Zoho Recruit sandbox using the extracted CSV files to validate the field mapping, denormalization logic, and record count reconciliation. The customer reviews the sandbox results, spot-checks migrated records against the Circa source, and signs off on the mapping spec before the production migration begins. Any field mapping corrections, placeholder value issues (such as null last names), or denormalization adjustments surface here and are resolved in the transform scripts before production.
CSV extraction and transform
We extract all active record CSVs from Circa using the confirmed extraction method and run the transform pipeline. The transform handles the denormalization of Outreach Records and AAP metrics into Zoho Notes and custom fields, replaces null last names on Candidate records with 'Not Provided', maps Circa diversity badge values to the new Zoho multi-select custom field, and preserves the original Circa entity ID in a custom field on each record for audit and reconciliation. The transform output is a set of CSVs ready for Zoho's Data Migration wizard.
Production migration in dependency order
We load records into Zoho Recruit in dependency order: Job Openings first (parent records), then Candidates with the diversity tag custom fields populated, then Community Partners as Contacts or custom module records with diversity focus tags, then Notes and custom fields for denormalized outreach and AAP history, then resume attachments attached to the corresponding Candidate record, then Employer Profile content applied to job description templates or stored as a custom record. We run row-count reconciliation after each phase and flag any discrepancies before the next phase begins.
Cutover, delta migration, and handoff documentation
We coordinate a cutover freeze with the customer — ideally a short read-only window in Circa — and run a final delta export to capture any records created or updated during the migration window. The delta is loaded into Zoho after the main migration is complete. We deliver written handoff documentation covering the active Circa workflows, automations, and ESDS posting configurations that require rebuild in Zoho; a complete list of custom fields created and their source mapping; the AAP denormalization schema and original Circa AAP record IDs for compliance audit purposes; and a Zoho user provisioning guide mapping Circa roles to Zoho profiles. We offer a one-week hypercare window for reconciliation issues raised by the recruiting team.
Platform deep dives
Mitratech Circa
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 Mitratech Circa 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
Mitratech Circa: Not publicly documented.
Data volume sensitivity
Mitratech Circa 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 Mitratech Circa to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Mitratech Circa 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 Mitratech Circa
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.