Migrate from ZippyApp to Crelate

ZippyApp Job Seeker records contain name, contact details, resume, cover letter, and application history. We extract these as Crelate Person records, mapping the ZippyApp email address to the Person email field and name fields to Crelate's structured name fields. The Job Seeker's application history is preserved by linking each migrated Application to the corresponding Person record via the Crelate Person-Job association. If a Job Seeker applied to multiple Positions under the same employer, the Person record in Crelate will have multiple associated Job entries, matching ZippyApp's shared-profile design.

ZippyApp Employer accounts store company profile, branding details, and hiring team members. We map these to Crelate Company records, with the employer name as Company Name and industry vertical stored in a custom Company field if present in ZippyApp. The employer-branding assets (logos, QR graphics) are excluded as they have no standard ATS equivalent and would require manual re-upload in Crelate.

ZippyApp Positions map directly to Crelate Job records. Each Position carries a title, description, location, and status (open, filled, closed). We map Position title to Job title, Position description to Job description, and Position status to the appropriate Crelate Job status value. The QR code associated with each Position is documented in a custom field on the Crelate Job record for reference, but the QR graphic itself is not migrated.

ZippyApp Applications link a Job Seeker to a Position with a status field. We create a Crelate Job-Person association with status preserved. The application status requires extraction from the raw status field in the employer inbox view rather than from bulk-action exports, due to a documented ZippyApp UI issue where browsing can accidentally trigger archive or disposition actions. We also preserve the application submission timestamp as a custom field on the association for timeline ordering.

Resume files are stored as binary attachments on ZippyApp Job Seeker records. We extract each resume as a file (supporting PDF and DOCX formats) and attach it to the corresponding Crelate Person record. Crelate's attachment handling preserves the original filename and file type. We flag any parsing failures (corrupted files, password-protected PDFs) in the gap report for manual re-upload by the customer.

Cover letters are optional per-application attachments in ZippyApp. We attach each cover letter to the corresponding Crelate Person record, naming it with the pattern '{Person Name} - Cover Letter.pdf' to distinguish it from the resume attachment. If the cover letter was submitted for a specific Position, we add a note to the Job-Person association referencing the cover letter attachment.

ZippyApp's custom application forms store candidate answers per application. Crelate's field mappings feature allows these answers to be copied directly into custom fields on the parent Person or Job record. We configure Crelate field mappings during the Development phase, creating custom fields for each distinct ZippyApp application question, then activating field mappings so the data flows automatically after migration. The customer reviews field mapping output during the Testing phase before production migration.

Push notifications and email alerts generated by ZippyApp during the hiring workflow are transient communication events stored only in the candidate's email client and the ZippyApp notification system. They are not persistent records in ZippyApp's database and are therefore not migrated. Candidates can re-subscribe to Crelate's notification settings during onboarding.

Logos, brand colors, and QR-code graphics tied to ZippyApp employer accounts are media assets that do not map to any standard ATS object. We document each employer's branding assets in the gap report with the asset location in ZippyApp and recommend manual re-upload to Crelate's employer profile settings post-migration.

ZippyApp stores in-progress applications in a queue accessible via the employer inbox. These records are recoverable if the candidate navigates away before submitting. We extract in-progress applications as Crelate Job-Person associations with a custom status value 'In Progress (ZippyApp)' and flag them for the customer's recruiter to contact the candidate for re-submission in Crelate or to complete the application manually.

ZippyApp stores hiring team members on the employer account. We extract each team member's name and email and map them to Crelate User records. Owner assignment on migrated Jobs and Companies resolves to the corresponding Crelate User by email match. Any ZippyApp team member without an existing Crelate User account is added to the reconciliation queue for the customer's admin to provision before production migration.

ZippyApp tracks how candidates discovered each Position, including whether they applied via QR code scan, direct link, or job board referral. We map this source attribution to a custom field on the Crelate Job-Person association so that the customer's recruiting team retains visibility into which channels generated applications. This is a non-standard ZippyApp field that has no direct Crelate equivalent without custom field creation.