Migrate from mploy to Zoho Recruit

mploy User accounts (admin, recruiter, hiring manager roles) map to Zoho Recruit Users imported via CSV before any candidate or job data. We resolve each mploy user by email address against the Zoho Recruit destination account and flag any users without email for manual Zoho User provisioning. Role assignments from mploy map to Zoho Recruit's role model (Admin, Recruiter, Standard) during the import wizard setup. Importing Users first satisfies the OwnerId lookups required on Candidates and Job Openings.

mploy Candidates represent job applicants with standard fields (name, email, phone, resume) plus any customer-specific custom fields enumerated during discovery. We map these to Zoho Recruit Candidates, enforcing Zoho's mandatory Last Name field: any mploy Candidate record without a last-name value receives a placeholder of 'Not Provided' before import to prevent record rejection. Resume files stored in the candidate export archive attach to Zoho Recruit Candidate records via the Attachments module after primary field import completes.

mploy Job records (title, department, location, description, open/closed status) map to Zoho Recruit Job Openings. Active and archived jobs migrate to preserve closed requisition history. Job status (open/closed) maps to the Zoho Recruit Opening Status field. We resolve the Department from mploy to Zoho Recruit's Department picklist or create a matching custom picklist value during import wizard setup.

mploy Applications are the join records linking Candidates to Jobs, capturing submission date, stage in pipeline, and source attribution. In Zoho Recruit, applications appear as job associations on Candidate records via the Job Applications subtab. We map the mploy application submission date to Zoho Recruit's Applied Date field and the pipeline stage to the Zoho Recruit Hiring Process stage. Source attribution (Indeed, LinkedIn, direct) migrates to the Source field on the candidate record.

mploy pipeline stages (Applied, Phone Screen, Interview, Offer, etc.) map to Zoho Recruit Hiring Process stages. We preserve the ordered stage sequence from mploy by configuring matching stage names in Zoho Recruit's Hiring Process before candidate import. Stage names vary by customer configuration, so the stage mapping is defined during the discovery enumeration step and deployed as part of the Zoho Recruit Hiring Process setup before data migration begins.

mploy Offer records containing compensation details, start dates, and acceptance status map to Zoho Recruit Offers. We migrate Offer fields (offered salary, start date, offer status) to Zoho Recruit's offer module fields and link each Offer to the corresponding Candidate and Job Opening via Zoho Recruit's relationship model. If mploy stores offers as a custom field on Applications rather than a standalone object, we map those values into Zoho Recruit's structured Offer module during transformation.

mploy Department assignments on Jobs map to Zoho Recruit Departments. We create matching Department records in Zoho Recruit during the pre-migration setup phase so that Job Opening imports can reference the correct Department lookup. If mploy stores departments as free-text fields rather than structured records, we extract distinct values during discovery and pre-create matching Zoho Recruit Departments before the main migration run.

mploy custom fields on Candidates require explicit enumeration during discovery because no public schema documentation exists. We export field definitions and values from mploy via admin-panel screenshots or CSV exports showing field headers, then map each to a Zoho Recruit custom field of equivalent type (text, number, picklist, date, checkbox). The Zoho Recruit field creation step happens during import wizard setup before candidate records are imported. Any picklist values in mploy custom fields are pre-created in Zoho Recruit as matching picklist options.

mploy custom fields on Jobs are enumerated during discovery and mapped to Zoho Recruit custom fields on Job Openings. Common examples include department-specific requisition metadata, hiring manager references, or compensation range fields. We create matching Zoho Recruit custom fields during the import wizard configuration phase and map values from mploy CSV exports during the main migration run.

Resume files and uploaded attachments in mploy are stored separately from the candidate CSV export and require a separate file archive request. We map the attachment file names to Zoho Recruit Candidate Attachments using the Candidate Email or Candidate ID as the linking key. If mploy does not include attachments in the bulk download, we request a separate file archive during discovery and confirm attachment coverage before migration sign-off.

Interview records in mploy are not confirmed as a separately exportable object, so we capture interview data as notes attached to the relevant Candidate record if present. Where mploy stores interview details as structured records, we map interviewer name, interview date, interview type, and feedback summary to Zoho Recruit Interview records linked to the Candidate. This mapping is confirmed during discovery scoping with the customer's mploy admin.

Candidate and Job notes from mploy migrate to Zoho Recruit Notes attached to the corresponding record. We preserve the note body, author, and creation timestamp. Notes on Jobs map to Notes on Job Openings; notes on Candidates map to Notes on Candidates. The note author resolves to a Zoho Recruit User by email match where possible, or is stored as free text if no matching User exists.