Getting your data into Boom

Boom starts from a CSV export you can produce today. No data warehouse, no middleware, no place in next year's IT roadmap. Most campuses are live in 48 hours.

The default path

What Boom needs
A CSV with one row per student. Required fields: student ID, first name, last name, email, phone, enrollment status, program, credits enrolled, term. Optional: campus, cohort, GPA, Pell eligibility, first-generation status.
How it's delivered
Manual upload through the Boom dashboard, or email to a secure intake address. SFTP drop available on request.
Cadence
Once per term at minimum. Weekly or daily for campuses that want fresher signals.
What happens next
Boom maps your columns to its data model, configures deadlines and escalation paths, and goes live. You review and approve the configuration before any student is contacted.

Going deeper, if you want to

Most campuses start with CSV and stay there. If you want more, the path is: scheduled exports via SFTP, then direct API reads for select systems. Boom grows into your stack on your timeline — not the other way around.

Systems Boom works with

Boom works with these because it doesn't need anything special from them — every one of them exports CSV.

SIS / ERP

  • Ellucian Banner
  • Ellucian Colleague
  • Oracle PeopleSoft Campus Solutions
  • Anthology
  • Jenzabar
  • Workday Student

LMS

  • Canvas
  • Blackboard
  • Moodle
  • D2L Brightspace

CRM

  • Slate
  • Element451
  • Salesforce

Boom's requirements are the same regardless of which system you run.

What this doesn't require

No IT project. No implementation timeline. No middleware license.

What Boom needs from IT

A CSV export of the fields listed above. Realistically, one to two hours of a DBA's time to build the query and set up a recurring job.

What Boom does not need

  • Write access to your SIS
  • Database credentials
  • A data warehouse or ODS
  • A vendor API contract or licensing change
  • VPN access or firewall changes
  • Middleware or an integration engine
  • A place in next year's IT project roadmap

Security and data

FERPA posture, data retention, deletion, and subprocessors are documented on the trust & safety page. Read the trust & safety page.

Back to the platform