Phase 0
Decide & Plan
Decisions that must be made before any extraction work starts.
-
Risk if skipped: Choosing Corporate HR when the operation is staffing locks Clients and Vendors out, forcing a re-purchase and re-provision.
-
Risk if skipped: Late-discovered Modules force schema changes mid-migration and trigger re-runs of upstream transform jobs.
-
Risk if skipped: Without a decision, every report shows every candidate created on cutover day, which destroys time-to-fill and source-of-hire trends.
-
Risk if skipped: Provisioning in the wrong DC cannot be reversed by moving data later — it requires a fresh org and a second migration.
-
Risk if skipped: Without written criteria, the migration drags on indefinitely because nobody can declare it done.
Phase 1
Pre-Migration Prep
Everything that must be true before the first byte leaves the source.
1a. Source-system audit and cleansing
-
Risk if skipped: Without a baseline, you cannot prove what was lost in transit.
-
Risk if skipped: Duplicate Candidates post-load split resume history and interview feedback across two records.
-
Risk if skipped: Rows with empty mandatory fields are silently skipped by the importer and do not appear in the destination.
-
Risk if skipped: Missing source statuses cause Application rows to land in the default Screening stage instead of the correct historical stage.
-
Risk if skipped: Loading 50 GB of resumes into a Professional org (2 GB default) saturates storage and blocks new uploads.
1b. Destination-system setup
-
Risk if skipped: Skipping a sandbox forces every test to happen in production where recruiter users see test candidates.
-
Risk if skipped: Single-user orgs cannot start a Data Migration job — the wizard blocks until a second user is added.
-
Risk if skipped: Changing time zone after import does not retroactively re-stamp records and creates an off-by-N-hours bug on every interview timestamp.
-
Risk if skipped: Silent column drops are the single most common cause of Phase 6 reconciliation gaps.
-
Risk if skipped: Unknown picklist values are rejected row-by-row and the row is skipped.
-
Risk if skipped: Without a Unique field, the importer cannot match incoming rows to existing records and inserts duplicates on every rerun.
-
Risk if skipped: Applications referencing a status that is not mapped to a stage land outside the pipeline view and become invisible to recruiters.
-
Risk if skipped: An active candidate-welcome workflow during a 10,000-Candidate load emails every candidate at cutover.
1c. People prep
Phase 2
Source Export
Get all ATS data out of the source system in a form you can transform.
-
Risk if skipped: Exporting Applications without both foreign keys forces manual re-association at scale, which is error-prone.
-
Risk if skipped: Treating email history as a standard Note loses the threading and sender metadata.
-
Risk if skipped: Files larger than the per-record cap silently leave the Candidate unlinked from their own resume.
Phase 3
Transform & Map
The data-engineering core. Take raw exports and produce Zoho-shaped files.
3a. Mapping spreadsheet
-
Risk if skipped: Without a single mapping document, transform logic drifts between engineers and reconciliation finger-pointing becomes unavoidable.
-
Risk if skipped: Importing a Currency value into a Picklist field returns 'Import Failed Abruptly' and the entire job halts.
-
Risk if skipped: Mismatched picklist values cause row-level skips at insert time, with the row reported in the import error log but not loaded.
3b. Data transformation
-
Risk if skipped: Date-format mismatches at import time cause every Date column to land null or rejected.
-
Risk if skipped: Non-UTF-8 files cause accented characters to corrupt to mojibake on Candidate names.
-
Risk if skipped: Rows exceeding field width are skipped during bulk import with INVALID_DATA errors.
-
Risk if skipped: Oversize zip files throw an error before any record is loaded.
3c. Relationship and audit-trail decisions
-
Risk if skipped: Reporting on Created Time shows every record dated to migration day, which destroys time-series trend analysis on hiring velocity.
-
Risk if skipped: Re-uploading 50 GB of resumes into a Professional org (2 GB cap) saturates storage and blocks new uploads.
-
Risk if skipped: Re-parsing resumes after migration overwrites human-curated Candidate fields with parser output, which is often less accurate.
-
Risk if skipped: Out-of-order loads leave Application rows with broken Candidate or Job Opening lookups and no error message.
-
Risk if skipped: Attempting to model many-to-many on Standard or Professional editions silently flattens to one-to-many and loses associations.
3d. ATS-specific transforms
-
Risk if skipped: Applications referencing an unmapped status fall outside the pipeline view and become invisible to recruiters.
-
Risk if skipped: Letting Resume Extractor run on every re-uploaded resume overwrites the transferred Skill, Experience, and Education fields with parser output.
-
Risk if skipped: Pipeline velocity reports for periods before cutover will be empty because Modified Time is overwritten on every subsequent status change.
-
Risk if skipped: Source-of-hire dashboards break if source values land as free text instead of picklist entries.
-
Risk if skipped: Loading EEOC data into an unrestricted field exposes protected-class data to every recruiter, creating an EEO violation.
-
Risk if skipped: Mixing rating types within one assessment template forces a manual choice at every interview and breaks score-roll-up reports.
-
Risk if skipped: Loading opted-out candidates as opted-in is a CAN-SPAM and GDPR violation.
Phase 4
Sandbox Test Migration
Catch every problem in Sandbox before it costs you in production.
-
Risk if skipped: Sampling fewer than 10 records misses field-level drops that only surface on certain Candidate subtypes.
-
Risk if skipped: An untested status discovered in production leaves Applications outside the pipeline and invisible to recruiters.
-
Risk if skipped: Character-encoding bugs are invisible until a recruiter opens the Candidate and sees mojibake.
-
Risk if skipped: If Resume Extractor unexpectedly overwrites fields, every Candidate's transferred data is silently degraded.
-
Risk if skipped: EEOC field permission misconfiguration leaks protected-class data to every recruiter.
-
Risk if skipped: Verbal sign-offs evaporate when reconciliation surfaces an issue post-cutover.
Phase 5
Production Cutover
Tightly sequenced execution window. Densest cluster of risk.
-
Risk if skipped: Skipping the delta loses every Candidate, Application, and Interview created between Phase 2 export and cutover.
-
Risk if skipped: An active candidate-welcome workflow at cutover sends thousands of accidental candidate emails in minutes.
-
Risk if skipped: Out-of-order loads leave lookup fields blank with no error and require a second pass to repair.
-
Risk if skipped: Insert-only loads on partial failure create duplicate Candidates on retry.
-
Risk if skipped: Pushing through with an unexplained count delta makes Phase 6 reconciliation impossible.
-
Risk if skipped: Without a clean post-load snapshot or a tracked Import History job, partial rollback requires per-record manual cleanup.
Phase 6
Validate
Prove the migration was correct before letting end users in.
6a. Reconciliation
-
Risk if skipped: Unexplained deltas typically trace to skipped picklist values, missing mandatory fields, or status-to-stage mismatches.
-
Risk if skipped: Stage-count mismatches typically trace to unmapped source statuses landing in default Screening.
-
Risk if skipped: Null External IDs force every subsequent upsert to treat the record as new, creating duplicates.
6b. Relationship validation
-
Risk if skipped: Orphaned Interviews sit in the global Interviews view but never appear in the Candidate timeline.
6c. Audit and compliance
-
Risk if skipped: EEOC field exposure to non-Compliance Profiles is an EEO violation.
-
Risk if skipped: Audit logs older than 60 days are not retained in the Audit Log view; pulling them now is cheap, retrieving them later may not be possible.
6d. User-acceptance check
6e. Sign-off
-
Risk if skipped: Proceeding without sign-off leaves the project in a perpetual 'almost done' state.
Phase 7
Post-Migration Cleanup
Wrap up so the team can move on.
-
Risk if skipped: Job-board re-sync without External-ID checks duplicates every Candidate that applies again post-cutover.
-
Risk if skipped: Discarding exports too early eliminates forensic options if a data-quality issue surfaces months later.
Watch list
Risks to track throughout
These risks live across multiple phases — keep an eye on them from kickoff through cutover.
-
Candidate Status to Hiring Pipeline Stage mapping is the silent failure mode
Zoho Recruit's Hiring Pipeline groups Candidate Statuses into Stages. An Application referencing a status that is not mapped to a stage lands outside the pipeline view and becomes invisible to recruiters even though the row exists. Track this risk from Phase 1 (build the pipeline and map every status) through Phase 3 (transform value mapping) through Phase 4 (test every status) through Phase 6 (reconcile per-stage counts).
-
System-managed Created Time cannot be overridden on bulk load
Zoho Recruit stamps Created Time and Modified Time at the moment of insert. Bulk imports do not let you supply a historical timestamp for these fields. The workaround is a 'Source Created Date' custom Date field per Module, populated during transform. Any time-to-fill or source-of-hire report that depends on Created Time will be wrong for pre-cutover records — flag this to the talent-analytics team in Phase 0.
-
Resume Extractor overwrite of transferred Candidate fields
When a resume is uploaded to a Candidate, Resume Extractor parses it and writes Skills, Education, and Work History fields. If those fields were already populated from the source migration, the parser output silently overwrites them. Decide in Phase 3 whether to suppress Resume Extractor on bulk re-uploads, validate the decision in Phase 4, and confirm no overwrites occurred in Phase 6.
Related
Common migrations to Zoho Recruit
Every link below is a dedicated pair page covering field-level mapping, edge cases, and pitfalls for that specific source-to-destination move.
Pair this with the long-form guide
The complete Zoho Recruit migration guide
Same research, written as prose: data model, import mechanisms, mapping strategy, pitfalls, and partner landscape.