Migrate from ZippyApp to Zoho Recruit

ZippyApp Job Seeker records contain name, email, phone, resume (PDF or DOCX), cover letter (optional), and application history with timestamps. We extract these fields and map them to Zoho Recruit Candidate records. The candidate's email becomes the primary dedupe key. Resume files are extracted as binary blobs and attached to the Candidate record in Zoho Recruit. Cover letters are attached as separate files and flagged with a custom text field indicating cover letter was included. Application history is preserved as an activity log in Zoho Recruit's candidate timeline.

ZippyApp Employer accounts store company profile, industry vertical, branding details, and hiring team members. We map these to Zoho Recruit's Client module (for staffing/agency use) or the Organization module (for corporate in-house recruiting). The employer industry vertical becomes a picklist value in Zoho Recruit. Hiring team members are mapped to Zoho Recruit Users with a custom role field indicating their ZippyApp employer-level role. Note that custom employer branding assets (logos, brand colors, QR graphics) do not migrate because Zoho Recruit stores client logos as standard image fields, not the full brand asset set.

ZippyApp Positions include job title, description, location, employment type, and the QR code used for candidate discovery. We map these to Zoho Recruit Job Opening records. The QR code URL or value from ZippyApp is preserved as a custom text field on the Zoho Recruit Job Opening for reference. Job Opening status (open, paused, closed) maps directly to Zoho Recruit's status picklist. Each Job Opening is linked to the corresponding Client or Organization record that owns the position.

ZippyApp Applications link a Job Seeker to a Position with a status field (submitted, reviewed, interview, offer, hired, rejected). Zoho Recruit does not have a native Application record type separate from the Candidate-to-Job Opening association, so we create a custom Candidate Applications module in Zoho Recruit to preserve the full application lifecycle. The custom module stores original application date, current status, status change timestamps, and reviewer notes. Standard Edition customers should note that Custom Modules require Professional tier or above.

Resume files attached to ZippyApp Job Seeker records are extracted as binary files and attached to the corresponding Zoho Recruit Candidate record via the Attachment functionality. We note the file format (PDF versus DOCX) in a custom picklist field on the Candidate. Zoho Recruit's resume parsing (powered by Zia AI on Professional+ tiers) can re-parse the uploaded resume to populate structured Candidate fields after migration, which we trigger as a post-migration step.

Cover letters are optional attachments per application in ZippyApp. We extract them and attach them to the same Zoho Recruit Candidate record, tagging the file with a custom field indicating file type (Cover Letter) so recruiters can distinguish from resume attachments in the candidate portal. If no cover letter was submitted for a given application, we leave the field blank.

ZippyApp Employer accounts include one or more hiring team members who review applications. We extract these user records and map them to Zoho Recruit Users by email address. The user's role in ZippyApp (admin, recruiter, hiring manager) is preserved as a custom picklist field on the Zoho Recruit User. We do not migrate login credentials; Zoho Recruit Users must be provisioned by the customer's admin during the migration window.

ZippyApp position statuses (open, paused, closed) map to Zoho Recruit Job Opening status values. We map 'open' to Active, 'paused' to On Hold, and 'closed' to Closed. Any custom statuses defined by the employer are documented in the gap report and mapped to the closest Zoho Recruit standard status, with a note that custom status values require Professional tier or above.

Each application status change in ZippyApp generates a timestamped record in the application history. We extract these status transitions (e.g., submitted on 2024-01-15, reviewed on 2024-01-18, rejected on 2024-01-22) and create corresponding Zoho Recruit Activity log entries attached to the Candidate record. This preserves the full disposition timeline for compliance and audit purposes.

If ZippyApp captures job seeker availability (preferred shift, start date, location preference) as part of the application, we map these to custom Candidate fields in Zoho Recruit. These fields require Professional tier because custom fields are not available in the Free Edition. We flag this requirement during scoping if availability data is present in the ZippyApp export.

ZippyApp stores position city and state or full address. We map these to Zoho Recruit Job Opening location fields. If ZippyApp includes latitude/longitude for the QR code anchor point, we preserve these as custom number fields for reference.

The QR code generated for each ZippyApp position is a discoverability mechanism specific to ZippyApp's in-store hiring flow. We extract the QR code URL or the encoded job URL and store it as a custom text field on the Zoho Recruit Job Opening for reference. This field is informational; Zoho Recruit's job board posting and career page features replace the QR code discovery method post-migration.