Migrate your Zinc data
Automated pre-employment reference-checking platform with ATS/HRIS integrations. Customers use it to replace manual reference calls with structured digital workflows.
In its favor
Why people choose Zinc
The signal that keeps Zinc on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Automates reference checking that otherwise consumes 3–5 hours per hire across scheduling, chasing, and transcribing calls.
Delivers structured, scored reference data rather than vague verbal recollections — giving hiring teams defensible data to act on.
Integrates directly with ATS platforms like Greenhouse and HRIS systems like Rippling, reducing duplicate data entry in hiring workflows.
Offers a short-form candidate experience that users describe as quick and friction-free, improving completion rates.
Delivers completed reference reports in a central dashboard, replacing scattered email threads and giving HR teams a single source of truth.
Lack of live chat support forces users to rely on a chatbot or email, which some find inadequate for time-sensitive hiring queries.
Admin visibility into usage volumes — how many checks remain or have been used — is limited in the standard UI, frustrating finance and HR operations teams.
Custom check builder lacks an accessible backend view for some administrators, making it hard to audit or manage check usage at scale.
Reasons to switch
Why people leave Zinc
The recurring reasons buyers give for replacing Zinc. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Zinc fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Zinc pricing overview
Zinc Work uses a subscription-based pricing model with tiered plans. Pricing is not publicly disclosed; volume and feature access vary by plan. Enterprise customers typically negotiate custom contracts based on hiring volume.
Starter
Tier 1 of 3
Not publicly listed
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Zinc's schedule — see our quote-based pricing →
What gets migrated
Zinc object support
Object-by-object support for Zinc migrations. Per-pair details surface during scoping.
Candidates
Fully supportedCandidates are the primary record in Zinc Work — the individual being checked. We migrate candidates 1:1 with their name, email, status, and created timestamp. Custom candidate properties are mapped field-by-field at scoping.
Reference Checks
Fully supportedReference Checks link a candidate to a referee and track status through sent, pending, completed stages. We preserve the full status history and timestamps for each check.
Reference Responses
Fully supportedReference Responses are the structured data returned by referees — scores, free-text answers, and recommendation fields. We carry these over intact, preserving all score dimensions and narrative text.
Check Templates
Mapping requiredCustom check templates with bespoke question sets vary by customer. We map the template structure and its questions but flag any custom scoring rubrics that may not map directly to the destination system.
Users
Fully supportedAdmin and HR user accounts, including role assignments (admin, viewer). We migrate user records with role flags and preserve team assignments where present.
Integrations
Mapping requiredZinc Work connects to ATS platforms (Greenhouse, Lever, Ashby) and HRIS systems (Rippling, BambooHR, Bob). Integration configuration and webhook settings are not automatically migrated — we document them for reconfiguration post-migration.
Reports
Fully supportedCompleted reference reports with aggregate scores and summary narratives. We export these as structured records alongside the raw responses.
Audit Logs
Not in this platformZinc Work maintains immutable audit logs of who requested what check and when. These are not accessible via the customer-facing API and are not migrated.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | Candidates are the primary record in Zinc Work — the individual being checked. We migrate candidates 1:1 with their name, email, status, and created timestamp. Custom candidate properties are mapped field-by-field at scoping. |
| Reference Checks | Fully supported | Reference Checks link a candidate to a referee and track status through sent, pending, completed stages. We preserve the full status history and timestamps for each check. |
| Reference Responses | Fully supported | Reference Responses are the structured data returned by referees — scores, free-text answers, and recommendation fields. We carry these over intact, preserving all score dimensions and narrative text. |
| Check Templates | Mapping required | Custom check templates with bespoke question sets vary by customer. We map the template structure and its questions but flag any custom scoring rubrics that may not map directly to the destination system. |
| Users | Fully supported | Admin and HR user accounts, including role assignments (admin, viewer). We migrate user records with role flags and preserve team assignments where present. |
| Integrations | Mapping required | Zinc Work connects to ATS platforms (Greenhouse, Lever, Ashby) and HRIS systems (Rippling, BambooHR, Bob). Integration configuration and webhook settings are not automatically migrated — we document them for reconfiguration post-migration. |
| Reports | Fully supported | Completed reference reports with aggregate scores and summary narratives. We export these as structured records alongside the raw responses. |
| Audit Logs | Not in this platform | Zinc Work maintains immutable audit logs of who requested what check and when. These are not accessible via the customer-facing API and are not migrated. |
Gotchas
What to watch for in Zinc migrations
Issues we've hit on past Zinc migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Integration settings do not migrate automatically
Custom check templates with bespoke rubrics require field-level mapping
Audit logs are not accessible for export
| Severity | Issue |
|---|---|
| High | Integration settings do not migrate automatically |
| Medium | Custom check templates with bespoke rubrics require field-level mapping |
| Low | Audit logs are not accessible for export |
Leaving Zinc?
Where Zinc customers move next
12 destinations Zinc can migrate to.
How a Zinc migration works
Four steps, Zinc-specific
Connect
Client token via HTTP Basic Auth into Zinc. Scopes limited to read-only on the data we move.
Map
We translate Zinc-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Zinc quirks before production.
Migrate
Full migration with Zinc rate-limit handling. Rollback available throughout.
FAQ
Zinc migration FAQ
Answers to the questions buyers ask most during Zinc migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Zinc migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Zinc.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Zinc setup and destination — written quote back within a business day.