Migrate from ZippyApp to Recruit CRM & ATS

ZippyApp Job Seeker records include name, contact details, resume file, cover letter attachment, and application history. We extract these fields and map them to Recruit CRM Candidate records. The full application timeline is preserved as a chronological Activity log on the Candidate record. Resume files migrate as binary attachments linked to the Candidate. We parse name into First Name and Last Name fields and flag any record missing a contact email for admin review before import.

ZippyApp Employer accounts store company profile, industry vertical, branding details, and hiring-team members. We map each Employer to a Recruit CRM Client record, preserving the company name as Client Name and extracting the industry field where visible. Employer hiring team members map to Recruit CRM Users with matching email addresses; any team member without an existing Recruit CRM User is flagged for the customer's admin to provision before production migration.

ZippyApp Positions (job title, description, location, and QR code) map directly to Recruit CRM Job records. The Position title becomes Job Title, description becomes Job Description, and location becomes the Job Location field. We preserve the QR code URL as a custom text field on the Job record if the customer wants to maintain the original application-discovery link. Job status (open/closed) maps to Recruit CRM's job status field.

ZippyApp Application records link a Job Seeker to a Position with a status field (submitted, reviewed, dispositioned). We map each Application to a Recruit CRM Application record linked to the corresponding Candidate and Job. The Application status migrates to Recruit CRM's application status values. Because ZippyApp's flat model does not distinguish between candidate and employee, we create the Application record in Recruit CRM rather than a Placement record.

Resume files stored as attachments to ZippyApp Job Seeker records are extracted as binary blobs and attached to the corresponding Recruit CRM Candidate record. PDF and DOCX parsing is attempted via Recruit CRM's built-in resume parsing on upload. Any resume file that fails parsing is stored as a raw attachment with a note indicating the original format. We track the original file name and upload timestamp as metadata on the attachment.

Cover letters are optional file attachments per Application in ZippyApp. We attach each cover letter to the same Candidate record in Recruit CRM, tagged with the source Application reference. We flag any candidate record with a cover letter present so the recruiting team knows to review it during screening. Cover letters that are text-only in ZippyApp (not uploaded files) are stored as notes on the Candidate record.

ZippyApp application statuses (submitted, reviewed, shortlisted, rejected, hired) map to Recruit CRM application status picklist values. We configure the destination picklist to match the source status set before migration. Any status value not present in Recruit CRM's default set is added as a custom status option. A verified reviewer noted accidental application dispositioning in ZippyApp's browse queue; we pull the raw status field rather than relying on bulk-export data that may carry unintended status changes.

ZippyApp stores hiring team members (name, email, role) per Employer account. We map these to Recruit CRM User records by email address match. The customer's admin reviews role mapping during scoping since ZippyApp's team-role model does not have a direct Recruit CRM equivalent; roles are mapped to Recruit CRM's team permission levels (Admin, Recruiter, Hiring Manager) at the customer's direction.

ZippyApp records the timestamp of each application submission. We preserve this as the Application Created Date in Recruit CRM to maintain the candidate pipeline timing history. The application modification timestamp migrates as a custom field for audit purposes.

ZippyApp Employer accounts may include an industry vertical field. We extract this value and map it to the Client Industry field in Recruit CRM. If the industry field is absent or incomplete in ZippyApp, we leave the Client Industry blank and flag it for the customer's admin to populate during onboarding.

ZippyApp push notifications and email alerts are transient communication events stored only in the notification stream, not as persistent records. We do not migrate them. The candidate's application submission timestamp, status change events, and any recruiter notes recorded in ZippyApp migrate as Activity Log entries in Recruit CRM, which provides the persistent timeline that notifications represent.

ZippyApp employer logos and brand color settings are media assets without a standard ATS object equivalent. We exclude them from migration scope. If the customer wants to preserve employer branding in Recruit CRM, we document the logo file names and brand color values in the gap report for manual re-upload to the Client record.