Migrate from Zinc to Salesforce Sales Cloud

Zinc's Candidate record maps directly to Salesforce Contact. Name, email, phone, address, and LinkedIn URL translate to standard Contact fields. Original create and update timestamps are preserved as custom datetime fields since Salesforce's CreatedDate reflects the migration load date, not the original record date.

Zinc stores employment history as an array of objects within the Candidate record. Each employment entry becomes a separate Employment_History__c record with a lookup to the Contact. Job title, company name, start/end dates, and responsibilities map to custom fields on the custom object.

Zinc's background-check results attach to the Candidate record as structured data (check type, status, completed date, verdict). Since Salesforce has no native background-check object, we create a Background_Check__c custom object with lookup to Contact and fields for each data point. If only a single check is needed per candidate, a set of custom fields on Contact suffices.

Zinc tracks onboarding as a step-by-step checklist (document signed, equipment provisioned, IT access granted, training completed). Each step becomes an Onboarding_Milestone__c record with a pick-list for milestone type, a status field, and a completion date. The parent Contact represents the employee being onboarded.

Zinc positions (open roles being hired) can map to a custom Position__c object for reference. If the hiring process includes revenue-linked positions, Opportunity records with a custom Position__c lookup capture the recruiting pipeline as a sales-like funnel in Salesforce, with stage values for sourcing, screening, interviewing, and offer.

Zinc interview records (interviewer, candidate, date/time, feedback) map to Salesforce Event records linked to the Contact. Event Type field captures the interview stage; Event Description holds the feedback summary. Interviewer email resolves to the Salesforce user record via email matching.

Zinc's reference records (referee name, relationship, contact info, responses) migrate to a custom Reference__c object with a lookup to the Contact (candidate). Reference responses and ratings map to custom fields on the object. Salesforce does not have a native reference-tracking object.

Zinc reference records capture referee name, relationship type, contact information, ratings, and written response notes for each candidate. Each reference migrates as a separate Reference__c custom object record linked to the Contact representing the candidate via a lookup relationship. Ratings and response text populate custom fields on the Reference__c object. Salesforce lacks a native reference-tracking entity, so the custom object is created during the schema setup phase with fields matching Zinc's data structure. If your organization uses an AppExchange reference-management application, FlitStack can map to that app's objects instead provided you supply the API names during planning.

Zinc attachments (resumes, cover letters, signed documents) are downloaded and re-uploaded to Salesforce as ContentDocuments linked to the relevant Contact or custom object. File size limits of 25MB per Salesforce file apply; larger files require chunked upload or external storage with a link stored in Salesforce.

Zinc users (recruiters, hiring managers) resolve to Salesforce users by email address. Unmatched users are flagged before migration so the team can either invite them to Salesforce or assign records to a fallback owner. Role and team membership from Zinc maps to Salesforce Role and Permission Sets.

Zinc's reference-checking and onboarding automation sequences do not have a direct Salesforce equivalent. FlitStack AI exports the workflow definitions as JSON with step logic, triggers, and conditions. Your Salesforce admin rebuilds these in Flow using the exported definitions as a configuration reference.

Zinc email templates used in reference-request communications and onboarding notification sequences do not migrate automatically. FlitStack AI exports the complete template content as HTML files including styling, merge fields, and body copy. Your team recreates these as Salesforce Email Templates or Apex-based templates using the exported HTML as the starting point. Salesforce supports Visualforce email templates and Lightning email templates; the appropriate format depends on your org's configuration. This manual recreation step is scoped separately from the data migration and typically takes 1–3 days depending on the number of templates and their complexity.