Migrate from ZenApply to Crelate

ZenApply Jobs map to Crelate Job records. We extract Job name, description, department, and status from the CSV export. The salary range field is not included in ZenApply's standard export and must be manually added during export preparation or sourced separately from the customer. Open and closed status maps directly to Crelate's active and inactive Job status.

ZenApply Application records link a Candidate to a Job. We preserve Application status, submission date, and source attribution. Status values vary by customer-configured pipeline in ZenApply, so we normalise them against Crelate's configurable status picklist during field mapping. The Application record is the parent for any associated scorecard data and attachments.

ZenApply Candidates map to Crelate Contact records. Standard fields (name, email, phone, address) transfer directly. Custom profile fields require field-by-field enumeration during scoping because ZenApply does not expose an admin schema export. Any missed custom field will not appear in Crelate; we use a structured discovery questionnaire to capture every active custom property before writing the mapping spec.

ZenApply video resume assets are hosted URLs rather than downloadable file blobs. We download each video to temporary storage during the migration window, then re-upload to Crelate as attachments on the corresponding Contact record or to an agreed media host. This step extends the timeline by 1-2 days per 100 video assets. URLs must be transferred before the ZenApply account is deactivated or they become invalid.

ZenApply custom profile fields (per-position and global) require manual discovery walkthrough with the customer because no admin schema export exists. We map each discovered custom field to a Crelate custom field of the equivalent type (Short Answer, Long Answer, Picklist, Date, Numeric, Monetary). Crelate supports field-level audit logging on custom fields from the Business plan upward.

ZenApply scorecard templates and individual ratings link to Applications and Interviewers. We preserve the scorecard structure as a Crelate Activity Form template and map individual ratings to the corresponding custom fields on the Contact record. Reviewer comments migrate as free-text fields. Note that scorecard rebuilding as native Crelate forms requires post-migration admin configuration.

ZenApply User records include name, email, and role (Admin, Hiring Manager, Recruiter). We map active Users to Crelate User accounts by email match. Unrecognised role types or inactive ZenApply users are flagged in a reconciliation report for the customer's admin to resolve before record migration proceeds.

Resume files, cover letters, and portfolio attachments stored as file URLs are downloaded from ZenApply and re-uploaded to Crelate as Contact attachments. Original filenames and MIME types are preserved. The customer must ensure the ZenApply account remains active during the attachment download phase; we recommend scheduling attachment extraction before the account closure step.

Application source attribution (e.g., LinkedIn, Indeed, referral) from ZenApply maps to Crelate's candidate source tracking field. Crelate's Business plan includes Candidate Source Tracking as standard. If ZenApply used custom source labels, we normalise them against Crelate's picklist or create new source values during mapping.

ZenApply position-level pipeline stages map to Crelate Job Pipeline status values. We configure the destination Crelate pipeline (including any custom status labels) before migration so that Application status values map correctly during import. Crelate supports multiple pipelines from the Business plan upward.

ZenApply email templates used in automated candidate communication are identified during scoping. Crelate supports email templates with merge fields from the Business plan. Templates migrate as text content; the customer rebuilds any HTML email design in Crelate's template editor post-migration.

ZenApply free-form notes and tasks attached to Applications or Candidates map to Crelate Activity records. Note body transfers as rich text. Task status, due date, and assignee migrate with Owner resolved via email match to the Crelate User table. Any task with an unresolvable assignee goes to a reconciliation queue.