Migrate from cvviz to BambooHR

CVViZ Jobs (requisitions with title, description, department, location, and job board distribution settings) map to BambooHR Job Postings. The job title and description migrate directly. CVViZ's department field maps to BambooHR's top-level department value. Job board distribution settings (LinkedIn, Google for Jobs, etc.) are documented as metadata but must be re-published in BambooHR because BambooHR handles its own job board posting distribution natively. Any Jobs beyond the customer's BambooHR plan active-job limit are imported as closed or archived postings.

CVViZ Candidate records (name, contact information, social profiles, employment history) map directly to BambooHR Candidate records via 1:1 field mapping on first name, last name, email, phone, and address fields. Social profile URLs (LinkedIn, GitHub) migrate as custom text fields on the BambooHR Candidate record since BambooHR does not have native social profile fields. Employment history from CVViZ does not map to BambooHR's employee employment history because BambooHR Candidates are pre-hire records.

CVViZ's Talent Pool CRM holds passive candidates not tied to a specific job requisition. BambooHR does not have a native Talent Pool concept. We migrate Talent Pool entries as BambooHR Candidates with a lifecycle tag indicating Passive source. The original talent pool source attribution (where the candidate was first added, e.g., LinkedIn sourced, referral, Stack Overflow) migrates as a custom text field. If the customer requires an active talent pool CRM in BambooHR post-migration, a separate engagement rebuilds this as a BambooHR candidate tagging and list workflow.

CVViZ Application records link a Candidate to a Job with a current pipeline stage and stage-change timestamps. BambooHR's ATS stores application status as a hiring stage on the Candidate record. We map CVViZ pipeline stage names (e.g., Resume Screening, Technical Interview, Final Round) to BambooHR hiring statuses (Applied, Phone Screen, Interview, Offer, Hired, Rejected). Any CVViZ stages with no BambooHR equivalent are flagged during schema review for manual pre-configuration before the final import run.

CVViZ stores resumes as binary PDF or DOCX files alongside parsed structured fields (extracted name, email, phone, skills, education, work history). We extract the raw binary file and attach it to the corresponding BambooHR Candidate record as a file attachment. Parsed structured fields migrate as individual custom fields on the BambooHR Candidate record so that the content is searchable without opening the attachment. If the destination BambooHR account does not have a resume parser, candidates land with the raw file unparsed and the structured fields carried as custom fields only.

CVViZ's proprietary AI ranking score is calculated from its own NLP model against the job description and historical hiring decisions. We carry the numeric score value as a custom field on the BambooHR Candidate record. The destination BambooHR ATS will not recalculate or update it. We recommend documenting the score as a migration snapshot and setting expectations that BambooHR's native ranking will re-normalize over time as users apply their own candidate rating system.

CVViZ stores job-specific pre-screening questions and candidate responses as key-value pairs per Application. We map these to identically named custom fields on the BambooHR Candidate record. If the customer's BambooHR instance does not yet have these custom fields created, we create them during schema preparation. Any questions that used a response type (dropdown, multi-select, file upload) not supported by BambooHR's custom field types are flagged as requiring manual configuration or a workaround in BambooHR.

CVViZ tracks each Application's movement through pipeline stages with timestamps. BambooHR's ATS does not expose a full stage-history timeline natively. We create a custom multi-line text or note field on the BambooHR Candidate record to capture the stage progression with dates. Stage names are mapped during schema review (see Application mapping). The raw stage history is preserved as structured text for audit rather than as a native timeline.

CVViZ automation rules (email triggers, stage-transition notifications, candidate communication sequences) are platform-specific and do not map cleanly to BambooHR's workflow model. BambooHR's built-in workflows handle employee information updates and time-off requests, not job-level candidate communication automation. We do not migrate automation rules as code. We deliver a written inventory of every active CVViZ rule with its trigger, conditions, actions, and a recommended BambooHR workflow equivalent (or a third-party ATS re-adoption plan if BambooHR's native ATS lacks the required automation depth). The customer or a BambooHR partner rebuilds them post-migration.

CVViZ users with recruiter and hiring manager roles map to BambooHR Employee records. We resolve users by email match. Any CVViZ user without a matching BambooHR Employee record goes to a reconciliation queue for the customer's admin to provision before record import. Role-based access control permissions from CVViZ are documented as a role mapping matrix for the admin to reconfigure in BambooHR's permission set model post-migration.