Migrate from Zinc to Pipedrive

Zinc Work candidates map directly to Pipedrive People. Name, email, phone, job title, and address fields carry over as direct mappings. Candidates without an associated organization land as standalone Pipedrive People records — your admin can link them to a Pipedrive Organization after migration if a company relationship becomes clear.

Individual reference check records in Zinc Work are too rich for a single custom field. FlitStack migrates each completed reference as a Pipedrive Note attached to the corresponding Person record. The Note body contains reviewer name, relationship to candidate, check status, submitted date, and key findings. This preserves the full reference narrative inside Pipedrive's activity timeline.

Zinc Work tracks reference check status natively (pending, in-progress, completed, verified, etc.). Pipedrive has no built-in equivalent. FlitStack creates a custom pick-list field (Reference_Check_Status__c) on the Person object and maps each Zinc Work status value directly. Your Pipedrive admin defines the pick-list options to match Zinc Work's status taxonomy before migration.

Zinc Work supports custom check types that define which fields appear per reference request — background check results, employment verification flags, credential checks, etc. Each unique custom field in Zinc becomes a custom field in Pipedrive on the Person object. The field type in Pipedrive (text, pick-list, date, checkbox) is chosen to match the source data type. Your admin pre-creates these in Pipedrive; FlitStack maps values during migration.

The reviewer who submits a reference in Zinc Work is stored as a name and email. This maps to a secondary Pipedrive Person record linked to the candidate's primary Person record via Pipedrive's Activity log. If the reviewer is already in Zinc as a contact, FlitStack links to their existing Pipedrive Person record by email match.

Zinc Work preserves when a reference was requested (submission_date) and when the reviewer submitted feedback (completed_date). Pipedrive's CreatedDate is set at migration time, not at the original event time. FlitStack preserves both timestamps as custom datetime fields on the Person record — Reference_Submitted_Date__c and Reference_Completed_Date__c — so reporting shows the original reference timeline.

Pipedrive users (sales reps, hiring managers) must exist in Pipedrive before migration so Zinc Work candidate owners can be resolved by email match. Unmatched owners are flagged before migration runs — your team either creates Pipedrive users first or assigns their candidates to a fallback user.

Zinc Work candidate profiles may include a company name. FlitStack extracts this and migrates it as a Pipedrive Organization record linked to the candidate's Person record via OrganizationId. If the company name is blank or unclear, the Person lands without an Organization link — your admin links it manually post-migration.

Zinc Work labels apply universally across candidate records. Pipedrive labels are scoped per entity type — a label group for People, a separate one for Organizations, etc. If your Zinc label set is used across multiple record types, FlitStack creates parallel Pipedrive label groups and maps each label value per entity type. Your admin reviews and renames label groups post-migration.

Zinc Work automation logic (reference request sequencing, reminder email triggers, threshold-based escalations) has no equivalent in Pipedrive's object model. FlitStack exports Zinc automation definitions as a text reference document your Pipedrive admin uses to rebuild equivalent Pipedrive Automations (Growth+ plan feature). The reference document lists each trigger, condition, and action with screenshots from Zinc Work.

Zinc Work logs candidate profile updates, reference request events, and status changes. These events migrate as Pipedrive Activities (tasks, emails, meetings) linked to the candidate's Person record. Original event timestamps and actors are preserved. This gives your team a complete activity timeline inside Pipedrive rather than a static snapshot.

Zinc Work tracks how a candidate was sourced (referral, job board, direct application, etc.). Pipedrive has no built-in candidate source field. FlitStack creates a custom pick-list field (Source_Channel__c) on the Person object and maps each source value. This preserves sourcing analytics post-migration.