1. Export and map a small pilot
Export candidate and facility/client records from your source system using its supported export tools and your authorized access. Keep an untouched copy. Begin with a small representative sample, including blank fields and multi-state licenses.
StaffTiva currently imports candidates and clients, not job orders, submissions, placements, credentials, attachments or activity history through this CSV importer. Do not infer a full Bullhorn migration from a successful candidate import.
2. Use the actual template columns
Candidates: first_name, last_name, email, phone, discipline, specialty, years_experience, licensed_states, compact_license, desired_pay, availability_date, preferred_locations, status, tags and notes.
Clients: name, facility_type, city, state, msp_name, contract_status and notes. MSP/VMS names are record fields, not direct connections.
Use semicolons for lists, two-letter state codes and YYYY-MM-DD or M/D/YYYY dates. Use yes/true/1 for compact_license. Header names are normalized to lowercase with underscores. A name or full_name can supply candidate names if separate names are absent.
3. Upload, review and import
Sign in to your agency. Owners and Recruiters use Candidates → Import CSV; Owners and Account Managers use Clients → Import CSV. Download the built-in template, select your file and review the ready-to-import count.
Candidates without a first/full name and clients without a name are skipped. Other unexpected values may be retained or defaulted, not fully validated. Check names, pay units, dates and statuses yourself. Imports create new rows; they do not update existing records or automatically deduplicate the file.
Click Import only after review. Rows are inserted in batches of 200. If a batch fails, previously inserted batches remain; review the reported count before retrying to avoid duplicates. Imported candidates belong to the agency and the importing recruiter.
4. Bullhorn switch checklist
Complete these checks before turning off your old process.
- Inventory candidates, clients, jobs, submissions, placements, credentials, documents and activity history separately.
- Confirm authorized Bullhorn exports, retention obligations and any vendor migration fees.
- Map the supported candidate/client fields and agree how unsupported history and attachments will be retained.
- Remove duplicates, standardize state codes and test pay/date formats before importing.
- Import a pilot; compare source counts and review individual records, not just totals.
- Verify recruiter ownership and teammate roles; invite users and test access.
- Recreate a sample client/job/pipeline/placement workflow and verify rates, credentials and reminders.
- Keep payroll, client invoicing, SMS and VMS connections operational outside StaffTiva.
- Agree a final export, cutover window and rollback process; do not import the same rows twice.
Try a fictional CSV sample
This preview runs in your browser. It does not upload or import records; use fictional data only. Full field validation happens through your own review and the signed-in importer.
Questions and answers
Will CSV import migrate all our Bullhorn data?
No. The importer creates candidate and client records from supported fields. Documents, linked history and other record types need a separate reviewed plan.
Does importing update existing records?
No. It inserts new records. Clean your file and check existing agency records before importing to avoid duplicates.
Does the public preview save our CSV?
No. The sample preview below parses in your browser and never writes to the agency workspace. Use fictional data when evaluating the public tool.
