Screening volunteers

Import volunteers from another service

Migrate your roster from Sterling (or anywhere) via spreadsheet or API — including last check dates.

Import volunteers from another service
Drop in a spreadsheet and preview every volunteer before importing.

Switching from another background-check service like Sterling? You don't have to re-enter anyone. Bring your whole roster over in one step — by spreadsheet (easiest) or through our API.

Bonus: a clean hand-off

Include a Last check date column and VolunteerBadge schedules each volunteer's next re-screen from it. Pair that with automatic re-screening and your migration becomes truly hands-off.

Option A — Spreadsheet (recommended)

  1. Export your volunteers from your current service to CSV or Excel.
  2. In VolunteerBadge, go to Volunteers → Import Roster and download our template (optional — we match common column names automatically).
  3. Drop your file in. We map the columns, validate every row, and show you a preview.
  4. Confirm you hold signed FCRA authorization for these volunteers, then click Import.

Columns can be in any order; headers are matched loosely. Recognized columns:

ColumnRequiredExample
First nameYesJamie
Last nameYesRivera
EmailRecommendedjamie@example.com
PhoneNo443-790-8081
Date of birthNo05/29/1981
SSNNo123-45-6789
Address / City / State / ZIPNo12112 Blue Hill Trail · Lakewood Ranch · FL · 34211
Last check dateNo06/01/2025 — seeds the next re-screen

Rows missing a name (or with an invalid email/SSN/date) are flagged and skipped — the rest still import. Anyone already on file (matched by email) is skipped automatically, so you can safely re-run an import.

Option B — API (for ongoing sync)

Developers or tools like Zapier can push volunteers programmatically. Create an API key under Settings → API, then:

curl -X POST https://www.volunteerbadge.com/api/v1/volunteers \
  -H "Authorization: Bearer vb_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "first_name": "Jamie",
    "last_name": "Rivera",
    "email": "jamie@example.com",
    "dob": "1981-05-29",
    "state": "FL",
    "last_check_date": "2025-06-01",
    "fcra_authorization_on_file": true,
    "status": "approved"
  }'

The call is idempotent on email — posting the same person twice returns the existing record instead of creating a duplicate ({ "volunteerId": "...", "created": false }).

One requirement

Imported volunteers are created with FCRA authorization marked on file (that's the attestation you confirm). Only import people whose signed authorization you actually hold — it's what allows checks (and auto-rescreen) to run for them.
Didn't find what you needed? Email support@screenforgelabs.com or browse all articles.