Migrate from cvviz to Bullhorn ATS & CRM

CVViZ Job records (title, description, department, location, employment type) map directly to Bullhorn JobOrder. The jobOrderStatus and dateSubmitted fields in Bullhorn correspond to CVViZ's job status and created-at timestamp. CVViZ active-job limits (5-50 per tier) determine how many Jobs migrate as active; any Jobs beyond the target Bullhorn tier are imported as archived. Job board distribution settings (LinkedIn, Google for Jobs) are preserved as metadata but require re-publishing on the destination platform since Bullhorn distributes via Bullhorn Advertising and OpenWeb.

CVViZ Candidate records with name, email, phone, social profiles, employment history, and skills map 1:1 to Bullhorn Candidate. Email address is the dedupe key; Bullhorn enforces email uniqueness per Candidate record. Social profile URLs (LinkedIn, GitHub, Stack Overflow) from CVViZ migrate to Bullhorn Candidate socialNativeID or custom text fields. CVViZ's contact fields (address, timezone, preferred contact method) map to Bullhorn Candidate address, timeZone, and preferredContact fields.

CVViZ stores parsed resume data as structured fields plus raw PDF/DOCX binary files. We extract the binary file and attach it to the Bullhorn Candidate record via the Bullhorn REST API file upload endpoints (/file/{entityType}/{entityId}) and link via contentDocumentLink. Parsed resume fields (summary, education, work experience) migrate to Bullhorn Candidate custom fields. Bullhorn does not run its own resume parser during import; the raw file lands unparsed unless the customer licenses Bullhorn AI resume summarization separately.

CVViZ Application records link a Candidate to a Job with a current pipeline stage and timestamp. These map to Bullhorn JobSubmission with the candidateID and jobOrderID lookups resolved at migration time. The CVViZ application dateSubmitted maps to Bullhorn dateSubmitted; application status maps to JobSubmission status. We preserve the candidate journey through each stage by mapping CVViZ stage timestamps to JobSubmission custom fields if the customer tracks stage history.

CVViZ pipeline stage names are fully customizable per organization with no universal schema. We capture the complete CVViZ stage map during pre-migration schema review, then apply a named mapping to Bullhorn's jobOrderStatus values and any custom status definitions configured in the Bullhorn ATS. Stages with no Bullhorn equivalent are flagged for the customer's Bullhorn admin to configure in Bullhorn Admin > Job Order Status before the final import run. Stage probability percentages, if tracked in CVViZ, migrate to Bullhorn opportunitySuccessRate on the associated Placement entity.

CVViZ Talent Pool entries are passive candidates not tied to a specific active job requisition. We migrate these as Bullhorn Candidate records with a custom passiveTag__c flag set to true, preserving the original source attribution (LinkedIn, GitHub, Stack Overflow, referral) in candidateSource or a custom field. Passive candidates do not have an associated JobSubmission in Bullhorn; they land in the Bullhorn Talent Pool equivalent via Bullhorn's candidate search and talent management features.

CVViZ AI candidate scores are calculated from its proprietary NLP model against the job description and historical hiring data. We carry the score value as a custom numeric field cvvizAIScore__c on the Bullhorn Candidate record. Bullhorn will not recalculate or update this score; it serves as a one-time snapshot from CVViZ. We recommend documenting the score distribution and setting expectations that Bullhorn AI will generate its own candidate-job fit scores through its own model. The original CVViZ score becomes informational only.

CVViZ stores job-specific pre-screening questions and candidate responses as key-value pairs on the Application. We map these to Bullhorn JobSubmission custom fields (using the Bullhorn REST API to create custom fields on the JobSubmission entity) or to custom fields on the JobOrder if the questions are job-level. Questions with no Bullhorn equivalent are flagged in the scoping report with a recommended custom field type. Responses migrate as string values with the question text stored as the field label.

CVViZ job board distribution settings (LinkedIn, Google for Jobs, Indeed, and other boards) are stored as job metadata in CVViZ. We preserve the distribution configuration as a custom text field jobBoardDistribution__c on Bullhorn JobOrder. The actual job postings do not transfer as live links; they must be re-created and published in Bullhorn via Bullhorn Advertising or the individual job board's Bullhorn-integrated connector. We flag all job boards requiring re-activation after migration.

CVViZ Users map to Bullhorn User records by email address. We resolve each CVViZ Owner (recruiter, hiring manager, admin) referenced on Jobs, Candidates, and Applications and match by email against the Bullhorn destination org's User table. Any CVViZ Owner without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision. Custom role permissions from CVViZ are documented in the scoping deliverable; Bullhorn's role-based access is configured separately in Bullhorn Admin > Users & Permissions.

CVViZ custom fields on Jobs and Candidates (excluding AI scores and pre-screening questions) migrate to Bullhorn custom fields on the equivalent entity. We pre-create Bullhorn custom fields via the Bullhorn REST API before migration, matching CVViZ field names to Bullhorn custom field API names with the appropriate Bullhorn data type (string, integer, float, boolean, date, enum). Bullhorn Admin Field Mappings (field-level control on Add/Edit pages) are configured separately by the customer's Bullhorn admin post-migration.

CVViZ does not have a separate client/corporation entity, but Bullhorn's staffing workflow requires ClientCorporation records for agency clients. We create Bullhorn ClientCorporation records from CVViZ organization-level data if present, or from the company's own employer-of-record profile if the customer is an agency. If the customer is a direct employer using CVViZ without client accounts, we configure ClientCorporation as the employer's company record to enable Bullhorn's placement and billing workflow.

CVViZ automation rules (email triggers, notifications, stage transitions) are platform-specific and do not map cleanly to Bullhorn Automation. Bullhorn Automation uses event subscriptions and webhook steps to trigger actions on record changes, but the trigger logic, conditions, and action sets are structurally different. We document each CVViZ automation rule with its trigger, conditions, and actions in a written handoff inventory. Bullhorn's admin rebuilds these in Bullhorn Automation or via Bullhorn's workflow configuration tools post-migration.